Hi,
immediately after installing 6.x-2.0-beta1 and running update.php, I'm getting this fatal error when loading a (any) node:
Fatal error: Cannot use string offset as an array in /var/www/drupal/sites/all/modules/community_tags/community_tags.module on line 971
The same error is logges by watchdog:
ERROR:
Array
[type] => 1
[message] => Cannot use string offset as an array
[file] => /var/www/drupal/sites/all/modules/community_tags/community_tags.module
[line] => 971
The website is mostly broken (thus priority "crital"), but I can access the administrative backend without any trouble.
Disabling 'community_tags' and all submodules seems to help as a temporary workaround.
Greetings, -asb
Comments
Comment #1
asb commentedThis issue still persists for me. Are there any updates on this?
Comment #2
asb commentedThree months after posting a bug report about an critical issue that affects the whole Drupal site and no comment from the maintainers at all. Is this module still maintained?
Comment #3
chaps2 commentedComment #4
asb commentedWould you mind to elaborate about closing this issue? Currently not even a newer release than the horribly broken 6.x-2.0-beta1 from 2011-Mai-27 has been published...
At least for me this issue is absolutely not fixed so far...
Comment #5
chaps2 commented@asb - fix is in dev now. Sincerest apologies for any inconvenience and frustration caused...
Comment #6
asb commentedThanks for the new dev release. I updated community_tags 6.x-2.x-dev from 2011-Oct-25, enabled the core modules, and they doesn't kill the site anymore, indeed (drawback: so far, nothing related to community_tags seems to work, but this issue appears to be resolved). Closing.
Comment #7
Rhino-new commentedThis is a mystery. I had community tags working just fine, when I decided to try a new theme out. Upon selecting a new theme, the
log message appeared. Only certain admin pages could be accessed, everything else threw an error 500. I disabled community tags but am perplexed as to how I could have avoided this issue for s long.
My community tags is version = "6.x-2.0-beta1" so I'll try the dev-release.
Comment #8
asb commentedYes, the dev release probably will sove your issue.
Another thing is drush; it sometimes forces "upgrades" that actually are downgrades. Every now and then I get a WSOD, find this issue again, check the version and find out, that I'm running this crappy 6.x-2.0-beta1. Again.
It'd be really nice to push out a new stable release for the 2.x branch!