Closed (fixed)
Project:
Drigg
Version:
5.x-1.24
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Apr 2008 at 06:35 UTC
Updated:
29 Apr 2008 at 08:52 UTC
Hi,
I've updraded to Drigg 24 on my main _live_ site, which used to run on 23.
Clicked on updrage.php ... everything went fine there.
Then the problems started ocuring:
It gave me a WSOD:
Fatal error: Cannot redeclare drigg_embed_contents() (previously declared in /home/example/public_html/sitename/sites/all/modules/drigg/drigg/legacy_and_missing.inc(89) : eval()'d code:4) in /home/example/public_html/sitename/sites/all/modules/drigg/drigg_embed/drigg_embed.module on line 297
Checked drigg-code.org for documentation, or to see if I need to change anything in my node-drigg.tpl and page.tpl, but nothing new there.
Please help! This is urgent, my live site is broken because of this upgade.
Comments
Comment #1
drupalina commentedIt also told me to enable drigg_ui module, which cannot be activated untill the META base module is activated.
After I try to activate META base, if gives me a WSOD (white screen of death):
Fatal error: Cannot redeclare drigg_ui_sections() (previously declared in /home/example/public_html/sitename/sites/all/modules/drigg/drigg/legacy_and_missing.inc(89) : eval()'d code:4) in /home/example/public_html/sitename/sites/all/modules/drigg/drigg_ui/drigg_ui.module on line 654
Comment #2
mercmobily commentedHi,
The module probably has problems if the site is not in the root directory.
So:
1) Keep trying to enable to module. It will give you a different error each time... enable one extra module at a time
2) If 1) fails, open drigg/drigg/legacy_and_missing.inc and delete outright:
drigg_legacy('drigg_embedded_contents','drigg_embed_contents');
drigg_legacy('theme_drigg_sections','drigg_ui_sections');
drigg_legacy('drigg_get_view_type_menu','drigg_ui_type_menu');
drigg_legacy('drigg_get_order_menu','drigg_ui_order_menu');
drigg_legacy('drigg_get_article_menu','drigg_ui_article_menu');
drigg_legacy('drigg_get_submit_button','drigg_ui_submit_button');
drigg_legacy('drigg_related_links_get_html','drigg_rl_related_links_get_html');
drigg_legacy('drigg_get_promote_string','drigg_promoted_string');
drigg_legacy('drigg_get_created_string','drigg_created_string');
However, you will need to fix your theme very quickly because the "missing" functions won't work anymore.
Keep trying to enable the extra modules, however, and things will work!
Merc.
P.S.
Leave this issue open, I need to fix th upgrade procedure
Comment #3
drupalina commentedhi... you're right... I kinda panicked too early, but eventually got my head around it.
With an exception of one "Stop script" incident while enabling drigg-promote module (I'm not sure if it will have repercusssions later), everything else seems to have gone ok...
FAO everyone else who will be upgrading from 23 to 24; here's what I did:
After you run the upgrade script, remember that now Drigg is split into different functionalities in different folders... so not all functionalities will be there by a default upgrade. You will need to go to your modules and enable them.
Don't enable them all at one. Do one at a time!!!
Make sure that you do all this while in the drigg_theme!!!
When you enable each module, you are most likely to get a WSOD, like the ones that I described above. Don't panic! Click on the "Back" button, and activate another part of drigg module... and so on, back-and-forth, untill all your desired modules are enabled.
After you've evabled all these different drigg sub-modules, run the update.php once more.
This is when I got the message:
Once you do this, you will start getting warning messages about how each function has been renamed. Open your page.tpl and node-drigg.tpl files and carefully rename each function as per instructions.
(Afterwards, don't forget to disable theme caching and press F5... and those messages would have disappeared)
PS: Thanks Merc for yet another release of this great module.
Comment #4
mercmobily commentedHi,
Ugh. I've spent ages trying to replicate this, and I couldn't. I thought it was caused by Drigg nor being in the root directory, but nope.
So I don't know what's happening there.
Well, it will go well _most_ of the time. If it doesn't, it just needs a little bit of "hammering"!
It's basically a complete rewrite. So, it's probably understandable...
Merc.
Comment #5
mercmobily commentedComment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.