Strange Object entering Session differs in Dev vs. Deploy
Strange Object entering Session differs in Dev vs. Deploy
- Subject: Strange Object entering Session differs in Dev vs. Deploy
- From: Nathan Walker <email@hidden>
- Date: Tue, 21 Jun 2005 11:47:52 -0400
I have this CMS solution. When the user is logged into the site, they
may edit each page by clicking an Edit button which pops open a new
window (with javascript) that contains form fields that allows them
to edit the content. In development mode, everything is dandy, you
click the Edit button, the page content shows right up in the new
Edit window and you can click Update and it saves the page back to
the database, closes the Edit window and refreshes the parent page
and shows the updated content.
Now when I went to Deploy the app (standard WebObjects deployment
with Monitor), when you click the Edit button, the new window pops up
and shows nothing, but if you hit Cancel (which closes the Edit
window) and click Edit a SECOND time, THEN the content displays in
the new Edit window and you can make changes. It's behavior is
consistent across every page. Why is this different in deploy mode ?
I am using the Default Editing Context because it is a very simple
CMS solution and the page content is being pulled into the
defaultEditingContext every time you click the Edit button. I am
confused.
hopefully this is clear,
Thanks,
Nathan
_______________________________________________
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