I can move this if it's better placed elsewhere:
2 issues have surfaced post upgrade;
a.) The "author" actually posted on the blog header is not the author set anywhere on the actual blog post form. (Curiously, it is the name of the last user I created, but I'm not signed in as that)
b.) the "password" autofill on the blog save form problem that I previously discussed has re-surfaced, but worse; in 2.3 if I was aware of the password being auto-filled I could edit the form to remove it and re-save - now, the auto-fill happens again between clearing the field and the "Save" function being activated.
Upgrade to 2.5
Re: Upgrade to 2.5
b.) it turns out that it looks worse, but actually clearing the password field before saving still works. In 2.3 the autofill didn't refill the password field after save; now it does. Can I suggest you either: 1.) make this a configuration option so if we don't want it, it doesn't appear on the form to tempt the browser, or
2.) don't use the word "password" on the form. Call the field "protect your entry" and use the info icon to explain that further. I don't know what your variable are called, but hopefully nothing with "password" in them
The authorship problem remains, but it's not a big or urgent one
2.) don't use the word "password" on the form. Call the field "protect your entry" and use the info icon to explain that further. I don't know what your variable are called, but hopefully nothing with "password" in them
The authorship problem remains, but it's not a big or urgent one
Re: Upgrade to 2.5
Hi!
As a note, you can deactivate the entry password field. Plugins -> Event Plugin -> serendipity_event_entryproperties (its settings) -> remove the checkmark of the password item.
As a note, you can deactivate the entry password field. Plugins -> Event Plugin -> serendipity_event_entryproperties (its settings) -> remove the checkmark of the password item.