By rcr1000 on
So, I followed all the readme instructions to upgrade to 6.13. When I got to /update.php, I get a full installation window with "Choose language" "Verify requirements," etc.
First of all, is this what should be showing up? It didn't sound that way from the readme.
Secondly, going along with this screen, it won't accept my database information. When I submit it, it just refreshes on the same page with emptied fields, though I'm 99% sure everything there is correct.
Can someone help me out here? I'm desperate.
Comments
=-=
sounds like you removed your original settings.php file. which is fine to do, however, when you do so you have to manually add teh information to setting.php $db_url so that 6.13 can connect to your database.
Okay, that worked (thanks),
Okay, that worked (thanks), but now I have two more problems. First off, I can't access the modules page. When I navigate there, I get a blank page.
Second, none of my images are being accessed. They are in the same directories that they used to be. The ones uploaded to nodes are no longer on the nodes, and the non-node ones aren't showing up either.
This may have something to do with the modules, but since I can't configure them, I'm stuck. Any advice?
=-=
blank pages are apache errors, check your apache logs. I'd assume you are runing out of memory on your host. Ensure you run update.php as well.
for minor to minor updates, you didn't have to disable modules as those versions will still work in all Drupal 6.x releases. the upgrade.txt does not differentiate between minor to minor and major to major, however it is geared toward major to major which is why it states to disable all modules. for a minor to minor this is an unnecessary step.
You also don't need to remove your sites/ folder as you have done and now permissions on teh folder are likely wrong. check them verses your backup, or your test site. Not sure how you prepared the upgrade. I never just do it on a production site without a test run on a test site.
I'm running this locally and
I'm running this locally and should have plenty of memory.
What do you mean by "check your apache logs"? How do I do that, and what should I be looking for?
=-=
running it locally does not instantly mean you have enough memory allocated to PHP in php.ini
what you are looking for is what error is being thrown and can't be printed to the screen before it dies. Typically it's an exhaustion of memory.
apache errors logs could be anywhere on your system above the public root, I don't know how you're set up. check your environment documentation. mine are in a folder called /logs
Hmm, a lot of stuff here, and
Hmm, a lot of stuff here, and I don't know what to make of any of it. Here are all the errors since 6.13 was implemented:
List of errors removed=-=
next time use pastebin and link to a list like that please.
check all permissions on sites folder. default folder default settings.php settings.php so on so forth.
and again I ask, did you run update.php?
Sorry about that. Re-pasted
Sorry about that. Re-pasted here: http://pastebin.com/m3c07624d
I did run update.php. I did it both times as stated in the readme. I've also done it twice since then.
Sorry to be so dense, but, again, I don't know what I'm looking for as far as the permissions go. I have default.settings.php and settings.php files, but what exactly do I need to check for in them?
Also, occasionally I get the
Also, occasionally I get the same blank screen for "Site building," which I think reinforces your suggestion that it's a memory problem. I wish I knew more about this stuff.
=-=
http://drupal.org/node/76156
Still not working. I even
Still not working. I even tried upping it to 64M just to be sure.
Now update.php won't run,
Now update.php won't run, either.
=-=
64M may not be enough depending on how many and which modules are running. imageapi, asks for 96M alone.
based on your issues, I'd use your back up and get back to a working 6.12 version and without disabling things and without removing your sites/folder I'd start over.
Okay, a few questions, and
Okay, a few questions, and I'll try not to bother you anymore. First of all, thanks for the help.
First, keeping in mind I know horribly little about php and memory issues, etc., is my needing so much memory likely to be a problem when I get this on a shared server? I know this can vary, but I'll be looking for reputable hosts ... if that helps at all. If it is a problem, what would be my other options?
Second, I raised my memory limit (using that instructions on that link you gave me) all the way to 256 trying it out, and my modules page still wouldn't come up. Does this sound right?
=-=
no 256 should be enough and you likely have other problems. shared servers can be a PITA with memory limits yes. limit the amount of modules you use.
I point back to likely file and folder level permissions issue somewhere. however, I can't be specific beyond files folder for example, should be CHMOD writable and readable. ie: 755, 775 or 777
Alright, well I won't bother
Alright, well I won't bother you anymore. I just tried reinstalling the whole version 6.13 without disabling any modules or anything, and I got the same problem. Is there some good service that you can pay to help troubleshoot issues like these? I know there's not a Drupal-endorsed one.
Solved:
Solved: http://drupal.org/node/507716