Can't find image toolkits errors
| Project: | ImageAPI |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I'm continually getting this error from the status report page and (a similar one from) the image api settings page, and I don't know why.
"ImageAPI Toolkit -No ImageAPI toolkits available
ImageAPI requires a Toolkit such as ImageAPI GD or ImageAPI ImageMagick to function. Go to admin/build/modules and enable one of them."
This has just cost me hours, and I've got no resolution and no idea. I've tried tracking through the code, but for some reason imageapi.module fails at line 120.
foreach (module_implements('imageapi_toolkit', true) as $module) { // nothing happens :( }Obviously the GD and ImageMagick modules are there. GD was installed, everything was ok the other day, but I cannot undo this problem or find out what's causing it.
This is with :
ImageAPI 6.x-1.3 AND dev
ImageCache 6.x-2.0-beta8
ImageField 6.x-3.0-alpha4
I tried with the dev versions, and even rolled IC back to b6 but nothing works. I get this error every time. :(
#1
Did you enable the imageapi gd module though?
#2
Well... yeah :)
ALL the modules were enabled, but the error persisted.
#3
you ever figure this out?
#4
Nope :( It's still lurking in the site, no ideas/clues...
Edit: are there any environment variables, checks, server things I could look for?
#5
Daym, baby. Updated to 6.10 and it just went away. No idea...! :/
Who cares, I guess?!
#6
I just updated from 6.13 to 6.14 and now i have the same problem above. Worst is I can't activate/enable ImageAPI GD2 and ImageAPI ImageMagick Toolkit. Everytime I checked their boxes and press save configuration, it will just reload the page again and the two boxes unchecked again. I can activate other modules with no problems though. It was not like this before the update. Does this means that the two toolkits for Image API has problem with drupal 6.14?
#7
nevermind... I found the problem... It's a fault in my part! ^_^ I overwrite my customized .htaccess with the default one included in the drupal zip file. I just customized it again and everything is back to normal ^_^