We're seeing a few reports in Blogger Help Forum: Something Is Broken, from blog owners attempting to compose a new post, and seeing
The problem appears to result from trying to compose a post, without first entering a Post title.
It appears that Blogger, trying to stabilise the post editor, is requiring non blank post titles, to save posts being composed. This includes the post being under effects of AutoSave, and the creation of Draft posts.
If you are composing a post, and seeing "Required field must not be blank", ensure that you are entering a valid Title to your new post.
As you enter this non appreciated new requirement, you may consider the requirement for Post Title uniqueness. A single space is accepted as a Title - but multiple posts, with the same Title, will result in duplicate titles, and an anti-duplication title suffix.
As an alternative to the single space, you may be able to hide the Title altogether, by adding custom CSS code.
If you have to change the Title before actually Publishing the post, you may be able to use the Permalink option, to change the URL to match the final Title.
We have a rollup discussion, where we are asking the people who are seeing this problem to provide details of what they are seeing, to help Blogger Engineering diagnose the underlying problem.
If you're willing to provide details, we ask that you be brief, polite, and on topic. Blogger Support needs objective statement of details - but using the rollup discussion to simply complain won't effectively encourage them to do anything.
(Update 7/8): We're seeing reports that this problem has been fixed.
>> Top
Required field must not be blank
The problem appears to result from trying to compose a post, without first entering a Post title.
It appears that Blogger, trying to stabilise the post editor, is requiring non blank post titles, to save posts being composed. This includes the post being under effects of AutoSave, and the creation of Draft posts.
If you are composing a post, and seeing "Required field must not be blank", ensure that you are entering a valid Title to your new post.
As you enter this non appreciated new requirement, you may consider the requirement for Post Title uniqueness. A single space is accepted as a Title - but multiple posts, with the same Title, will result in duplicate titles, and an anti-duplication title suffix.
As an alternative to the single space, you may be able to hide the Title altogether, by adding custom CSS code.
.post-title.entry-title { display: none; }
If you have to change the Title before actually Publishing the post, you may be able to use the Permalink option, to change the URL to match the final Title.
We have a rollup discussion, where we are asking the people who are seeing this problem to provide details of what they are seeing, to help Blogger Engineering diagnose the underlying problem.
If you're willing to provide details, we ask that you be brief, polite, and on topic. Blogger Support needs objective statement of details - but using the rollup discussion to simply complain won't effectively encourage them to do anything.
(Update 7/8): We're seeing reports that this problem has been fixed.
>> Top
Comments
Does this change mean I can no longer publish my blog posts without titles? I've always elected to have the title field turned off, but now it's suddenly there, and insisting that I enter something into it!
Jeez, why fix something that isn't broken ?
Any tip on how to bypass this ?
"Ignore warning" doesn't do anything.
:-)
Thank you for starting a thread for this in Google Groups. I've posted my blog address there already.
Not sure if you're the right person to ask, but do you know if they will reverse this latest update? It's affected me so much so that despite close to 10 years with Blogger, I will be looking out for other blogging platforms if the issue is not resolved.
Hope to hear from you soon! =)
I'm still using Windows 98 and Netscape 9.0, and I haven't been able to post a title for months now.
Therefore, with this new requirement, I can now not post at all.
And before you say 'please update your browser', I'm already working with the highest browser for Windows 98. Upgrading my browser would include buying a new computer.
Just a thought.
Blogger provides their product with features which are supported for a limited set of browsers, browser versions, operating systems, and operating system versions.
Windows 98 and Netscape 9 are long declared obsolete. Blogger simply cannot support their use. You are allowed to use your computer, as you wish - but you are on your own when you do this.
Buy a new computer - please.
http://blogging.nitecruzr.net/2011/08/blogger-browser-support-policy-and.html
The error message is:
Required field must not be blank Ignore warning
Now the real problem is that the 'Ignore warning' option is not working. You can click on it, but it immediately bounces back whenever there is an automatic or manual save.
Question: why force everyone to have a title, when a) not everyone can save the title and b) not everyone wants to fill in a title.
For that matter, why force people to use the new interface, and not give the users the option to keep using the old interface?
Is blogger there for the ease of use for the actual bloggers, or for the programmers.
Just a suggestion.
Most people simply put the cursor in the Title box, and hit the Space bar once, to simply add one space.
One of the problems here is that the "Title field must not be empty", the "You can't have more than 20 labels", and the "You can't have more than 200 characters in labels" error conditions, which are all common post editor problems, share the same error format - an error message (in this case, "Required field must not be blank"), followed by the option to "Ignore the warning".
Blogger programmers reuse a lot of code - some excessively. This is, to our eyes, excessive reuse. Whether they will agree remains to be seen. Obviously (to our eyes), the option to "Ignore warning" is wrong, since the Title is a required field.
There may be actual reasons (however misguided) behind the change which currently causes this new error condition. I'll explore these reasons, separately.
I do hope, however, that you are able to heed my advice, given quite seriously - that you purchase a new computer. Windows 98 is seriously out of date - and it's continued use poses a security risk to you, and to your neighbours.