500 Internal Server Error

Quote from: Meristem at Sep 05, 2008, 08:54 AM

Can you point me to instructions for installing? I didn’t see them in the downloads area.

Start here: http://svn.modxcms.com/docs/display/revolution/MODx+Revolution

Quote from: Meristem at Sep 05, 2008, 08:54 AM

I changed the index.php to html because earlier in this thread it was suggested as part of troubleshooting.

I think you misunderstood. They were saying rename the index.php so an index.html would show up (assuming you have an index.html in the same directory).

I followed the instructions. I made sure that core transport wasn’t unzipped when I uploaded the files (Advanced)

I double checked that all the directories had the correct permissions.

How do I enable the PDO driver? Via my server cpanel?

Quote from: Meristem at Sep 05, 2008, 05:06 PM

I followed the instructions. I made sure that core transport wasn’t unzipped when I uploaded the files (Advanced)

I double checked that all the directories had the correct permissions.

How do I enable the PDO driver? Via my server cpanel?

For advanced, you need permissions to write to the root of the install location you specify for every context.  Not just what is described during install steps.

And see http://php.net/pdo for details on installation and configuration details for PDO.

I’ll check that out.

On another note I uploaded the regular alpha 3 and got a 503 error. Previously I was able to install alpha 3 when it was first released.

My host provider is installing the pdo drivers. I’ll let you know how it goes after that.

Meristem:

Glad to hear they are getting you a proper PDO configuration. Unfortunately, Revolution only works in systems without PDO completely, or in systems where PDO exists and the PDO_mysql driver is available. Systems with PDO, but without the PDO_mysql driver will need to run MODx in the emulated PDO mode (i.e. non-native). I’m working on an install utility to detect this situation and fix it automatically where possible.

Also, just a reminder, please be cautious deploying alpha software on live servers that you do not have full control over. That’s why we do not recommend using it on shared hosts in the alpha stage. This is in development, and though it will probably be fine, you never know what loose ends might be available for exploitation by those malcontents with nothing better to do with their life but try and undo what others have done, and most hosts won’t take kindly to you creating attack vectors on their servers. I’m not saying there are any in the Revolution code, but web security in PHP applications is anything but trivial and it would be best to "evaluate" the software on local testing machines that aren’t accessible, at least until beta.

I came across the same problem

Internal Server Error


With title 500 Internal Server Error

I actually came accross this problem when I’s trying to enabie SEF .
Renamed ht.access to .htaccess and modified it accordingly.

So does anyone know how to solve it???

Not without knowing your structure (MODx in webroot or subdirectory?) and seeing your modified .htaccess file.

Is it a local install or hosted? Some hosts don’t allow to use mod_rewrite rules in .htaccess files or .htaccess files at all. It will result as error 500. That’s probably what’s happening in your case.

Another possibility is a php config command in .htaccess. Some setups don’t allow this and you have to move the php commands (e.g. php_flag register_globals off) to a php.ini file.

Yet another possibility is that your host uses suPHP or something similar that requires the .htaccess and index.php permissions to be set to 644 rather than 666.