Hi, Seems the anonimous data are corrupted, can you clean the cookies and refresh the portal and check.
Regards /Nuwan On Thu, Aug 12, 2010 at 7:49 PM, Daniel Callejas Albalate <[email protected]>wrote: > The only error a could see is a JavaScript error in that function > > > > gadgetserver.showExtraGadgets = function() { > > var checkGroup = document.newGadgetForm.checkgroup; > > if (checkGroup.length > 0) { > > jQuery("#newGadgetsPane").show("slow"); > > } > > }; > > > > The error is that > > Error: checkGroup is undefined > > > > And the line: if (checkGroup.length > 0) { > > > > But seems a error retrieving data from the db, or at least it seems to me, > but in the logs there aren’t any error. > > > > *De:* [email protected] [mailto:[email protected]] *En > nombre de *Daniel Callejas Albalate > *Enviado el:* jueves, 12 de agosto de 2010 15:37 > > *Para:* [email protected] > *Asunto:* Re: [Carbon-dev] Status Error 500 > > > > Thanks for the help! Now is working almost perfectly. The last thing that > remains is, the default gadgets aren’t visible and only the gadgets added by > the user can be viewed and the anonymous users can’t add gadgets the button > to add gadgets doesn’t respond. Any idea? > > > > Thanks, > > Daniel Callejas > > > > *De:* [email protected] [mailto:[email protected]] *En > nombre de *Senaka Fernando > *Enviado el:* jueves, 12 de agosto de 2010 10:31 > *Para:* [email protected] > *Asunto:* Re: [Carbon-dev] Status Error 500 > > > > > > On Thu, Aug 12, 2010 at 11:42 AM, Tyrell Perera <[email protected]> wrote: > > > > On Wed, Aug 11, 2010 at 6:11 PM, Daniel Callejas Albalate <[email protected]> > wrote: > > Well, we have a partial workaround. With one server in R/W mode and the > other on Read Only, the Read only server doesn’t generate more error. With > that in mind we mount a third server. Now two are in Read only mode, which > act as front-end, and the last one are in R/W mode an isn’t accessible from > outside and his only work is to update the DB. Now the two front-end server > doesn’t generate more 500 errors, but now we have another issue, if we log > in one of the front-end server and create a new tab or add a gadget this > changes doesn’t persist only if we make the changes on the R/W server the > changes are available on the other server. There are some issue with the > replication of this elements? > > > > > This is because of the read-only nodes. You can't use GS nodes with read > only, they all have to be R/W. You might be able to fix the concurrent > modification issue by disabling registry versioning. > > > Yep. It seems that all nodes in GS needs to be R/W. To disable versioning > in Registry, you will have to yet again modify the registry.xml of each > node. More information can be found at [1]. Please note that you will need > to start with a fresh database after versioning has been disabled. > > Regarding the clustering scenario, I believe that future versions of GS, > might need to have the possibility of starting against a read-only config > node. > > [1] http://wso2.org/library/tutorials/learning-registry-xml > > Thanks, > Senaka. > > > > Tyrell > > > > > Thanks! > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Nuwan Bandara WSO2 Inc. | http://wso2.com lean . enterprise . middleware http://www.nuwanbando.com
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
