Troubleshooting

Your server may have been reset unexpectedly, and you may need to perform a repair on your MySQL database.

You can easily do this yourself by going into your hosting CPanel -> phpMyAdmin. Select the script’s database and it will list the tables in the database. Tick the checkbox next to each of the tables, and you should see a drop-down box saying “With Selected”. Select “Repair table”.

See the screen shot for an example of how to do this.

Your hosting provider should be able to do this if you contact their support. But it’s helpful to know how to do a MySQL repair yourself.

If you see this “DB: Error: unknown error” error again in the future, in any of your PHP scripts, you can perform a database repair yourself.

Save

Save

That error means that the script can not connect to your MySQL database.

Either the MySQL server is down, or the database somehow got deleted, or the config.inc.php settings are somehow no longer valid.

99.9% of the time it is because you have incorrect values in your config.inc.php database login settings.

Make sure that the /include/config.inc.php file contains the correct database settings, including the ‘hostspec’ field, (phpMyAdmin should tell you the server & database values at the top of its pages).

Try using phpMyAdmin to view the database, to make sure it still exists and the server is running. On the “Structure” tab it should list 6 tables, along with the number of records they each have. If any of the tables say “In Use” then it probably needs to be repaired. You can try doing a repair on the tables via phpMyAdmin (tick their checkboxes then select “repair” from the drop-down field).

You can also try asking your web host to check if the database server is up.

This is because the server uses PHP 5.2.5 or higher, and the Ioncube loader must be installed in the php.ini file in this case. Your hosting provider should be able to do this if you contact their support, but it may also be possible for you to use a custom php.ini file to install the Loader yourself.  You should check your web hosting technical support area for information on how to install Ioncube loaders.

These errors indicate a problem with your PHP configuration or filesystem permissions and are not specifically related to the rotator script. You would encounter the same problems on your server with any script that uses PHP sessions. The problem is usually that the server’s PHP session.save_path setting is incorrect.

		php_value session.save_path "/home/yourusername/tmp"

This error is probably due to an incomplete file being uploaded when you transferred the script to your server.  Try deleting the corrupted file, and reuploading.  Also, use binary transfer mode in your FTP client when transferring the files.

If the problem remains after reuploading, then the error is probably due to incompatibility between the encoded PHP files and the version of the Ioncube loaders on the server trying to decode them. Basically, the old loaders being used can’t read the new format of the encoded script so it thinks the files are corrupt. The script makes use of recent Ioncube features (such as license files, and ASCII upload compatibility) and so the latest version of the loaders must be used.

A suitable loader for the most common server operating systems is included in the script packages /ioncube/ directory. Provided that you have uploaded this directory and your server supports run-time loading then the script should usually be able to use the correct Ioncube loader.

However, the “file xxx.php is corrupted” message suggests that the correct loader is not being used, and instead an old version of the Ioncube loader is trying to decode the PHP files. This happens when your web host has an old version of the loader already installed server-wide via php.ini, and unfortunately, you cannot override this with runtime loading.

Please contact your web server administrator and let them now that they need to upgrade their Ioncube loaders. They can be freely downloaded here:http://www.ioncube.com/loaders.php. They should have no problem seeing as they’re already using the loader, and the loaders are backward compatible so nobody else on the server will be inconvenienced by the upgrade.

Make sure that in the /url/include/config.inc.php settings file you have:

$GLOBALS[‘config_settings’][‘short_base_url’] = “/url/”;

Please double-check that you have uploaded the /url/.htaccess file included in the .zip package. The rotator script uses mod_rewrite rules defined in .htaccess to transparently rewrite URLs.

The codefu.net rotator script allows you to add any javascript tracking snippet through a setting in the config file. The setting will affect all portals, in other words, if you add the snippet to the config file, then all portals will be tracked.

Edit the /url/include/config.inc.php file in a text editor, and look for the following section:

$GLOBALS['config_settings']['analytics_code'] = <<< END
PASTE YOUR SNIPPET HERE
END;

Simply paste your javascript snippet in the area indicated in red.

If you want to use Google Analytics tracking, I recommend that you use the following snippet, and modify it to insert your own tracking ID:

$GLOBALS['config_settings']['analytics_code'] = <<< END
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
try{
var pageTracker = _gat._getTracker("UA-XXXXXXXX-X");
pageTracker._trackPageview();
} catch(err) {}
</script>
END;

Simply replace the UA-XXXXXXXX-X with your actual Google Analytics tracking ID.

Before you proceed you should create a rotator portal that you will use to rotate your http://www.yoursite.com/ traffic. For this example let’s say you have called that portal ‘main’, and it’s auto-generated link is http://www.yoursite.com/url/rotator/admin_main.