Troubleshooting

Since version 5.3.27.6 we've gradually moved all the custom files (like templates, banner images and other uploaded files) from /accounts/default1 directory to the database of the software. Main reason for this move was to meet the requirements for our cloud infrastructure where all the hosted with us monthly accounts run the same files and the only difference per different customers is their database. For self-hosted customers this move brings easier way of moving their installation from locat...

Since version 5+ Post Affiliate Pro stores all templates, images, CSS files in database instead of directly in file system. In order to keep the link structure untouched (backward compatibility reasons) we have added a few rules to .htaccess files which redirect requests to correct files which load the requested resources from DB. Also since version 5.4.24.3 we have added an extra option to hash names of tracking scripts which will work only in case of correctly working .htaccess files. ...

Since version 5+ Post Affiliate Pro stores all templates, images, CSS files in database instead of directly in file system. In order to keep the link structure untouched (backward compatibility reasons) we have added a few rules to .htaccess files which redirect requests to correct files which load the requested resources from DB. Also since version 5.4.24.3 we have added an extra option to hash names of tracking scripts which will work only in case of correct rewrite rules. Since IIS doesn't...

If anyone is trying to install and run Post Affiliate Pro or Post Affiliate Network on HHVM server, it won't work without a special setup. Currently there is no option to run PHP loaders (IonCube or ZendGuard) on HHVM server so you need to set up a rule on your server using which you will run all PAP/PAN files via PHP server and not via HHVM server. You can use the following code (goes to a conf file in nginx, but the same theory should work with htaccess etc) : location ~ /affiliate(.*).ph...