WordPress Fun

24Apr07

I guess I haven’t been stressing WordPress until now but yesterday’s post didn’t quite work out as planned. I’m probably trying to be a bit too fancy with the layout but because I’m using WordPress’ free hosting¹ and don’t have as much control over the layout as I’d like I had to hack it a bit. I’ll be tidying it up a bit shortly but I’ll probably also need to move to my own hosted version as well to give me more control.

A funnier² problem emerged while I was working on editing the post though. For some reason when I edited it after it had been published it was marked as private without my knowledge. A quick Google turned up these posts here and here, along with this thread, about how this is a bug, apparently occurring when editing published posts using Firefox. It didn’t seem to happen to me when I was using Safari³ so this is probably the case. However I’m starting to wonder if this isn’t so much a bug as an undocumented feature⁴.

Essentially what happens is that when you edit an already published post and then hit “Save and Continue Editing” it is suddenly marked as Private. This actually kind of makes sense. If you want to save an already published post but want to continue editing it then you may not want it visible while you’re still making changes. When you’re done you manually reset it back to public and hit save. Perhaps I need to RTFM but I didn’t realise that it was supposed to work like this. I’ll also need to play around with this to confirm it but if it’s consistent behaviour then why does it only seem to “work” on Firefox? Perhaps the real bug is that it doesn’t seem to happen on any other browser.

Follow-up 24/4/07: No. It’s a bug. :-) Tried reproducing the problem while editing yesterday’s post but couldn’t get it to happen.

– Fintan

---

1 – And being cheap about it by not paying the extra for CSS editing…
2 – But not ha-ha funny.
3 – Although the HTML validator in the editor on Safari has a nasty habit of just removing anything it doesn’t like – including any element attribute that doesn’t have a space between it and the end of the element: align=”right”/> will cause the entire align attribute to be removed, align=”right” /> is okay though (note the space…).
4 – Ah! That old excuse.

---

Possibly related posts: (automatically generated)

• Turkey ::Goodbye Cruel World…For a Week at Least!::
• Plague House

Filed under: Blogging, General   |  Leave a Comment