Trouble with PDO setup on Host

They should be able to update that for you so you can focus on other issues, if not let me know.

My account was migrated to another machine which has different processors and does not exhibit the same bug.

Now I am getting further, seems PDO is working. However, I can't access the manager at all. I get a blank screen. Pretty sure I've updated all the critical paths in the config files and db. Cache is empty.

When I hit the site root (home page), it does a redirect to the blank manager page.

I can run setup, but can't complete it. After the language screen, I click "next" to continue and get a blank screen with this url: /index.php?action=options. ModX is not creating an error log.

I've set all folders to 755 and files to 644. I am trying to run with fastCGI now instead of suPHP. This seems like a permission issue to me...do permissions need to be set differently with fastCGI?

-Brian

Yes, if you are running PHP using DSO you will need to use 666/777 instead. If you want I have a command you can run to automate that.

Personally I would recommend using suPHP instead, far less headaches in the long run (especially if you are reselling on the server).

DSO is great for single site servers.

No, not running DSO but fastCGI instead. I don't think they are the same thing?
http://boomshadow.net/tech/php-handlers/

We will not be sharing hosting accounts, it's just for our sites. The reason I am trying fastCGI instead of suPHP is so that I can enable PHP caching via eAccelerator. It's not compatible with suPHP. But this is new to me, I've only run suPHP in the past.

-Brian

I don't see a FastCGI option, so I am guessing you mean CGI. If this is the case I would recommend changing to DSO as you will get better performance. The permission for CGI should be the same as with DSO tho if you want to move forward with that method.

If you are having load issues with suphp, you might want to look into CloudFlare. Granted any reasonable server running phpsuexec should support at least 115k monthly traffic without a problem. If you have less traffic than and problems, you want to take a good look at your provider/vps as something is very wrong imo. (At least if you are running MODX sites... A Wordpress site on the other hand, you will run into issues around 25k with heavy caching in Wordpress)

Your results may vary depending on the site and configuration, but that's my rough mileage...

"fcgi" is an option for PHP 5 handler if you build it in with EasyApache.

After continuing to get a blank screen for manager and setup next step I decided to go back to what I've used in the past : suPHP. I set this as the handler and set permissions to 644/755.

Problem was the same. If I renamed the core/config/config.inc.php file, I found that setup would continue to the next install screen. That keyed me in to the config file. I think the culprit is a very secure db password that contains a lot of special characters. I've changed the pw and now everything is working without even having to run setup.

Now I am going to try to get fcgi and eAccelerator working.

-Brian

That makes sense, why would I build something in if I don't use it. Good to know for future reference.

In regards to the password if you had a " or ; that would likely kill things, granted you should have gotten a database connection error. The other special characters (for the most part) are fine to use. Those two tend to break things.

Best of luck getting fcgi/eAccelerator working!