Threaded Comments & new post galleries

Well, I’ve SVN’d up to the latest version of WordPress 2.7, And as such, I’ve enabled Threaded comments on this blog.

More information about Threaded Comments is available in the Trac Ticket.

I have also implemented some gallery functionality (By that, I mean *more* of a gallery function than a Stock WordPress install has) into my theme, I’ll be replacing Gallery2 with the new WordPress Gallery functionality shortly, You might be surprised at what you can achieve with a theme and the right gallery functions :) – Hopefully you’ll see this when i load the Gallery2 items into WordPress.

Week 12 Status

Well, Today (monday) is supposably the end of coding for SoC.

Am i finished? Heck no. The last few weeks have been *very* slow moving due to Uni & life commitments, But theres no reason why the installer will not be polished & nice by the time 2.7 is released (slated for November 10th, Gee, Uni exams start on the 3rd, I hope people get all the testing done before then please!)

I’m still working on Plugin upload .zip => Install & planning on starting to implement #7395.

I need to go over some of the code and make sure that all data is treated as  non-trusted data (That is, The data returned from the readme’s needs to be sanitized, so probably needs running through kses), of course, I dont have much choice but to trust the .php files :)

Week 11 Status report

Nothing much to report..

I’ve been doing a bit with SwfUpload and installing a plugin via upload, That so far is working, but needs cleaning up a fair bit — I’m still getting used to Swfupload, as well as handling non-flash uploads

Some more work has been done on integrating the user experience between the installer/upgrader/plugin browser, It’d be nice to work out if the page is being loaded via Thickbox or directly, and serve the correct headers, but i have a feeling that’ll be too much work, and as such, should just expect thickbox items to be thickbox served. The other item is the Action links after an upgrade has taken place, due to the error box for re-activation box taking up so much room, the action links are shoved furthur down the page.
One option might be a javascript to increase the height of the iframe to show errors..

Damn Buggy Software!

Well, Thats that, Over the last few weeks i’m sure some people have noticed nice large lovely 500 Error messages on my blog, And i’ve finally fixed it.

Well, Sort of.

It appears to have been caused by a conflict between the Buggy PHP 5.0.5 which my Host runs, and the new HTTP API in WordPress 2.7, The solution? Well, for the past few weeks its been to manually modify some of the source to remove statements which would blow up PHP (ie. replace SITEURL with  get_option(‘siteurl’), which actually just returns SITEURL…. – Note: Thats mearly an example, and not the actual changes i’ve made)’

..Until it happened again today. Finally had enough, I fired up SSH and took a look into it:

me@host:~/www/wordpress$ php index.php
FATAL: emalloc(): Unable to allocate 3768593271 bytes
me@host:~/www/wordpress$ php index.php
Segmentation fault
me@host:~/www/wordpress$ php index.php
Segmentation fault
me@host:~/www/wordpress$ php index.php
FATAL: emalloc(): Unable to allocate 3260808055 bytes
me@host:~/www/wordpress$ php index.php
Segmentation fault

(Oh yeah.. Trying to allocate 3.2GB? I’m not supprised its failing..)

Yep.. I’ve had enough, I have switched from PHP 5.0.5 to PHP 4.4.0 and it appears to now be working.. For now.

I guess the time has come to consider moving to a new Host, I’ve been thinking about a VPS solution, At least that way i can keep up with the version of the software i *want* to use.

Any suggestions from anyone? SliceHost has been mentioned to me, And their base package would probably do for me,  Heck, Find someone else to go halves would end up paying about the same as a el-cheapo shared hosting plan each!. But other host suggestions would be good (or hey, Even a hosting offer or 2 ;) heh)