dDeviantArt Announcement

EDIT: A number of bugs were present in 0.1 as expected, a Beta of 0.2 is now available, If the plugin doesnt work for you, try this beta version:  http://dd32.id.au/files/ddeviantart-0.2.zip

I’m proud to present to you, dDeviantArt 0.1.

dDeviantArt is a WordPress plugin designed to integrate your Deviations from DeviantArt.com into your WordPress blog.

The main features are:

  •  The ability to have Multiple Widgets predefined, This allows you to quickly switch between the Deviation set your displaying (Or to display multiple Widgets at once)
  • In-line Deviations, You can post deviations inside your Blog post by simply including the :thumb: string which is located on all Deviation pages
  • Portfolio Pages, You can define an unlimited number of “Portfolio Pages”, These pages allow you to show off upto 24 of your Deviations on a single page.

The plugin allows you to either set a RSS feed of the Deviations you want to display, Or allows you to set the Search Criteria when defining a page/widget, This allows anyone to quickly set up the item to display as they please.

More information(And Demos) will be available on the Plugin Homepage, You can download the plugin directly from here.

All comments are welcome, Feature requests, Bug reports, etc, may be submitted via my Contact page.  This is my first Released Plugin, So hopefully you’ll like it.



Download Link  WordPress Plugin competition DeviantArt News

Week 7 status report

Whats been acomplished this week.

  • Integrated the Plugin Search page with the Plugin Installation pages
  • Added a few filters/actions here and there
  • Plugin installation page checks requirements before installing plugins(If requirements are available from wordpress.org)
  • Started the ball rolling for the wordpress.org integration server side.
  • A Few misc. other things.

Plans for Next Week

  • Improve Plugin Installation methods
  • Improve FS options (And the Options page for it)

Problems Encountered so far (And useful resources)

  1. #4639 came into play this week, in short, the “admin_print_scripts-plugin_folder/plugin.php” doesnt fire if the plugin is in a subdirectory.. Was found as the issue while looking into westi’s comment here: gsoc-week-5-status-report#comment-52

This week was a rather slow week development wise, and this blog entry is running late too, Hopefully next week there’ll be more to report on.

Week 6 status report

Whats been acomplished this week.

  • Started putting together a linux box for testing purposes, the VM was becoming rather clunky in performance, Slackware+Apache2+PHP5(module), also plan on doing PHP4 and hopefully safe mode on/off, and perhaps even PhPSuExec if i can manage them all.. I can handle Virtual Hosts OK, just not yet sure on how different PHP settings will work.
  • Removing Serialized data support, moving to XML.
  • Added Ajax loading of next page worth of Theme Search results
  • Started the Plugin Search interface
  • Cleaned up a bit of code.
  • Added a few filters/actions here and there
  • Few minor modifications of the Requirement checking

Plans for Next Week

  • Continue tidying up the plugin search pages
  • Add Plugin installation methods
  • Improve Filesystem handlers
  • start investigating what needs to be done to achieve a plugin/theme upgrader
  • Add more filters and hooks into the code
  • Start writing some documentation on the hooks
  • Start PHPDoc comments for the filesystem handlers(Only in the Direct filesystem class for now, the others are functionally the same) as well as any other functions.
  • Continue testing under other environments, If someone would like to do testing for me, get in touch.

Problems Encountered so far (And useful resources)

  1. PHP XML Functions contain no useful method to convert XML into a flat array simply, theres the option of several PEAR libraries, or simply using preg_match (Which i have done for now).
  2. Bug #3002 affected my only tester this week.. turned out to be the reason the last plugin he tried didnt work as well.
  3. The documentation which explains adding a hook into a plugins code is rather lacking IMO, It took me awhile to find something which could explain a action with multiple arguements, Infact, I think Ihad to do a grep over the WP source code in order to find something, Writing up documentation isnt my strong point, but IMO a good chunk of documenation needs to be written on the codex.
  4. Oh, and TinyMCE suddenly breaking into non-breaking spaces again, Someone got a plugin to strip out non-breaking spaces?, Else i’ll write one next week.