Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By stevem-1 on
It's now driving me mental. I'm passed wit's end, so forive my rambling post ...
Image module. I've installed it. Here's what I know to be true:
I have gd installed and enabled. admin/settings says it's working correctly. I'm running on FreeBSD 4.10 RELEASE. I'm running in Apache 1.3. I'm running under php 4.1.3.
I have tried changing filemanager settings from public to private and back again. I've tried with and without clean urls.
I've tried uninstalled the image module and deleted the relevant image_* fields from the variables table using phpadmin. I've reinstalled image again. I've followed what instructions there are carefully. I've set permissions on files and images to 777 and 755 alternately with no difference. Same for my private and temp directories.
I've created a gallery. I've made sure that the Image Galleries vocab is set to "multiple select" and "required".
Here's what's happening...
I upload an image, and I get an internal server 500 error. The image file is complete and stays in images/temp. No node is created. If I attempt to create na image node with no image, the node *is* created. If I then try to edit the node, and upload an image, I get the same 500 error.
There's nothing logged in the drupal log. I have no access to /var/log/*, so I can't check any server side logs. Is there something obvious I've overlooked? Any ideas on how I can troubleshoot this - I've been searching and trawling the forums for a week on this, and I'm desperate. Even Google (who knows all) has been fruitless.
At this point I'll be happy with just a different perspective to help me get to the bottom of this...
Any takers?
Cheers
Steve
Comments
Logging
Try to create a custom error log someplace in your
/homeusing an.htaccessdirective. Drupal's logging usually isn't as good as the httpd's logging when it comes to errors, I've found. Sure it can tell you there was a 404 and the last cron run completed and what nodes are popular, but I find that you can get more information, especially when something isn't working as it should.