This forum is for questions about upgrading an existing Drupal site. Don't forget to read the UPGRADE.txt file that comes with every Drupal download.

Update Failure

Has anyone else had problems with the module updater system?

In the last couple of weeks, and using 7.26 version of drupal I had a complete failure with my databases and perhaps my files on my remote server have been corrupted.

Talking to 1and1 restoring backed up files they pointed to the Entity API modules as being the cause - but they do not claim to be experts in Drupal

Now I've up dated to drupal 7.27 and now Entity API wants me to update to 7-15 so I'm nervouse

Is this just a problem with my system or is it more common

Webform Detection

Since I upgraded to 7.27, I now have 3 different page types that ('may') have a webform attached to it (while previously I had only one, which is correct). Why is that? Not a big deal, but I don't see why it can't properly detect.

Error after failed updated to 7.27

Most of this stuff is a bit over my head. I'm mostly deal with HTML and CSS. I tried updating from 7 something to 7.27. I now get the following when I enter my url:

Warning: require_once(/home/content/12/10104912/html/includes/common.inc) [function.require-once]: failed to open stream: No such file or directory in /home/content/12/10104912/html/includes/errors.inc on line 62

Token replacement not working

We recently upgraded our site from Drupal 6 to Drupal 7. We were using auto-nodetitle on D6, and it was working great. When we did the upgrade, I added auto-nodetitle again, but it doesn't work. Instead of replacing the tokens correctly, it simply saves the token text as the title - [field_first_name-formatted] [field_last_name-formatted] instead of John Doe. I can't figure this out for the life of me.

Core modules in /sites/all/modules - Now what?

While upgrading from 6.29 to 6.30, a friend mistakenly placed the core modules in /sites/all/modules. He ran UPDATE.php and all seemed well. Earlier this week he upgraded to 6.31, this time placing the core modules in their correct location. Now, no matter what he did, the site wouldn't budge from 6.30.

I asked him to delete the 6.30 core files in /sites/all/modules but now the site is down with an error message:

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal