Troubleshooting Installation

If page edits are not saving or sub pages cannot be seen..

In the rare case you have some difficulty, this troubleshooting guide will help.

General issues

Here is a short video that shows the install process:  Pulse 4.0 Installation.


Content not saving

If you have trouble saving content or settings, check permissions on the content folder and the config.php file. As a general rule, permissions for folders should be set as 755 and files 644.


Content not appearing

Add a line to your .htaccess file

Some web hosts (1&1 etc) require the following line to be uncommented in your .htaccess file for your Pulse site to work correctly: 

RewriteBase /

And some others will require an extra line on line 1 of your .htaccess file instead of the above:

Options +SymLinksIfOwnerMatch

In most cases, even the majority of shared hosting servers, these steps are not necessary.

.htaccess file is missing

Some computers hide files that start with "." so the .htaccess file may not have been uploaded when you installed. In this case upload the sample.htaccess then rename to just .htaccess on your server.


Installing in sub-folders

As mentioned on installing, you will need to change the path in the config.php to /sub. However it should also be noted that if the web hosts (such as 1&1 etc) require changes in the .htaccess as also mentioned above, then the "RewriteBase /" line must also be in this case: 

RewriteBase /sub/


Installing on Nginx

in the "server" section in the Nginx configuration file, add the following (instead of using the .htaccess file):

location / 
{ index index.php;  

rewrite ^/blog-page-([^-]*)$ /?page=$1&p=blog break; 
rewrite ^/blog-([^-]*)+? /?d=$1&p=blog break;  

if (!-e $request_filename){ 
rewrite ^(.*)$ /index.php?p=$1 last; 
}
}


Installing on Amazon EC2

To install the necessary middleware for your EC2 instance, use:

# yum install httpd php php-gd -y


Installing on cPanel with Base64 errors

In some cases, servers disable base64 encoded code from running. There are many legitimate reasons to allow this to run so if you are uploading Pulse via a control panel (such as cPanel) and are getting upload warnings or errors please do one of the following, then re-upload:

  • Remove the base64_decode string from the disable_functions at php.ini* file
  • Ask your hosting provider to remove the string above if you don't have an access to the php.ini* file
  • Change hosting provider which allows the running of the base64_decode function

*php.ini is a configuration file that resides on the server that hosts your website. In some cases it can only be edited by the administrator of the server.

This issue will no longer apply to Pulse 4.7+ as all purchases made of Pulse will be unobfuscated, and not using Base64 encoding.


For further troubleshooting

If problems persist, check the built-in Pulse Diagnostics Install and Requirements Check Tool by going to yoursite.com/admin/install.php to see if the system requirements match, session handling is on, permissions are set correctly and so on.

For any other issues, try searching the community forums or getting in touch with us.

Pulse is easy to setup and install, but *some* shared hosting make it difficult (out-of-date PHP, upload restrictions and so on). If you run into that, let us know and we'll try and sort it.

Still need help? Contact Us Contact Us