Hi everyone. I'm really, really clueless about the error I encounter whenever I activate the Imagefield module. As soon as I do this my drupal site (midshipman.org) stops working completely. I just get a blank site with no error messages at all. I don't even know where to begin looking for errors (didn't find any php errors in the Apache log files). I have to deactivate the module by modifying the system table manually. Can anonye give me hint on how to fix this?
I had this once with another module and never found a solution so I just didn't use it. But imagefield is far too important to _not_ use it.
Any help would be appreciated.

Comments

mwille’s picture

mwille CreditAttribution: mwille commented

I have to correct myself: my site crashes as soon as I try to add a new imagefield to my blog content type.

dopry’s picture

dopry CreditAttribution: dopry commented
Status: Active » Postponed (maintainer needs more info)

memory limits? don't know... You're gonna have to make the error logging more verbose and visible.. There should be something in the error logs or in watchdog...

cookr1965’s picture

cookr1965 CreditAttribution: cookr1965 commented

Having the same problem....only I wouldn't call it crashing the site. When trying to create a new imagefield, all I get a blank screen that I have to back out of. Checked the logs. PHP log returns:

PHP Fatal error: Cannot redeclare date_token_list() (previously declared in /Users/cookr/drupal/sites/all/modules/date/date/date.module:361) in /Users/cookr/drupal/sites/all/modules/token/token_cck.inc on line 226

Not really sure whats going on here because I don't understand token integration, but if I comment out all instances of tokenized paths from the imagefield module, the problem disappears. Instances are on lines 244, 450, 603, and 741. not sure how this will effect other modules though and I know its not a fix, but hopefully this points someone in the right direction.

dopry’s picture

dopry CreditAttribution: dopry commented
Title: Imagefield crashes site » Token_cck conflicts with recent date.module.... Remove date_token_* from token_cck.inc.
Project: ImageField » Token
Version: 5.x-2.0-rc8 » 5.x-1.x-dev
Status: Postponed (maintainer needs more info) » Active

umm the version of date.module you're using conflicts with the version of token you're using...

token needs to be updated and needs to stop trying to provide tokens for other modules and leave their integration up to them.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
CreditAttribution: greggles commented
Status: Active » Closed (duplicate)

Take your pick of the duplicate for 5.x/date #206649: Update Date code in Token module for API changes in Date 2.x or for doing this in general for 6.x #231323: remove token_cck.inc after cck module copies it into their module.

Token 5.x-1.11 was released specifically to address this.

If other cck modules are implementing their own token hooks in 5.x and then we need the same "if function_exists()" kind of logic, but I'm not aware of other 5.x cck modules which do this.