with installed sweaver 1.1. and activated custom css plugin do in drush:

drush dl sweaver-7.x-1.3
drush cc all

yields

Fatal error: require_once(): Failed opening required '.../sites/all/modules/sweaver/plugins/sweaver_plugin_customcss/sweaver_plugin_customcss.inc' in .../sites/all/modules/ctools/includes/plugins.inc on line 855

and will do this on any request so setting high prio.

CommentFileSizeAuthor
#2 1548428.patch1.78 KBAnonymous (not verified)

Comments

geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented

quickfix for the suffering:
* drush dl sweaver-1.1
* goto mysite/admin/config/user-interface/sweaver/plugins and deactivete custom css plugin
* drush up

looks like the update script comes too late when the missing plugin already wsod'd:

function sweaver_update_7100() {
  variable_del('sweaver_plugin_status_sweaver_plugin_customcss');
  variable_set('sweaver_plugin_status_sweaver_plugin_advanced', true);
}

so i propose to add an empty file where the plugin is expected as an upgrade path.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Patch (to be ported)
StatusFileSize
new 1548428.patch1.78 KB

Thanks for the notification. Update functions are actually called but there is a mistake in one of them. I should have rebuild the registry after 7100. I pushed the patch.

However if you have already downloaded a higher version than Sweaver-7.x-1.1 then you are stuck. That is why I created a patch for you. Apply it only if you have a fatal error after updating Sweaver.

lyyyn’s picture

lyyyn commented

Hi,

I am sorry, I am using Drupal 7.15 and just install the Sweaver http://ftp.drupal.org/files/projects/sweaver-7.x-1.3.tar.gz.

Now my site cannot be accessed at all.

Previously, I did:
1. SELECT name,status FROM system WHERE type='module';
2. UPDATE system SET status='0' WHERE name='module_name';
3. DELETE FROM dr_cache_bootstrap WHERE cid='system_list'

as I tried to disable the module manually. It didn't work.

I still got the error:
"Fatal error: Cannot redeclare class InsertQuery in /home/lyyyn/public_html/bisakita.com/includes/database/query.inc on line 727

Fatal error: Class 'MergeQuery_mysql' not found in /home/lyyyn/public_html/bisakita.com/includes/database/database.inc on line 826"

I come to this page and saw the the patch. Unfortunately I have no idea what to do with patch.

Could you please kindly advise?

It's a live website (www.bisakita.com) that I accidentally ruined.

Please help.

Thank you very much,

Lina

enzo3946’s picture

enzo3946 commented

lyyyn How you fix it? the site is online now...... I have the same problem:

"Fatal error: Cannot redeclare class InsertQuery in xxxxxxxx/includes/database/query.inc on line 727

fadrupal’s picture

fadrupal commented

I too when upgrading from 1.1 to either 1.2 or 1.3 get a site crash. Here is my error message

Fatal error: Call to a member function show_editor() on a non-object in /home/quickstart/websites/[my website]/sites/all/modules/sweaver/sweaver.module on line 586 Call Stack: 0.0032 329140 1. {main}() /home/quickstart/websites/[my website]/index.php:0 0.0055 389788 2. drupal_bootstrap() /home/quickstart/websites/[my website]/index.php:20 0.1466 1249484 3. _drupal_bootstrap_full() /home/quickstart/websites/[my website]/includes/bootstrap.inc:2198 0.2263 2658916 4. menu_set_custom_theme() /home/quickstart/websites/[my website]/includes/common.inc:5117 0.2263 2658960 5. menu_get_custom_theme() /home/quickstart/websites/[my website]/includes/menu.inc:1769 0.2264 2659300 6. module_invoke_all() /home/quickstart/websites/[my website]/includes/menu.inc:1747 0.2290 2665728 7. call_user_func_array() /home/quickstart/websites/[my website]/includes/module.inc:857 0.2290 2665920 8. sweaver_custom_theme() /home/quickstart/websites/[my website]/includes/module.inc:0 0.2291 2665920 9. sweaver_show_editor() /home/quickstart/websites/[my website]/sites/all/modules/sweaver/sweaver.module:397

Quentin, how do you apply that patch?

fadrupal’s picture

fadrupal commented

By the way, as a follow up to my post above, Custom CSS plugins is not enabled prior to upgrade, but after upgrade the site crashes anyway. Any suggestions please?

fadrupal’s picture

fadrupal commented

It appears that, in my situation, upgrading Sweaver from 1.1 to either 1.2 or 1.3 breaks my site, regardless as to whether Custom CSS plugins is enabled or not.

However, if I recreate the site from scratch in a development environment and run a 'drush up' before opening the site up for the first time (i.e. accessing the site for the first time), the Sweaver upgrade will go smoothly.

From there I can just push the upgraded site from development into production and solve the problem without having to patch the module.

For anyone who might find this approach useful.