MPA3:Admin area/Settings/Gallery Settings
This section is placed in the MPA3 Admin -> Program Management -> Gallery Settings.
This section allows you to set a different MySQL server to process the hits to the galleries. This way you can distribute the load of the MySQL server over couple of other servers. You will need to copy the MPA3 database structure over to the galleries MySQL servers.
- MySQL host/database/username/password - set the MySQL account that MPA3 will use to access the galleries' databases. Leave blank to use the default MPA3 database.
- Gallhit.php, Godhit.phpand Podhit.php URL - These are the names of the files that will track the galleries hits. You can set whatever name of the file you want and rename it via the file system. This way nobody will understand what affiliate program you are using.
- Gallery hits, GOTD hits and POTD hits PATH - Since galleries hits can be quite overwhelming, by default MPA3 is set to write the hits to a flat file, and then on every minute to form a sql having in mind those recorded hits and to update the database. This is essential, especially with large traffic programs, since the MySQL server can easy reach its maximum allowed connections, in case this is turned off. This option is to let you define where to put the galleries hits. On very large traffic programs, we recommend building a virtual RAM drive, and setting the HITS path there, since it will be much faster than saving them on the hard drive.
- Use hosted galleries as source - When the checkbox is checked, the last X galleries (whatever is set in the box on right to it) will be used and rotated every day for a site. This way you can bypass the adding of GOTD galleries and the galleries will be up-to date with your hosted galleries. Set 0 in the form field box to use all the hosted galleries in the GOTD rotation.
- No commas in the link codes - Here you can set whether or not to use commas or slashes in the link codes for the galleries. Some TGP softwares are incapable of using links with commas, so this is the right solution when this is the case. Before using slashes, make sure to create symlinks to the tracking scripts and force the symlinks to execute as php script. For example:
ln -s gallhit.php gallhit ln -s godhit.php godhit ln -s podhit.php podhit
and then make an .htaccess file with the following content:
<Files gallhit> ForceType application/x-httpd-php </Files> <Files godhit> ForceType application/x-httpd-php </Files> <Files podhit> ForceType application/x-httpd-php </Files> <Files modhit> ForceType application/x-httpd-php </Files>