Search results

I am not a RoR expert at all, but from a generic programming point of view, the route matching algorithm should try to match the longest path when possible, maybe change the routing configuration order can help.

Please download our latest 3.3.5 build see if works, just change the version number in the download link.

We have updated our default httpd_config.xml for cPanel installation, to write error log to /usr/local/apache/logs/error_log, so, it should work out of box.

http://x3demob.cpx3demo.com:2082/frontend/x3/index.html check the "Error log" button under "Logs" section.

something like "error log" as I remember.

All should work well with the latest PHP LSAPI release.

Those are three most popular control panel, all work well with LiteSpeed now. The choice for you is pretty much depends on your preference, server resource usage and panel functions. You won't go wrong with either one.

They should be able to override PHP error_reporting configuration in .htaccess with "php_value" directive. It should be off globally. cPanel can view error log for each vhost. should have a button available.

Please monitor the LSWS realtime status report, if "WaitQ" > 0 consistantly, you may consider up the "PHP suEXEC Max Conn" from "10" to a little higher value. Default LSWS configurations are pretty optimized.

If you mean displaying error in user's browser, you need to check a phpinfo page to make sure php configuration has been set properly. If you want to user view PHP errors in cPanel, you need to change the location of error.log to /usr/local/apache/log/error_log, where apache place its error log.

OK, will do.

That's the top three control panels supported by LiteSpeed, all should be fine.

http://www.litespeedtech.com/docs/webserver/config/listeners/#listenerBinding

OK, I see, we could make the log configuration in the main httpd.conf the default for all vhosts. Does all vhost log to the same log file in your setup?

Are you using a control panel? or a customed one.

some PHP modules does not match the current PHP verison, so, you need to rebuild your extra PHP modules as well, like memcache, etc.

Yes, or, you can make a backup of the configuration file before mess around. :)

You can add 404 custom error page for that vhost.

I don't think it is the rewrite rules in .htaccess. requests to admincp should not be rewritten. You can turn on rewrite log by adding "RewriteLogLevel 9" for the configuration in that vhost in httpd.conf. Then you can check lsws/logs/error.log. strace the lsphp process is the way to find out...

That's what in our cPanel+LiteSpeed wiki. :)