Closed (fixed)
Project:
Image
Version:
6.x-1.0-alpha1
Component:
image.module
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
13 May 2008 at 08:18 UTC
Updated:
2 Nov 2008 at 22:58 UTC
I've just upgraded to 6.2 and all seemed fine but when i started upgrading my modules and turning them on I ran into problems.
I narrowed it down to Image. If I enable it all seems fine and page looks good but when I try to go back into the admin pages I get the following:
Fatal error: Call to undefined function: image_gd_check_settings() in /home/sites/kamonjj.co.uk/public_html/includes/image.inc on line 70
Comments
Comment #1
trefor commentedJust reitterate page looks fine but with image enabled I cannot access admin pages. I was able to go go back to the admin page and using browswer back button to disable image and then access admin once more. I tried this several times with various combinations of modules and even with none but Image enabled I still get this problem. Does anyone have any ideas?
Comment #2
Hetta commentedmarked http://drupal.org/node/257835 as duplicate
Comment #3
trefor commentedHi Hetta Should I delete one of them? Can I delte one of them?
Comment #4
Hetta commentedMarking as duplicate removes an issue from the active queue. I've marked the other issue as duplicate ...
Comment #5
cougar88 commentedI deleted image modules, seems work fine until i wanted to change my image,
then comes the error again.
Fatal error: Call to undefined function image_gd_check_settings() in /home/myuser/public_html/includes/image.inc on line 70
Comment #6
trefor commentedI've noticed that if you try and bypass the admin page by typing in for example mysite/admin/modules/
then you can access the admin section but if you go direct from the front page youstill get the error.
Can anybody help with this?
Comment #7
tarek commentedThis issue was solved for me by copying the image.imagemagick.inc from the "image" directory in modules to the "includes" directory.
tarek : )
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #9
markthecarp commentedThis worked for me on an upgrade from 6.5 to 6.6.