The name .htaccess refers to the main configuration file for Apache, a popular web server, as well as WordPress. Some design tools utilize .htaccess to enable websites based on them to function correctly. .htaccess can also be used to manage website behaviors like redirecting traffic for a page (e.g., a 301 redirect) or shortening the URLs for pages (URL rewrite).

.htaccess is accessible in Turbify Web Hosting through the cPanel File Manager.

Jump to:

• Accessing .htaccess
• .htaccess configurations for Turbify design tools
  • Website Builder
  • Site Solution

Accessing .htaccess in the File Manager

1. Sign in to your My Services page.
2. Click the Web Hosting link.
   
3. Click the File Manager link in the Files module. A new browser tab opens to the File Manager.
   
4. Click on Settings in the top right corner.
   
5. Check Show Hidden Files. Then click Save.
   
6. Go to the public_html directory. A file named .htaccess will now be visible in the file list.
7. Right-click on .htaccess. In the context menu, click Edit.
   
8. When finished making changes, click Save Changes to save the file.

Note: Turbify has a limited scope of support for .htaccess. We can assist with accessing it in the File Manager. However, we cannot provide support for the customization of your site using .htaccess. We encourage you to explore this technology and use what you are comfortable with. However, troubleshooting and resolving any resulting issues are your own responsibility.

.htaccess configurations for Turbify Design tools

Certain design tools utilize .htaccess to enable websites based on them to function correctly. In Web Hosting tools supplied by Turibify, this includes the current tool Website Builder and sites created in the retired Site Solution tool. In some cases, manually editing .htaccess is necessary to either enable the use of a website based on those tools, or when moving away from that site to a different tool.

Important: These configurations are provided as is. Turbify support can assist with the complete addition or removal of the code provided, but cannot provide assistance with modification or customization of the code.

Enable or disable Website Builder as the Homepage

When publishing a Website Builder based site, a configuration is added to .htaccess. This configuration allows the website files to be accessible. If switching between design tools, it may be necessary to modify .htaccess to enable or disable the Website Builder based site as the homepage.

To enable Website Builder as the homepage:

1. Follow the instructions above to access .htaccess in the public_html directory.
2. Add the following configuration to the top of the file. Then Save Changes.

To disable Website Builder as the homepage:

1. Follow the instructions above to access .htaccess in the public_html directory.
2. Remove the following configuration from the file. Then Save Changes. 

RewriteEngine on 
RewriteCond %{DOCUMENT_ROOT}/.websites%{REQUEST_URI} -f 
RewriteRule ^(.*)$ .websites/$1 [L] 
RewriteCond %{REQUEST_URI} ^/$ 
RewriteCond %{DOCUMENT_ROOT}/.websites/index.html -f 
RewriteRule ^(.*)$ .websites/index.html [L] 
RewriteCond %{REQUEST_FILENAME} !-f 
RewriteCond %{REQUEST_FILENAME} !-d 
RewriteRule ^(.*)$ $1 [L] 

Enabling or disabling Site Solution based pages as the live site

When the Site Solution tool was retired, a configuration was added to .htaccess for websites based on the tool. This configuration allows links to Site Solution based pages to resolve without the .html file extension. If switching to a different design tool, it may be desirable to modify .htaccess to enable or disable this behavior.

To disable page links loading without the .html file extension:

1. Follow the instructions above to access .htaccess in the public_html directory.
2. Remove the following configuration from the file. Then Save Changes.

To enable page links loading without the .html file extension

1. Follow the instructions above to access .htaccess in the public_html directory.
2. Add the following configuration to the top of the file. Then Save Changes. 

RewriteEngine on
DirectorySlash Off
RewriteCond %{REQUEST_FILENAME}\.html -f
RewriteRule ^(.*)$ /$1.html [NC,QSA,L]