Oh, okay. I tried Elgg also but I couldn't get that going either, after setting up plugin and trying to browse Elgg dashboard my Apache web server started to crash for some reason.
Anyway I'll try to get it going somehow. I'll try rewriting the plugin code. On Tue, Feb 23, 2010 at 11:47 AM, Scott Wilson <[email protected]> wrote: > On 23 Feb 2010, at 09:25, Raido Kuli wrote: > >> Hi. >> >> I tried to use Wookie Wordpress plugin. Plugin is installed >> successfully in Wordpress, but it's not usable. > > Hi Raido, > > This plugin was created a long time ago against the early (pre-Apache) > versions of Wookie and probably needs a ground-up rewrite as both Wookie and > Wordpress have changed significantly since then. > > Bernhard's Elgg plugin code may be a better basis for the Wookie-specific > PHP code; I'm also pretty sure Wordpress's built-in plugins and widgets > scheme has changed since this plugin was written. > > S > >> >> Wordpress ver. 2.9.2. >> >> I opened up plugin source to do some debugging. Here are the response >> for three request what plugin does: >> >> 1) >> http://localhost:8080/wookie/WidgetServiceServlet?&requestid=getwidget&api_key=b5MvXajz5xH88pM1rXqghNaN9WQ.eq.&servicetype=qti&userid=1&shareddatakey=wordpress >> >> >> Outcome: >> <widgetdata> >> <url> >> >> http://localhost:8080/wookie/wservices/notsupported/index.htm?idkey=0000&proxy=http://localhost:8080/wookie/proxy&st= >> </url> >> <identifier>0000</identifier> >> <title>Unsupported widget widget</title> >> <height>350</height> >> <width>500</width> >> <maximize>false</maximize> >> </widgetdata> >> >> Servicetype definetly exists, I've tried other servicetypes also. >> >> 2) >> http://localhost:8080/wookie/WidgetServiceServlet?&requestid=setpersonalproperty&api_key=b5MvXajz5xH88pM1rXqghNaN9WQ.eq.&servicetype=qti&userid=1&shareddatakey=wordpress&propertyname=LDUsername&propertyvalue=admin >> >> Tomcat HTTP 400 - The request sent by the client was syntactically >> incorrect (). >> >> 3) >> http://localhost:8080/wookie/WidgetServiceServlet?&requestid=setpersonalproperty&api_key=b5MvXajz5xH88pM1rXqghNaN9WQ.eq.&servicetype=qti&userid=1&shareddatakey=wordpress&propertyname=conference-manager&propertyvalue=true >> >> Tomcat HTTP 400 - The request sent by the client was syntactically >> incorrect (). > >
