| By not creating a new WOContext :-)
I forget exactly what I was doing, but I think I was loading a component with the action binding on an AMC. The action binding generated a new page, the new page had a new context, and loaded prototype.js via AOD into the existing page. Then everything broke, including all subsequent calls to AOD.
I believe I fixed it by wrapping the component in the AMC rather than using the action binding. I had to rewrite the component to do that though.
Ramsey On Feb 14, 2012, at 11:20 AM, James Cicenia wrote: OK -
I see all this but what am I supposed to do? Works great on my dev machine but deployment breaks.
This is also a very pure plan jane ERModernLook application... so I don't know where new WOContexts would come from?
how did you solve it before? On Feb 14, 2012, at 12:01 PM, Ramsey Gurley wrote: AOD is on line 159 of wonder.js. It's called whenever you do a ERXResponseRewriter on an ajax response. ERXResponseRewriter keeps track of what it sends down, so it usually doesn't resend prototype.js. But if something happens that generates a new WOContext, then prototype.js sometimes can get reloaded, then all the wonder.js variables are lost.
Ramsey On Feb 14, 2012, at 10:30 AM, James Cicenia wrote: Ok...
What is and where is Ajax On Demand thing?
On Feb 14, 2012, at 11:22 AM, Ramsey Gurley wrote: Ajax Update Popsicle. It always makes my app freeze.
;-)
I've had the wonder.js ajax variables disappear on me on more than one occasion when the prototype.js was reloaded by the Ajax On Demand (AOD) thing. I don't know if that's the problem now, but it's a place to start.
Ramsey On Feb 14, 2012, at 9:52 AM, James Cicenia wrote: ReferenceError: Can't find variable: AUP
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|