Backlight pages use clean URLs when run in Apache servers in conjunction with the mod_rewrite module and .htaccess files.
In most cases this should work without any need for further configuration. This page serves to document steps needed in the event that clean URLs are not working, or that your site fails completely with the .htaccess files
On launch, Backlight uses clean URLs in two ways:
You'll know that clean URLs are not working, if those URLs are parameter based, such as ?page=about, or single.php?id=image1234. There is no harm in your site creating URLs in this format. Backlight is designed to use this format if .htaccess files are not found, empty or not supported.
If your site is using parameter based URLs there are some steps to take:
We have made the .htaccess files shipped with Backlight as flexible as possible. However, there are some server setups that we can not cater for out-of-the-box. The 'No input file specified' message is one particular case. This is caused by your host's PHP being configured to run in FastCGI mode.
The main benefit of FastCGI is that it speeds up PHP execution. However, this mode changes the paths on the server, breaking our .htaccess files. Here are some options to resolve this:
There are two places to edit the contents of the .htaccess files.
Some hosts may disallow .htaccess files or certain directives within the files. Fixing this is beyond the scope of this article. One option is to locate your Apache error file and determine the underlying error. This file may be found via FTP, or via your cPanel.
As stated above, Backlight is designed to work without .htaccess files, albeit without clean URLs in certain locations. As such, removing or renaming the .htaccess file at the top of your site, and following the preceding steps for updating Album .htaccess files so that the field is empty, should solve any issues with .htaccess files.