Login to admin shuts down Apache

[doodlebee]

A new update - I deleted everything again (all files and directories, dropped the database again) and started over, this time with 1.3.0 - an older version. The sucker works just fine. My thinking was, I'd install the old version and try to upgrade instead.

Before I attempted the upgrade though, I decided to check out my Apache logs to see if anything weird was there. Wouldn't you know it, the same errors are showing up - but the older version is just overlooking it and continuing on, rather than completely shutting down Apache.

So, I've decided not to upgrade as of yet - I've been spending the entire day working on this to no avail. I now - apparently - have a working version, and I need to get started on this client's site. So it looks like - unless I cna get it figured out - I'm just going to have to hack the core files again to get rid of all the tables. Yuk. My work is cut out for me, I guess.

If I ever get this figured out, I'll post back. But hopefully someone else has some alternate suggestions before I start digging into the core stuff again!

[Kim]

This really sounds like a server issue of some sort. What are you using to set up your server?

[doodlebee]

Well, like I said in the forst post, I'm running Windows XP Home Edition, with Apache 1.3.34, PHP 4.4.2 and My SQL 5. It's a setup I've been using for a couple of years now, with no problems. (The MySQL 5 is an upgrade, as well as the PHP, from older versions - I did those upgrades least year)

I'm running other databases on this setup - I've got Wordpress, Joomla, Expression Engine, Mambo and a few other programs running with no problems. So if it's a server issue, I have *no* idea what it could be. This is the only program I've ever installed that's had a problem like this.

[DrByte]

During installation, on the "Admin Setup" page, what happens if you uncheck the "check for updates" box?

What happens if you rename the various .htaccess files under /admin and /admin/includes etc?

[doodlebee]

Hey Dr Byte :)

Uncheck the "check for updates" box didn't do anything - checked or not, it was screwed up. Renaming the .htaccess files (I mentioned I'd tried that before) only made the problem worse.

However, I have good news. I *did* figure it out - and I rechecked the documentation that came with the installation. Nothing is mentioned about this (not that I could find), so maybe it should be.

The two configure.core.php files needed to have the "read-only" status changed - the box needed to be unchecked so full access was given to those two files. (These files are located in "includes/autoloader/" and in "admin/includes/autoloader"). Someone mentioned to me that I should try to make the *folders* be fully accessible, but it turns out Windows will not allow you to change the read-only status on folders - only files. When I changed the status on those two files - holy crap it went slicker than snot on a doorknob.

So, for future reference (anyone who needs this!) when you're putting your installation on a localhost server, be sure those two files are NOT marked "read only". (Seriously, it turned out to be that simple!)

I'm going to to take some painkillers now. My head hurts from staring at the screen all day, my forehead hurts from banging it on the desk, and my back hurts from slouched-over sleuthing poses.

And by the way - thank God you all removed the tabled layouts! I could *cry* it makes my life so much easier! :)

Thanks for all the help :)

[DrByte]

That will certainly be a quandry when running Apache on Windows ... permissions options are very different in windows vs linux. (but you knew that :) )

Glad you got it sorted out !

[Merlinpa1969]

Dont the instructions say to rename the dist_config.php files and set the permissions to 777 read write execute

[doodlebee]

>>Dont the instructions say to rename the dist_config.php files and set the permissions to 777 read write execute<<

Yes, they do. but the files I had to change the permissions on weren't the "dist_config.php" files. The files I needed to change were "config.core.php". Now, if the "dist_config.php" file is the same thing, that wasn't made very clear in the instructions - it didn't say that they were the same file. So if they *were* the same file, I had no idea because nothing in the installation instructions alluded to that.

But it's cool - all sorted and now I can actually begin working. And I'm *still* psyched that the tables are gone! Woo-hoo!