I'm trying to resurrect a 4.7 site that I has both a core installation and several modules in need of upgrades. It crashed while someone was in the midst of uploading content; afterward, the webhost limited access because the site was chewing up a bunch of its server resources. The webhost described the problem thus: "We have made an extensive investigation to find the root causing the issue. It seems that there is some kind of problem with the php script index.php. This script is running too long on the server and is causing the excessive load."
Here's the situation:
- The site had about 20 pieces of content added since the middle of September, but none of that content had been backed up (yes, I know). Since the content was edited online, we don't have final versions of these files stored anywhere else. (Again, yes, I know.)
- We do have backups prior to that.
- We had to post 5 or 6 new pieces of content before the end of this week; then no new content will be posted until midJanuary.
- I probably should explain that I'm not a Drupal expert nor an effective web troubleshooter. I do this on a donated, part-time basis when I have time to help out.
- After the problem surfaced, I pulled a database dump and downloaded the old site to my Mac.
- Since all of the previously uploaded content served only archival purposes on this low-traffic site, I chose to shift the existing, problematic drupal installation into another folder in the directory and create a new 5.x installation just to get the few new bits of content online. Since we're talking about maybe a total of 6 pieces of new content, I figured it would be easier to do a clean install to get someone online for a week or so, and then spend the rest of December salvaging/upgrading the old installation. Once that was fixed, I'd upgrade the old site to 5.x and simply enter the new 5 or 6 pieces of content so nothing is lost.
So that's were I stand. Could this be something as simply as replacing the index.php file? Also, I would prefer to try to fix this offline rather than risk having the webhost suspend access to the new installation. I'm working on a Mac ... what would be the best way to troubleshoot this offline?
Comments
_
More than likely nothing will be solved by simply replacing the index.php file but it's quick so it can't hurt to try (could be corrupted).
My first impulse would be start over on a fresh d6 install, but assuming you don't want to do that, this is what I would do if it were me:
1. restore the old site from the most recent backups you have. You'll need both the db and the files. Verify it's working and make a backup.
2. upgrade that site to d5. again, verify it's working and make another backup.
3. upgrade the d5 version to d6. Yes, again, verify it's working and yes, make another backup.
4. add the new content.
5. finally, go back to the database and see if you can salvage the content from september. Assuming its nodes, the actual html source of the content will be in the node revisions table-- if nothing else you should be able to copy & paste it no problem.
And yes, you can do all your work locally on a mac or any other computer you have handy, no problem.
how to upgrade
I have a similar need to upgrade from 5.x. to 6.x. My old ISP was 5.x. my new ISP is 6.x. How do I fix my files from 5.x that includes theme and modules. How do you verify the versions of the themes and modules?
Thanks!
Kurt
_
This is really an unrelated post but you can use the d5 update_status module to see the version and project page links for the modules you have installed.
As for upgrading, see http://drupal.org/upgrade.
hi
I can fix it .kindly contact me at [contact info removed]
_
Please stop soliciting jobs in the forums. Thanks.