Sorry if this doesn't help but I remember experiencing the same phenomenon before when I used 4.7.5. I remember I also posted a few queries in the main Drupal site about it but I never got around to solve the problem so I "was forced" to move up to 5.x back then. It appears you have already tried what I would normally tinker with - try different browsers, clear my browsers' cache, empty the Drupal sessions table...
Pasensya na po.
How about doing a fresh install of 4.7.8's files in another directory while using your old db?
I know enough that the db schema changes quite significantly from one major version to another, so that would be out of the question. I had to repopulate the nodes by hand. Incidentally, there is a node populator script for Drupal (taking from one db onto another, third-party solution) I've come across somewhere but I've lost track of it. I believe it also works for CCK. Takes a bit of work but will be sure worth the time especially if you have gazillions of node content already. Maybe you or others can find it.
Comments
Sorry if this doesn't help
Sorry if this doesn't help but I remember experiencing the same phenomenon before when I used 4.7.5. I remember I also posted a few queries in the main Drupal site about it but I never got around to solve the problem so I "was forced" to move up to 5.x back then. It appears you have already tried what I would normally tinker with - try different browsers, clear my browsers' cache, empty the Drupal sessions table...
Pasensya na po.
How about doing a fresh install of 4.7.8's files in another directory while using your old db?
Good luck!
http://loloyd.net/, http://loloyd.com/
Hi loloyd, Thanks. When you
Hi loloyd,
Thanks.
When you upgraded to 5.x did you use your old database? Just so I can eliminate the possibility of the database being the problem.
http://PinoyTechie.com | http://PinoyFilm.com | http://FilipinoWriter.com | http://WriteLit.com
http://PinoyTechie.com | http://PinoyFilm.com | http://FilipinoWriter.com | http://WriteLit.com
God, no
I know enough that the db schema changes quite significantly from one major version to another, so that would be out of the question. I had to repopulate the nodes by hand. Incidentally, there is a node populator script for Drupal (taking from one db onto another, third-party solution) I've come across somewhere but I've lost track of it. I believe it also works for CCK. Takes a bit of work but will be sure worth the time especially if you have gazillions of node content already. Maybe you or others can find it.
Good luck!
http://loloyd.net/, http://loloyd.com/
had the same problem last
had the same problem last year. after upgrading my 4.7.3 to a more recent version, everything was ok. check this out Upgrade
collectivetech.org
Technology for organizations. Open Source. Consultancy. Training.
Solution
Hi guys,
Upgrading to the latest 4.7 version did fix the problem. Here are the details of how I came upon the solution -- http://drupal.org/node/191274#comment-630426 .
Thanks a lot for your help! :)
http://PinoyTechie.com | http://PinoyFilm.com | http://FilipinoWriter.com | http://WriteLit.com
http://PinoyTechie.com | http://PinoyFilm.com | http://FilipinoWriter.com | http://WriteLit.com