Hi ,
I installed the new upgrades for the following modules.After updating the folowing modules, I am unable to edit story.
cck-6.x-2.2,filefield-6.x-3.0-beta3,imagefield-6.x-3.0-beta3,imagecache-6.x-2.0-beta8,imageapi-6.x-1.5. I am not sure which one of these is causing the problem.I guess it must be either imagefield-6.x-3.0-beta3,imagecache-6.x-2.0-beta8. Is there any way to revert back to earlier working modules, apart from using the backup sqldump, as I have few changes which I have not backed up.

Comments

wretched sinner - saved by grace’s picture

wretched sinner - saved by grace CreditAttribution: wretched sinner - saved by grace commented
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

Try disabling all the modules. Are you then able to edit story. Then try enabling them one at a time, to see when (if) it stops working. That will help narrow down the problem.

Also, do you get an error message when you try to edit? If so, what does it say? If not, what happens?

Are you trying to edit the Content Type Story or a created Story node?

shriya_atreya’s picture

shriya_atreya CreditAttribution: shriya_atreya commented

The problem was with the latest imagecache module. I could resolve it after disabling it.

wretched sinner - saved by grace’s picture

wretched sinner - saved by grace CreditAttribution: wretched sinner - saved by grace commented
Project: Drupal core » ImageCache
Version: 6.5 » 6.x-2.0-beta8
Component: install system » Code
Status: Postponed (maintainer needs more info) » Active

Moving over to the Imagecache queue then to see if they know what may have caused this, or if it is a reproducible error.

ngaur’s picture

ngaur CreditAttribution: ngaur commented

I think people are probably discussing the same thing as #402860: Fatal error: CCK data field not always unserialized. which has some code for correcting the database corruption, but I don't think it prevents the problem recurring.

I'm not sure which of these threads should be marked as a duplicate, or whether the problem is with imagecache, filecache, or CCK.

drewish’s picture

drewish CreditAttribution: drewish commented
Status: Active » Postponed (maintainer needs more info)

there's not much to go on here. i'd say update all your modules and re-open this if you can provide more detail.

fizk’s picture

fizk CreditAttribution: fizk commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)