Node edit page doesn't load for CCK types using imagefield
| Project: | ImageField |
| Version: | 6.x-3.0 |
| Component: | User interface |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
CCK version - 6.x.2.3
imagefield version - 6.x.3.0
permissions for your tmp and files directory - both file paths are set and validated
download method (public or private files) - Public
imagefield configuration - not sure what info required here. Only setting I could find was a path setting within a defined field for my content types.
expected results - node edit as normal, as can be done with content types NOT utilising imagefield
the unexpected actual results - node edit for each of several content types utilising imagefield don't load, giving a completely blank browser page..
Steps to reproduce the problem - by toggling imagefield module on and off, the problem comes and goes and is repeatable.
I have tried disabling javascript. This doesn't make a difference.
I have tried with Garland theme. This doesn't make a difference.
Thanks for input...
#1
A further comment: when I first noticed this issue, imagefield was not showing up in the Available Updates, even though it was in the modules list (I've used it with this site for a some time).
On inspection, I discovered that the imagefield module folder was half-empty, showing a couple of info field etc.. Thumbnails images and page images were still showing, but the node edit function was failing completely. Not sure how this situation could have arose.
I deleted that module folder and extracted a newly downloaded version of imagefield 6.x.3.0. Flushed all caches and updated the database. I expected that this would resolved the issue. Imagefield was now showing in Available Updates etc.
It did not resolved the issue. I am just wondering whether this may indicate a database issue, that is still effected by that previous setup.
Any thoughts?
#2
An empty white screen is always hard to debug. You should enable error reporting on your PHP installation so that PHP will actually report the error to you instead of just showing a blank white screen, then it's much easier to tell what went wrong. Usually this is done by setting
display_errors = Onin your php.ini file. You might also check watchdog at admin/reports/dblog, which might tell you what went wrong (but probably not since if PHP crashes Drupal can't log the error).#3
Thanks—good generic advice, which I'll bear in mind, even though I've now solved this issue, by re-installation.
#4
Closing since there's no way to know what the problem was and now it's been fixed.