No, I’m not sure why it worked originally, but the “sessions fix” is not working on the original site either :/.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
March 16, 2011 6:08pm
Subscribe [6]#16 / Jun 30, 2011 2:37pm
No, I’m not sure why it worked originally, but the “sessions fix” is not working on the original site either :/.
#17 / Jun 30, 2011 4:54pm
Hi, Stephen. Let’s recap.
You mentioned this was a problem on MT dv.
Using EE 2.1.3. the December build, and you still are setting Control Panel Session Type to Cookies only?
Has any of this changed?
#18 / Jun 30, 2011 5:27pm
Yes, that’s still correct—nothing has changed.
#19 / Jun 30, 2011 6:27pm
Stephen, if you turn on Firebug, or your debug console, or whatever you use for that =) Do you see any JS errors when you first load the edit screen?
We may need to have a look, but I want to rule out the obvious first.
Also, 2.2.1 is out and there are over 180 bug fixes since 2.1.3. Are you able to test that in a dev environment and see if it fixes your edit entry issue? Actually, I’d be curious if you can reproduce at all on your own dev installation with your data, etc. We’re definitely not seeing other reports of this, and I can’t reproduce.
Thank you!