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 wordpress.org 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..

Week 10 progress

Its time to get a move on!

  • API is Live!
  • A Diff is available on #6015
  • There are a number of TODO items still, however its definately getting there

Major items to note

  • Read general writeup in this trac comment: http://trac.wordpress.org/ticket/6015#comment:8
  • The API only returns 6 items per page right now it seems, I might have to look into that
  • upload-a-zip is not yet implemented, however shouldn’t be too difficult – but we’ll see about that :)
  • General testing of the code so far is needed, most of it should work pretty well AFAIK – as i would hope – but YMMV, so get to it! – I wouldnt mind this being commited to WordPress trunk right now, Would make it a lot easier to track progress.. The weeks seem to be flying past right now, and i’ve not got a clue what work i’ve actually done (Uni semester has started, and yet, i seem to have done SFA work..)

    Week 8/9 Status Report

    Last weeks status report was missed, There was not much to report in terms of progress & with Uni starting again this week..

    Progress has returned to a slow pace, The API has started being integrated into api.wordpress.org – Once that is complete, The plugin installer/browser should be able to be commited into the wordPress 2.7 trunk, theres still a lot more work to do, But theres another few months to finish it up while its in trunk, and people can report back on whats working, and whats buggy.

    A few changes are needed to the plugin information dialogue, The dialogue might be better integrated as a generic plugin browser – so that the upgrader can utilise it as well, this would allow users to get a bit more information about the plugin update before upgrading – Currently theres a link to wordpress.org, having that as linking to a thickbox plugin page would allow users to stay within wordpress, yet get all the information related to the plugin.

    Furthur to that last point, It might be possible to have each plugin item link to their respective plugin information page (If wordpress.org hosted) – This could allow for future integration between the WordPress.org plugins directory and Self-hosted wordpress installs, For example, rating plugins from within WordPress (Which was a requested feature of the installer actually).

     On the coding front, I’m not currently at home, so i cant really compare whats actually changed since last report, but AFAIK, Most of the activity has been cleaning up and modularising quite a lot of code, I looked at adding a Progress meter at some stage, However came up against a pretty nice brick wall when i realised there is not any decent pre-made progress bars written in Javascript/jQuery, Yes, theres a few half-attempts at them, but none which are what i would call, Useable. this basically meant that i ended up combining 2 jQuery progress bar plugins into one giant mess (Me not understanding how to write a jQuery plugin didnt help i’m sure) – So that was a pretty bad loss, I reverted all the progress bar changes and decided to have another crack at it later perhaps.


    PS: SCU; Your fire alarm has been going off in 2 of your computer labs for 10 minutes allready, Why has no-one noticed, and for that matter, Why are all us students just ignoring it?