Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Excited with the merge from cck phone ;) I uninstalled the previous module and went to the phone 2.x. , however...
Whenever I try to install the new 2.x dev branch of phone, I get a WSOD. (then I have to remove module from shell command).
I figured out that this is incompatible with Entity Translation 7.x-1.x-dev , if I disable entity translation, phone 2.x can be installed.
Comments
Comment #1
cdale CreditAttribution: cdale commentedCan you provide any information on what the error is? I just installed a clean drupal 7, enabled the dev version of entity translation module, then the 2.x branch of the phone module, and all worked fine.
Do you have information from your error logs as to what the actual error is that might help us track this down? It might be as simple as a cache clear that will fix this.
Comment #2
pedrospHi cdale,
Flushing caches before or even disabling caches didn't work.
Logs shows always the same error:
PHP Fatal error: Cannot access empty property in /all/modules/entity_translation/includes/translation.handler.inc on line 728
line 728: $this->entity->{$translations_key} = self::emptyTranslations();
Thanks!
Comment #3
cdale CreditAttribution: cdale commentedI think this is likely a problem with the entity_translation module. I can't replicate this, or even figure out how to replicate.
Assigning to Entity Translation project.
Comment #4
cdale CreditAttribution: cdale commentedThis might be a duplicate of #1370900: Fatal Error: Cannot access empty property in /sites/all/modules/entity_translation/includes/translation.handler.inc.
Comment #5
plach$translations_key
definitely should not be null as it is always defined. Steps to reproduce?Comment #6
pedrospI just bumped again today with this, impossible to have phone 7.x-2 dev and entity translation in the same installation.
Error WOSD (sometimes not inmediately but trying to add a new field) and as seen on drush:
WD php: Exception: Cannot initialize entity translation path variables (invalid path scheme). in EntityTranslationDefaultHandler->initPathVariables() (line 1449 of [error]
/var/www/mysite/sites/all/modules/entity_translation/includes/translation.handler.inc).
Drush command terminated abnormally due to an unrecoverable error. [error]
Exception: Cannot initialize entity translation path variables (invalid path scheme). in EntityTranslationDefaultHandler->initPathVariables() (line 1449 of /var/www/mysite/sites/all/modules/entity_translation/includes/translation.handler.inc).
Any tips ?
Thanks.
Comment #7
plachThe latest dev has a commit that might fix this or at least avoid the fatal error.
Comment #8
pedrospToday's test has been done with Last packaged version: 7.x-1.0-beta2+26-dev - Last updated: March 23, 2013 - 00:54
No luck :(
Comment #9
zxaos CreditAttribution: zxaos commentedI'm seeing this too with the March 23 version - disabling the Phone module caused the error to stop appearing.
Comment #10
cdale CreditAttribution: cdale commentedCan any one tell me how to reproduce this? I've tried installing phone and entity translation, creating a phone field, and nada, no errors. If I can at least reproduce it, I might have better luck tracking it down.
Steps to reproduce will need to be from a clean install, with as few modules enabled as possible.
Comment #11
plachClarifying title.