Hyperframe flatfile CMS

Troubleshooting your install

Existing files:

A .htaccess file and php.ini file are supplied in the distribution. It may be advisable to check if same-named files already exist on the server, and whether over-writing them would cause any issues.

Server returns a '500 Error' instead of displaying index.php

This usually indicates that there is a line in the .htaccess file which the server cannot understand. It might also indicate that a setting is present in .htaccess or php.ini which the hosting company has disallowed.  

If your php implementation is the CGI variety and the 'php_value auto_prepend_file' .htaccess line is activated, you will most definitely get this message. The fix is to add # to disable this line.

Server returns 'PHP Fatal error:  Unknown: Failed opening required codebase/hyperframe.php'

The respective line in php.ini or .htaccess refers to an incorrect location, or the file is missing. This might also arise if the permissions on the codebase directory are incorrect.

Page loads in browser, but with no banner or menu

Ensure that you are viewing the site through the webserver, and not by opening the pages directly from the zip. Regardless of the CMS used, no php site can be viewed directly from its files. The other reason this may happen is if the Hyperframe system is not being launched, and what you are seeing is the bare page content. It may be that the server's php setup is configured to disallow prepending, or that the php version is too old. Or, the page may be missing the 'shebang' (reflex loader command) in its first line.

A yellow 'Frame missing' message appears, followed by the plain page content.

This indicates that either some files are missing from the frame, or  that the reference to the frame in siteini.php is pointing to an incorrect location. Version 4 differs from earlier releases in that frames are in their own subdirectories, so the actual 'frame/' directory no longer contains a frame.

Page loads OK but login doesn't work or Hyperbar never appears

The user (page editing) login relies on a session cookie being set by the browser. If your browser is set to refuse cookies, this may be the problem.  Some Web filtering software or proxies may also cause problems with online editing. In that case, see if an exclusion can be set. Most modern browsers will be able to load the editing interface, although Firefox is recommended.  See the Requirements page for more info on this aspect.