By JakeRogers on

Hi All and thanks for any advice or reference,
I am now having my site restored from a backup to 7.34 following a failed attempt to upgrade to 7.35. I did it manually and called myself following the exact instructions, except for the automated drush part. My upgrade was successful, BUT I no longer had any content and all my contributed modules were no longer enabled. All my prepped Views were gone...just the basic installation with ONLY the Admin user. Basically I:
- deleted all of Public_html EXCEPT for Sites directory, htaccess and robots.txt, which I copied out of the public_html.
- Uploaded 7.35, extracted, then copied ALL folder/files back to public_html
- Moved Sites directory, htaccess and robots back to public_html
- ran update.php

I go NO errors or red flags when checking StatusReport. Any ideas what I might have done wrong? Thanks for any help.
Jake

⋅ Categories: Drupal 7.x

Comments

VM’s picture

VM commented

sounds like a new database was used. Did you run update.php or install.php?

JakeRogers’s picture

JakeRogers commented

I ran update.php per instructions, NOT install.php. Do the above steps that I performed appear correct? Any advice on this 2nd go around?

Jake

VM’s picture

VM commented

I backup all files and folders
I backup .htaccess and robots.txt

I remove all files and folders except /sites/
I backup the database

I upload all files and folders from the new archive except /sites/
I compare new .htaccess and robots.txt for any changes and ensure those changes are in my master files.

I run update.php

JakeRogers’s picture

JakeRogers commented

2nd time around it worked fine. I did one thing DIFFERENT...rather than deleting Everything from my public_html folder (except as noted), I deleted them from the upgrade folder. I then dragged and dropped all the new stuff into the public_html and allowed it to overwrite what was there. This is MUCH less prone to error, and FASTER.

Jake

VM’s picture

VM commented

for future reference the overwriting of files when updated/upgrading is not a best practice. Files that are removed from a new version (rare but it has happened) will wind up being orphaned because they won't be removed. While this may not be an immediate threat, a file orphaned long enough can become a security issue.