Posted by IonEarth on June 1, 2011 at 8:05pm
How do I update my Drupal Core to 6.22 when using the Mercury 1.1 stack. I've been running Mecury on EC2 for about 6 months and everything has been great, but recently Drupal released Core patches for 6.20 that have security updates. I researched updating Pressflow using Bazaar, but I don't know if that's what I need to do and I don't want to hose my site.
Anyone updated to Drupal Core 6.22 that is using the Mecury 1.1/Pressflow setup?
Comments
Just run update_pressflow.sh
Just run update_pressflow.sh from the command line.
---
Tomáš J. Fülöpp
http://twitter.com/vacilandois
Ok, I'll give it a shot.
Ok, I'll give it a shot. Thank you Tomas!
Updated via Drush - problem?
Hey team - I'm new to Project Mercury and made the mistake of updating Drupal Core to 6.22 via Drush. Now there is a new folder under sites\all\moduels with the Drupal 6.22 core in it. If we try to remove that update we get:
Fatal error: require_once() [function.require]: Failed opening required 'sites/all/modules/drupal-6.22/modules/user/user.pages.inc' (include_path='.:/usr/share/php:/usr/share/pear') in /var/www/kyler/indiestudio/includes/menu.inc on line 347array(4) { ["type"]=> int(64) ["message"]=> string(199) "require_once() [function.require]: Failed opening required 'sites/all/modules/drupal-6.22/modules/user/user.pages.inc' (include_path='.:/usr/share/php:/usr/share/pear')" ["file"]=> string(44) "/var/www/kyler/indiestudio/includes/menu.inc" ["line"]=> int(347) } n/a
My developer says the site appears stable, but there are some misc errors. I'm afraid something is toasted or broken with Memcache, Varnish, etc.
I've setup a new VPS at Linode with a fresh install of Project Mercury in case we have to migrate over. Should I just have the dev migrate our data to ensure everything is cool? I'd rather not since it will cost money. Any tips appreciated!!!!!
Someone told me since
Someone told me since Pressflow is a drop in replacement, I should be able to just undo what i did via that route.
Does anyone have feedback on that?