On 31 Jan 2014, at 21:16, Eduardo López wrote: > Hi Scott, > > Sorry to bother you again, but the problem continues appearing. Now it > happens when I add a new W3C widget into the store and I place it on the > page. > > When I add a widget that it is already posted on Rave, it appears > perfectly. Any guesses?
Not offhand - would you mind writing up each of the steps you take so I can see where the problem might occur? > > Thanks again. > > > 2014-01-25 Scott Wilson <[email protected]>: > >> >> On 24 Jan 2014, at 20:11, Eduardo López wrote: >> >>> Hi Scott, >>> >>> As Paula and Adrian, I am interested in this topic too. >>> >>> As you said, the widget appears when this attribute is removed, but this >>> change is not persistent, in what way could I make it persistent? >> >> I've found the source of the problem and committed a fix for this into >> trunk. >> >>> >>> Thanks a lot. >>> >>> >>> 2014/1/24 Scott Wilson <[email protected]> >>> >>>> On 24 Jan 2014, at 13:39, Adrian wrote: >>>> >>>>> Ok, solved. >>>>> >>>>> I was putting the .wgt not in the deploy folder but instead in the >>>> upload. >>>>> >>>>> Once I did it in the correct folder It appears in the widget store as >>>> you have commented. >>>>> >>>>> Another two question.: >>>>> >>>>> Every time we start rave we must include our .wgt in the deploy folder, >>>> or there is some way of execution that allow us to run cargo:run and >> have >>>> the own widget automatically added???? >>>> >>>> Well, you should only be using cargo:run during development anyway. For >>>> production you should deploy it in the usual way with Tomcat, in which >> case >>>> starting/stopping Tomcat won't remove any of your content or data. >>>> >>>> If you do need to use cargo:run to run Rave, and keep deploying your >>>> custom widgets, you could build it into your CI process, e.g using >> Jenkins, >>>> so that every time you build you also deploy the widgets and add them to >>>> the store. There is also an option in the portal preferences to skip the >>>> admin approval step for new widgets to speed things up. >>>> >>>>> >>>>> The other one, >>>>> >>>>> Is right now the render function widget for a W3C down??? I add any of >>>> them (mine or default) to portal but nothing appears,any solution? >>>> >>>> It appears so - I've created a new bug in the tracker for this. It may >> be >>>> something fairly trivial, because if you inspect the HTML and remove the >>>> "visibility:hidden" attribute from the widget iframes they look fine. >>>> >>>>> >>>>> Thanks for the help :):) >>>>> >>>>> El 24/01/2014, a las 09:47, Scott Wilson < >> [email protected]> >>>> escribió: >>>>> >>>>>> On 23 Jan 2014, at 11:53, Adrian wrote: >>>>>> >>>>>>> Yes. >>>>>>> >>>>>>> I tryied re-running the command mvn cargo:run, and what I could see >> is >>>> that after executing that command the folder where I placed my .wgt is >>>> eliminated and again created without my own widget.... so, of course, rave >>>> can't add my W3C widget. >>>>>> >>>>>> Just to confirm, I've written out the exact steps I've taken to add a >>>> new W3C widget to Rave: >>>>>> >>>>>> 1. Start Rave (mvn cargo run...) >>>>>> >>>>>> 2. Drop <mycustomwidget>.wgt into tomcat6x/webapps/wookie/deploy >>>>>> >>>>>> 3. In Rave, log in as an admin user (e.g. canonical from the default >>>> install) >>>>>> >>>>>> 4. Click "Widget Store" on the menu bar. >>>>>> >>>>>> The Widget Store page opens. >>>>>> >>>>>> 5. Click "Add new widget" on the menu bae. >>>>>> >>>>>> The Add new widget page opens. >>>>>> >>>>>> 6. Click the "W3C" tab. >>>>>> >>>>>> 7. Click "Browse". >>>>>> >>>>>> The Browse window opens. >>>>>> >>>>>> 8. Scroll down until you find your widget, and click "Get Metadata" >>>>>> >>>>>> The "Add Widget" form appears, with the information from your widget >>>> filled in. >>>>>> >>>>>> 9. Click "Add Widget" >>>>>> >>>>>> The message "This widget is waiting for approval by the site >>>> administrator" is shown. >>>>>> >>>>>> 10. Click "Admin inteface" on the menu bar. >>>>>> >>>>>> The Rave admin interface page opens. >>>>>> >>>>>> 11. Click "Widgets" in the left-hand menu. >>>>>> >>>>>> 12. Navigate through the results until you find your widget. The >>>> results are in alphabetical order. Click the title of your widget. >>>>>> >>>>>> The EDIT WIDGET DATA form opens. >>>>>> >>>>>> 13. Change the value of Status from PREVIEW to PUBLISHED >>>>>> >>>>>> 14. Click UPDATE WIDGET at the bottom of the form (not the orange >>>> "Update Widget Metadata" button) >>>>>> >>>>>> The widget is now published, and should be visible in the widget store >>>> for users. >>>>>> >>>>>>> >>>>>>> >>>>>>> El 23/01/2014, a las 12:39, Scott Wilson < >>>> [email protected]> escribió: >>>>>>> >>>>>>>> On 23 Jan 2014, at 11:33, Adrian wrote: >>>>>>>> >>>>>>>>> Hi all, I'm doing the same right now, but doing the steps as Scoott >>>> or Paula said, I have no widget new in store than the first ones that >>>> appears once I did the custom-installation. >>>>>>>>> >>>>>>>>> So, Can someone explain a little bit more in detail?? >>>>>>>>> >>>>>>>>> I add only my .wgt to the mentioned folder,I must say that it >> works, >>>> I proved it in a wookie portal first. >>>>>>>>> >>>>>>>>> After I execute mvn cargo:run as normal in the portal to run it. I >>>> go to the store and when I'm trying to add a new widget using W3C it >>>> doesn't appear so I'm lost -.- >>>>>>>> >>>>>>>> DId you go to the store admin view and add the new widget? They >>>> aren't added automatically to the store, you have to go through the >> admin >>>> screens and select it from those available from Wookie to make it >> available >>>> in the store. >>>>>>>> >>>>>>>>> >>>>>>>>> Thanks. >>>>>>>>> >>>>>>>>> >>>>>>>>> El 21/01/2014, a las 20:56, Scott Wilson < >>>> [email protected]> escribió: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 21 Jan 2014, at 18:42, Paula Álvarez Álvarez wrote: >>>>>>>>>> >>>>>>>>>>> Hi Scott, >>>>>>>>>>> >>>>>>>>>>> What I did is this: >>>>>>>>>>> 1.- One I had my widget, I copied the folder that contains >>>> all the >>>>>>>>>>> widget's files to the folder where Rave has its own widgets' >> files. >>>>>>>>>>> 2.- Then I copied the .wgt file (my widget) to the foler >>>> where Rave >>>>>>>>>>> has these files: >>>>>>>>>>> >>>> $RAVE_HOME/myraveproject-portal/target/tomcat6x/webapps/wookie/upload >>>>>>>>>>> 3.- I executed Rave as usual and tried to add my widget >>>> from the >>>>>>>>>>> widget store. However, it doesn't appear... >>>>>>>>>>> Is that what you meant? >>>>>>>>>> >>>>>>>>>> Yes (though I'm not sure about step 1 - normally you just need to >>>> drop the .wgt file and nothing else?) >>>>>>>>>> >>>>>>>>>> In Rave, you need to log in as the portal administrator, go to the >>>> widget store, and add the widget to make it available - it doesn't get >>>> added automatically, you need to select it from those available from >> Wookie >>>> within the Rave widget store admin UI. >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thanks, Paula. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -----Mensaje original----- >>>>>>>>>>> De: Scott Wilson [mailto:[email protected]] >>>>>>>>>>> Enviado el: martes, 21 de enero de 2014 15:30 >>>>>>>>>>> Para: [email protected] >>>>>>>>>>> Asunto: Re: Embedding widgets with Wookie >>>>>>>>>>> >>>>>>>>>>> Hi Paula, >>>>>>>>>>> >>>>>>>>>>> On 21 Jan 2014, at 13:38, Paula Álvarez Álvarez wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi at all! I'm Paula. >>>>>>>>>>>> >>>>>>>>>>>> I'm trying to embedding Wookie widgets in a platform with Apache >>>> Rave. >>>>>>>>>>>> I'm reading the documentation and I observed that there are only >>>>>>>>>>>> plugins for >>>>>>>>>>>> < >>>> http://community.elgg.org/pg/plugins/hoisl/read/385029/wookie-widgets >>>>>>>>>>>>> >>>>>>>>>>>> Elgg, >>>>>>>>>>>> < >>>> http://code.google.com/p/foogen/source/browse/#svn/trunk/drupal/modul >>>>>>>>>>>> e/didg >>>>>>>>>>>> et> Drupal, >>>>>>>>>>>> <http://wiki.lamsfoundation.org/display/lamsdocs/Wookie+Widgets >>> >>>> LAMS, >>>>>>>>>>>> <http://moodle.org/mod/data/view.php?rid=3319> Moodle and >>>>>>>>>>>> <http://code.google.com/p/wookiewordpressplugin/> Wordpress. If >>>> I want >>>>>>>>>>>> to do that, ¿is it necessary to develop a new plugin? >>>>>>>>>>> >>>>>>>>>>> No plugin is necessary, as Wookie and Rave are already >> integrated. >>>>>>>>>>> >>>>>>>>>>> In your Rave installation, just drop the widgets into the Wookie >>>> application >>>>>>>>>>> installed alongside Rave in your application server, and deploy >>>> them as >>>>>>>>>>> normal. You use the widget store within Rave to make them >>>> available for >>>>>>>>>>> users to add to their pages. >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> I appreciate any answer because I'm a bit lost. >>>>>>>>>>>> >>>>>>>>>>>> Thanks, Paula. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> --- >>>>>>>>>>>> Este mensaje no contiene virus ni malware porque la protección >> de >>>> avast! >>>>>>>>>>> Antivirus está activa. >>>>>>>>>>>> http://www.avast.com >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> --- >>>>>>>>>>> Este mensaje no contiene virus ni malware porque la protección de >>>> avast! Antivirus está activa. >>>>>>>>>>> http://www.avast.com >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> >> >>
PGP.sig
Description: This is a digitally signed message part
