NOT OPEN

How to Fix Custom Blogger Template support issue?

 

by Mohammad Fazle Rabbi

 5/5/15 

This topic is a duplicate

Please state the blog URL and any other details that you consider relevant, so we can address your issue quickly.
Hi Everyone,
I am a Blog owner and my Blog URL is http://www.bloggerspice.com/ but today suddenly I saw my Blogger site has broken. Blogger Auto Readmore code is not working anymore. But it is displaying whole post at a time.

I have created new demo blog but after uploading template showing same problem. Not only my template I have tested with several developers template. Not a single template working correctly. Open my Blog is Google Chrome. Opera, Mozilla but showing same problem.

I think this is problem from Blogger. But how to fix it? If anyone knows then please reply me soon.

Best Regards

Mohammad Fazle Rabbi

Categories:ChromeGet Help with an IssueTemplates, gadgets, HTMLWindows

4 posts

30 views

1 expert reply

+1

Community content may not be verified or up-to-date.

Similar topics

When will HTTPS be available for Custom Domains? I have a custom domain. I got the warning there was mixed content in my post and I pressed 'fix'. Now you can't see the post on mobile. Thank you

How do I add an author image and blurb to my blogs? (There is a blank space and i DONT KNOW HOW TO FIX IT)

menu issue on mobil

Replies

Press the enter key on a collapsed row to expand it.

5/5/15

Planx said:

We're experiencing the same problem with all of our templates.  Need a fix for this asap!

+1

5/5/15

Mohammad Fazle Rabbi said:

I am confirm this problem arise from Blogger. But I have found the solution.

Step 1 Go to https://www.blogger.com and Sign in to your account

Step 2 From Blogger Dashboard click on ->Template ->Edit HTML

Step 3 And locate the "Blog1" section in your Blogger template

and replace it with "Blog2"

Finally save your template.

+1

5/5/15

Thanks for posting in the Blogger Help Forum.  I believe that your issue is related to editing/custom HTML.  If so we're aware of this issue and are working on getting it addressed.  Please check out