Closed (fixed)
Project:
ImageCache Actions
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Jan 2011 at 18:25 UTC
Updated:
13 Jan 2012 at 12:25 UTC
Jump to comment: Most recent
Comments
Comment #1
juliusvaart commentedI'm having the same problem when trying to add an overlay to a preset.
Comment #2
PMorris commentedSame error with me! I could only fixed by deleting the module with FTP tool which allowed me back into admin of site.
It's on a MAMP test server. This module is awesome. I use it to slice images into grids and add rounded corners automatically. Hope to see it running!
As a footnote, enabling the base module doesn't seem to give any errors but any of the others like Imagecache Canvas Actions do.
Comment #3
Countzero commentedSame kind of problem here when adding an underlay :
Fatal error: Call to undefined function imagecache_include_standard_actions() in ... sites/all/modules/imagecache_actions/canvasactions/canvasactions.inc on line 441
I also had to comment some function declarations in utility.inc because they were already declared elsewhere.
I'll investigate and post here if I make the thing work.
This module is amazing and I definitly want a working D7 version.
Comment #4
Countzero commentedJust commenting the faulty line leads to the same message about the imagecache_actions_keyword_filter function.
The first call refers to the non-core version of imagecache functions. I guess we have to find how they are called now that they are in core, hoping their implementations didn't change too much (EDIT : in fact, despite its name, this function was in the module utility.inc fiel in D6).
The second is a call to an imagecache_actions function which is not present in utility.inc, which was the case in the 6.x version.
Trying to debug this leads to includes looping hell : either the functions are declared two times or they are missing, alterning error messages of each kind depending on which code you comment.
I'm stuck.
Comment #5
Lobidu commentedSame problem. Just mentioning.
Comment #6
ccheu commentedsubscribing. yes, same issue. :p
Comment #7
cpaks commentedsubscribing.
Comment #8
teh_catt commentedsubscribing
Comment #9
zd370 commentedsubscribing
Comment #10
fuse commentedSame problem here.
Comment #11
d0t15t commented+1
Comment #12
Anonymous (not verified) commentedI got the WSOD as soon as I enabled any of the actions (the base imagecache actions are OK). Fixed it by renaming the offending include, then disabling the module & renaming the inc. file back to its original name.
You won't see an error message unless you turn on error reporting in your php.ini; remember to disable this afterward if you are in a production environment.
Comment #13
Countzero commentedI was trying to solve the problem (mean : prevent it to happen).
To restore your site to normal operations, you can simply delete the module's directory.
I'm still investigating to correct the problem and make the module usable.
Comment #14
Countzero commentedSee this issue for a related discussion and a working temporary solution : http://drupal.org/node/818798.
Comment #15
krak commentedsubscribe
Fatal error: Cannot redeclare hex_to_rgb() (previously declared in O:\home\mysite.ru\www\sites\all\modules\imagecache_actions\utility.inc:88) in O:\home\mysite.ru\www\sites\all\modules\imagecache_actions\utility-color.inc on line 123
Comment #16
dman commentedYeah, was bad dependancies - resolved here #1046200: Resolve the mystery of the hex2rgb functions
Comment #17
fultonchain commentedMore confirmation, another subscription.
Comment #18
Anonymous (not verified) commentedJust an update to my experience w/ this (see #12) — downloaded the 31 Jan '11 snapshot & enabled Auto-rotate & Custom Actions successfully. Canvas Actions & Color both cause WSOD. Haven't tried to use the module yet, however, so can't comment on functionality.
Comment #19
Fidelix commentedSubscribing...
Comment #20
Sentrashy commentedsub
Comment #21
fietserwinAFAICC this has long been solved, back in the 7.x-0.0 version. I.m using the module to its full extend in several sites now, without this problem... Cleaning up the issue queue, feel free to reopen if I'm wrong.
Comment #22
fietserwin