THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
So proxify("http://example.org/myservice/") results in a URL like http://my.wookie.org/proxy?url=http://example.org/myservice/&api_key=myapikey
Shindig also uses the same method for OpenSocial applications, and has its own bundled proxy service.
...
Wookie's bundled proxy servlet is a bit stricter than the one bundled in Shindig, as it only allows text, xml or json (not binary), and can also be controlled using a whitelist set up by the Wookie administrator and using W3C WARP. For more information see the Wookie Administrators guide.
How does localization work in Wookie?
...
This problem occurs when building Wookie using Ant 1.8.x. The build will work fine if you use Ant 1.7.1. See Issue WOOKIE-152 for more information
Why doesn't my script run using JQuery's $(document).ready ?
This is a known issue. See Issue WOOKIE-90 for more information. As a workaround you can use <body onload="...">
My widgets do not seem to be updating the preference data in wookie
| Anchor | ||||
|---|---|---|---|---|
|
This is a known issue. See Issue WOOKIE-44 for more information. This problem typically occurs when using Internet Explorer (version 8 and less). It is only flagged here as a warning because depending on how the widget calls the widget javascript API, you may or may not encounter a problem. In essence there are two ways of setting a preference in your widgets javascript implementation...
(1) widget.preferences.setItem("foo", "bar");
(2) widget.preferences.foo = "bar";
If your widget has been coded to only use method (1), there should not be a problem in Internet Explorer. However if your widget implementation uses method (2) or a combination of both, then you may experience unexpected results.
If you are experiencing this problem and you are using Internet Explorer (version 8 or less), then...
(1) update the javascript code to only use method (1) above in the affected widget
OR
(2) install Internet Explorer version 9, which should resolve the problem.
Other browsers should be unaffected by this issue.
Why when I update my widget and load it back onto wookie do I get two copies of my widget in the gallery?
If your widget does not have an id defined in the widget's config.xml file or the id is not a valid URI then wookie will load but not update your widget. If this is the case then (for the moment) you will need to manually remove the old version of the widget using wookie's admin page.