You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by Raido Kuli <ra...@gmail.com> on 2010/02/24 14:08:55 UTC
Wordpress plugin updated
Hi!
I've updated Wordpess plugin. Previous Wordpress failure thread -
http://markmail.org/thread/7ilxyduqdkqbulaf
Update: Add Gallery (dropdown menu for selecting widget) support
from Elgg/Moodle plugin
Adjust width/height from plugin settings
Fix getWidget part, widgetid parameter appended to the request URL
Try it out, waiting for some feedback and debugging if any problems occure.
--
Raido
Re: Wordpress plugin updated
Posted by Scott Wilson <sc...@gmail.com>.
On 7 Mar 2010, at 20:17, Raido Kuli wrote:
> Hi.
>
> Now for some time I've been working on Wookie PHP framework. For now
> the framework is quite complete, so I did some work on Wordpress
> plugin too.
>
> I've created project on
> http://code.google.com/p/wookiewordpressplugin/. So link can be added
> to Wookie plugins page.
Fantastic - I've updated the link.
>
> If for some reason it's not acceptable, I can just create issue on
> tracker and 'Grant license to ASF for inclusion in ASF works'. and
> close project on Google code.
>
> --
> Raido
>
>
>
> On Sat, Feb 27, 2010 at 10:17 PM, Scott Wilson
> <sc...@gmail.com> wrote:
>> A great amount of work has gone into the plugins/connectors area
>> recently by
>> everyone - and I'm really pleased we've got a usable Wordpress
>> plugin at
>> last!
>>
>> On 26 Feb 2010, at 11:15, Raido Kuli wrote:
>>
>>> Should be fixed, thanks for testing and feedback.
>>>
>>> --
>>> Raido
>>> <wookie_wordpress26022010.zip>
>>
>>
Re: Wordpress plugin updated
Posted by Raido Kuli <ra...@gmail.com>.
Hi.
Now for some time I've been working on Wookie PHP framework. For now
the framework is quite complete, so I did some work on Wordpress
plugin too.
I've created project on
http://code.google.com/p/wookiewordpressplugin/. So link can be added
to Wookie plugins page.
If for some reason it's not acceptable, I can just create issue on
tracker and 'Grant license to ASF for inclusion in ASF works'. and
close project on Google code.
--
Raido
On Sat, Feb 27, 2010 at 10:17 PM, Scott Wilson
<sc...@gmail.com> wrote:
> A great amount of work has gone into the plugins/connectors area recently by
> everyone - and I'm really pleased we've got a usable Wordpress plugin at
> last!
>
> On 26 Feb 2010, at 11:15, Raido Kuli wrote:
>
>> Should be fixed, thanks for testing and feedback.
>>
>> --
>> Raido
>> <wookie_wordpress26022010.zip>
>
>
Re: Wordpress plugin updated
Posted by Scott Wilson <sc...@gmail.com>.
A great amount of work has gone into the plugins/connectors area
recently by everyone - and I'm really pleased we've got a usable
Wordpress plugin at last!
On 26 Feb 2010, at 11:15, Raido Kuli wrote:
> Should be fixed, thanks for testing and feedback.
>
> --
> Raido
> <wookie_wordpress26022010.zip>
Re: Wordpress plugin updated
Posted by Raido Kuli <ra...@gmail.com>.
Should be fixed, thanks for testing and feedback.
--
Raido
Re: Wordpress plugin updated
Posted by Bernhard Hoisl <be...@wu.ac.at>.
hi,
works for me - great.
just a quick comment: in file wookie.php line 210 you should also check
whether there is an ending slash or not by calling you checkWookieURI()
function:
$widgetGallery = new Gallery(checkWookieURI($wookieConf['server']));
furthermore, the gallery gives an error if no valid wookie url is
provided. so you could link that to your connection testing. only if a
connection was established successfully, instantiate a new widget
gallery in line 210. you do connection testing just some lines before.
-bernhard
Raido Kuli wrote:
>> Yeah, that can be done.
>>
>> I'll work one the code a little and get back here with updates when
>> they're ready.
>
> Update:
> Add Gallery support from Elgg/Moodle plugin
> Adjust width/height via web-interface
> Configure Wookie URI and API key via web-interface
> Display some info messages:
> a) If loading Widget failed -> "Could not load Widget (Connection failed)"
> b) API key or/and Wookie URI not set
> c) "Connection failed / Connection successful", when configuring Wookie URI.
> d) If no widget selected via Gallery, display -> No Widget
> selected! (widgetid empty)
> 'shareddatakey' parameter set to -> "wordpress_someWidgetIdHere";
>
> Waiting for testing feedback.
>
> At the moment this code could be better, but hopefully in near future
> there's going to be plugin framework, when that happens, this plugin
> is going to be rewritten.
Re: Wordpress plugin updated
Posted by Raido Kuli <ra...@gmail.com>.
> Yeah, that can be done.
>
> I'll work one the code a little and get back here with updates when
> they're ready.
Update:
Add Gallery support from Elgg/Moodle plugin
Adjust width/height via web-interface
Configure Wookie URI and API key via web-interface
Display some info messages:
a) If loading Widget failed -> "Could not load Widget (Connection failed)"
b) API key or/and Wookie URI not set
c) "Connection failed / Connection successful", when configuring Wookie URI.
d) If no widget selected via Gallery, display -> No Widget
selected! (widgetid empty)
'shareddatakey' parameter set to -> "wordpress_someWidgetIdHere";
Waiting for testing feedback.
At the moment this code could be better, but hopefully in near future
there's going to be plugin framework, when that happens, this plugin
is going to be rewritten.
Re: Wordpress plugin updated
Posted by Raido Kuli <ra...@gmail.com>.
Yeah, that can be done.
I'll work one the code a little and get back here with updates when
they're ready.
On Wed, Feb 24, 2010 at 4:25 PM, Bernhard Hoisl <be...@wu.ac.at> wrote:
> I gave it a try and it works for me - looks good.
>
> Just some quick comments:
>
> - If you haven't defined the URL to Wookie and the API key a PHP error
> occurs -> maybe you can catch it and diplay a notice
> - Would be good if you can insert the URL to Wookie and the API key directly
> through the wordpress web-interface (like in the manage plugins site) - is
> this possible?
> - i think the shareddatakey property should not statically be 'wordpress'
> but representing a specific context of wordpress, like the internal
> wordpress widgetd id or similar
>
> -Bernhard
>
>
> Raido Kuli wrote:
>>
>> Hi!
>>
>> I've updated Wordpess plugin. Previous Wordpress failure thread -
>> http://markmail.org/thread/7ilxyduqdkqbulaf
>>
>> Update: Add Gallery (dropdown menu for selecting widget) support
>> from Elgg/Moodle plugin
>> Adjust width/height from plugin settings
>> Fix getWidget part, widgetid parameter appended to the
>> request URL
>>
>> Try it out, waiting for some feedback and debugging if any problems
>> occure.
>>
>> --
>> Raido
>
Re: Wordpress plugin updated
Posted by Bernhard Hoisl <be...@wu.ac.at>.
I gave it a try and it works for me - looks good.
Just some quick comments:
- If you haven't defined the URL to Wookie and the API key a PHP error
occurs -> maybe you can catch it and diplay a notice
- Would be good if you can insert the URL to Wookie and the API key
directly through the wordpress web-interface (like in the manage plugins
site) - is this possible?
- i think the shareddatakey property should not statically be
'wordpress' but representing a specific context of wordpress, like the
internal wordpress widgetd id or similar
-Bernhard
Raido Kuli wrote:
> Hi!
>
> I've updated Wordpess plugin. Previous Wordpress failure thread -
> http://markmail.org/thread/7ilxyduqdkqbulaf
>
> Update: Add Gallery (dropdown menu for selecting widget) support
> from Elgg/Moodle plugin
> Adjust width/height from plugin settings
> Fix getWidget part, widgetid parameter appended to the request URL
>
> Try it out, waiting for some feedback and debugging if any problems occure.
>
> --
> Raido