|
 |
|
Frequently Asked QuestionsStaticNuke doesnt appear in the Administration System
You will need to re-upload the installation files to your PHP Nuke installation folder. Also, sometimes there can be troubles if you use an FTP client instead of the file manager that you get with your hosting. I recommend SmartFTP.
Static Nuke wont create module directories
Some web server configurations prohibit PHP scripts for making, modifying and moving files or directories for security purposes. Since StaticNuke does all three of these things, getting StaticNuke to work on a server that restricts script access to files can be quite a problem. However, there is a manual work around, as long as StaticNuke lists the categories as being created in the admin system, you can do this:
- Create your categories in StaticNuke and ignore the errors
- In your PHP Nuke /modules directory, manually create a directory
with the same name as the category you just created
- Rename "example_index.php" to "index.php" on your computer
- Open index.php in a text editor (WordPad is better than Notepad!)
and look for this line:
$categoryName = "POTM";
Rename it to:
$categoryName = "your_module_folder_name"; - Upload the updated index.php to your new module directory
You can find the example.php file bundled with StaticNuke.
When I access StaticNuke I get an Access Denied message
This is likely caused by either incorrect installation or file permissions. Make sure that the directories you upload from StaticNuke are all CHMOD to 755, and every file that you upload must be CHMOD to 644. Typically, these are the default settings, but different servers behave differently. If you don't know what this means, then using your FTP client you can usually set these by right clicking ont he file or directory and finding either Permissions, Properties or CHMOD. Some servers however will require you to use the file manager provided by your web host to correctly set permissions. This error is, again, principally a problem caused by PHP configuration variancies.
An alternative problem is that your security software (which you should have) is causing trouble with a non-standard script trying to access a script in your admin directory. There is no single workaround for this, please read the documentation that comes with your security scripts.
If you find any more problems, please email me. It all works fine for me, but there may be other things that I can fix, or at least work around.
|
|
| |
|
