blog draft errors and weird un-userfriendliness

[techwizard]

ok so first the wall of errors, then i'll put the user friendly issues in a reply. these happen when i hit "save article", but it still saves it fine:

Code:

Strict Standards: Non-static method HTMLPurifier_ConfigSchema::define() should not be called statically in /home/rfgene2/public_html/PHP/classes/htmlpurifier/HTMLPurifier/DoctypeRegistry.php on line 11

Strict Standards: Non-static method HTMLPurifier_ConfigSchema::instance() should not be called statically in /home/rfgene2/public_html/PHP/classes/htmlpurifier/HTMLPurifier/ConfigSchema.php on line 108

Strict Standards: Non-static method HTMLPurifier_ConfigSchema::define() should not be called statically in /home/rfgene2/public_html/PHP/classes/htmlpurifier/HTMLPurifier/DoctypeRegistry.php on line 18

Strict Standards: Non-static method HTMLPurifier_ConfigSchema::instance() should not be called statically in /home/rfgene2/public_html/PHP/classes/htmlpurifier/HTMLPurifier/ConfigSchema.php on line 108

edit: there's literally like 50+ more errors of exactly the same nature but i got a 500 internal server error when i tried to post them all at once

[techwizard]

now for the user friendly issues:
 - the drafts should really be easier to find, either a link along with the rest of the blog menu links or in a separate table under edit instead of a link above the list of published blogs.
 - why do the draft previews show under a randomly picked user's blog instead of my own?

[Shadow Kisuragi]

The last answer I can give immediately:
Those drafts are showing up due to the data loss we had back in January 2013. Those are old blogs that we never recovered.

[theGrue]

Looks like we're running a very old version of an external component called HTMLPurifier, which probably doesn't get along nicely with the new version of PHP on our server. I'll have to try to track down everywhere we use it and see how easy it'd be to update to the current version, or if any of the other devs have some more familiarity with it they're welcome to as well.

[Shadow Kisuragi]

Oh crap, that's right... we updated PHP. There are going to be A LOT MORE components that broke, since the standard for PHP changed between the update. I still need to figure out what's broken due to that, but there are going to be a few collection tool items that won't play nice. I had a list of them going, but I can't find it now.

[techwizard]

The last answer I can give immediately:
Those drafts are showing up due to the data loss we had back in January 2013. Those are old blogs that we never recovered.

it wasn't actually the other user's drafts though, it was my own writing showing as posted by me, but previewed on the blog page of someone else.

[Shadow Kisuragi]

That's what I'm talking about - sorry. The IDs in the preview are screwed up, and are showing other blogs.

[Izret101]

I previewed a draft i had saved and every time i checked it i got to see Tondogs blog.

Tech never did confirm if it was the same for him though.

[Shadow Kisuragi]

Whenever I preview a staff blog, it's a different blog. It's just the blog that's stored at that ID - when you publish, it publishes yours in its place.

[NES_Rules]

- why do the draft previews show under a randomly picked user's blog instead of my own?

I may be thinking of something different, but I think this has been the case since day 1 of the blogs. Its just the way Dave was able to work in the ability to preview a blog. I think it has to do with it needing a number ID, but since you're not publishing yet, it can't give you a new one yet, so it throws out a random one for the preview and then updates with a new one when its published.

 - the drafts should really be easier to find, either a link along with the rest of the blog menu links or in a separate table under edit instead of a link above the list of published blogs.

I think the whole blog system could use a facelift, but its pretty low on the priorities list.

[techwizard]

on the home page this time not blogs but similar looking errors:

http://i.imgur.com/BtXzrnt.png

[Shadow Kisuragi]

Yeah, that's a permissions issue for everybody. Not harming much atm.

[techwizard]

looks like it's working normally now!

i was still able to login with the full login page anyway so it wasn't that big a deal but just a slight nuisance

[Zagnorch]

Greetings,

ok so first the wall of errors, then i'll put the user friendly issues in a reply. these happen when i hit "save article", but it still saves it fine:

Code:

Strict Standards: Non-static method HTMLPurifier_ConfigSchema::define() should not be called statically in /home/rfgene2/public_html/PHP/classes/htmlpurifier/HTMLPurifier/DoctypeRegistry.php on line 11

Strict Standards: Non-static method HTMLPurifier_ConfigSchema::instance() should not be called statically in /home/rfgene2/public_html/PHP/classes/htmlpurifier/HTMLPurifier/ConfigSchema.php on line 108

Strict Standards: Non-static method HTMLPurifier_ConfigSchema::define() should not be called statically in /home/rfgene2/public_html/PHP/classes/htmlpurifier/HTMLPurifier/DoctypeRegistry.php on line 18

Strict Standards: Non-static method HTMLPurifier_ConfigSchema::instance() should not be called statically in /home/rfgene2/public_html/PHP/classes/htmlpurifier/HTMLPurifier/ConfigSchema.php on line 108

edit: there's literally like 50+ more errors of exactly the same nature but i got a 500 internal server error when i tried to post them all at once

I received the wall of errors when I attempted to save-and-publish a blog earlier tonight. I then scrolled down, and all the text in the News Body field had disappeared.

I re-entered the blog text, I tried to just Save, but the same wall of errors appeared, and the News Body text box was blank again.

I haven't had any trouble with preview post, though.

[NES_Rules]

This isn't a big deal, but it may be related, but having an apostrophe in the tags section of a new blog entry gives a "The validation of the submitted fields have failed. The description field can be alpha-numeric and also can contain spaces and most forms of punctuation. The publish date field must be of the format YYYY-MM-DD. Make sure that these fields contain the valid characters in them and then resubmit the form " error. I don't know if this has always been the case or not though, I don't usually use apostrophes in the tag section.