Well, would you look at that. While seriously procrastinating over my dissertation (in next week, haven't started it >.< ) I managed to finish my CMS. And here it is.

...nope, there's nothing different on your end, but there's a lot of difference on my end :) Most notably the fact that I don't have a layout for my admin panel and everything is a little bit weird.

Let me know if you see anything going wrong. I *think* everything's been updated for the new system, but knowing me I'm sure to have missed something.

Oh yes, and those of you subscribed to the feed: it doesn't work. It's on the list of things to do though. Fixed it!

Edit: I know about acronyms not displaying in feeds Fixed! I also know about the fact that the archive pages say "older entries" and when you click on that link you get newer entries. Various character encodings in the feed need fixing as well (double-escaped entities and stuff)... That and the random backslashes appearing every now and then. Ho hum.

...you dream about your script getting its own LiveJournal community. >.<

If by now you aren't aware of the serious vulnerabilities that exist within CodeGrrl.com's most popular scripts then I would recommend that you read this announcement as a matter of urgency.

As a result of the above vulnerability, I have recently discovered that certain people have been telling others to delete the affected file, protection.php, to avoid being hacked.

DO NOT DO THIS.

Deleting protection.php takes away the admin panel's password protection and you will be leaving your scripts wide open to much more than hacking.

At first I thought it was just a misinformed user telling others what they thought was best - I was wrong. Today I was alerted to the fact that it is in fact Surpass Hosting that is spreading this very seriously incorrect advice.

Please spread the word about this. Deleting protection.php is about as secure as leaving it unpatched on the server. You WILL be hacked if you leave it unpatched, and you will also be hacked if you delete it. If you've deleted protection.php, put it back as soon as possible and tell anyone else who may have deleted it to do the same.

If you are at all worried about running PHPFanBase or any other affected CodeGrrl.com script and have decided against keeping said scripts, you need to delete ALL the files associated with the scripts, not just protection.php.

Oh, and Surpass have apparently banned my script, PHPAskIt, because they believed the recent security vulnerability hoax that stated that my script could be hacked like the rest of the CG scripts. It CAN'T. It is not based on PHPFanBase like the vulnerable CodeGrrl scripts are, and can NOT be hacked through protection.php (there is no such file anyway) or through any similar method in other files.