By default Limb should just work with these Apache settings, however this step seems to be the most difficult one for Limb beginners.

All Limb application processing logic is done via PROJECT_DIR/root file, thus it must be of application/x-httpd-php type. The most common error is that PROJECT_DIR/root doesn't seem to be executed with PHP. There're several possible answers in this case:

This usually happens when you can't override Apache directory settings with .htaccess file(Apache AllowOverride option is responsible for that). You MUST have «AllowOverride All» for Limb based projects somewhere in httpd.conf. Ask your hosting provider or fix it yourself. Why do you need that? .htaccess file of the Limb based project has the following lines:

<FilesMatch "^(root)$">
  ForceType application/x-httpd-php
</FilesMatch>\\

It makes the root file PHP executable. At this moment there's nothing you can do if you can't set «AllowOverride All» for your project.(however we plan to implement support for root.php/path1/path2 urls in the future versions of Limb)

If you're running Apache 2.0 make sure that you have «AcceptPathInfo On» directive in .htaccess in FilesMatch section:

<FilesMatch "^(root)$">
  AcceptPathInfo On
  ForceType application/x-httpd-php
</FilesMatch>

It's not included by default since it raises 500 server error on Apache 1.3+.

This also can happen if you have PHP running as a CGI executable not as an Apache module, in this case you can use mod_rewrite module: replace YOUR_PROJECT_DIR/.htaccess with YOUR_PROJECT_DIR/.htaccess-if-rewrite. That should do the trick.

Seems like root works fine yet you get the blank page every time you try to access Limb based project?

First of all make sure that you've checked the following list of possible errors that may cause this:

• Check that you're using an appropriate version of PHP for this Limb project. PHP 5.0.x series crashes sporadically with PHP 4 compatible code on Win32 platforms, yet PHP 5.1-dev seems to work much better.
• Check logs in YOUR_PROJECT_DIR/var/log/ directory. You can find three types of error log files there: error.log, warning.log, notice.log. Read them carefully, the reason of the possible error is usually clearly stated there(especially in error.log)
• Check your DB settings thoroughly
• Check your file access settings for YOUR_PROJECT_DIR/var directory - it MUST be fully accessible with your Apache server.

Every time you try access the admin part you get the same login page even when you input proper login/password?

We hope you've really made sure you have proper access rights for the part of the site you're trying to reach. This sort of error is known to happen in IE when you're trying to access the Limb based project locally. Make sure the domain name has no «_» symbols - somehow IE has problems with cookies for such domain names(and probably it's correct since such domains don't conform to RFC). Thus the host named «limb_demo» may cause login error, just rename it to «limb-demo» or something else.