Mint Forum

In my case with the pepper, it was something my host had to change at their end, my domain was triggering a mod_security rule that underneath their config, couldn’t be changed through a .htaccess file - That may be one possibility.

With you having a permission problem, have you double checked that none of the CHMOD values have been altered on the directories in question?

And yes, I have checked, and permissions are fine.

Not sure if this helps much but check out the URL Help Page here.

OK, a quick update… I’ve fixed it, though it did require a little bit of hackery. In case anyone else has this problem for some reason, here is my solution:

(still don’t know why this was a problem in the first place, though)

Overall method: I adjusted the javascript file to remove “http:” from the beginning of the “to” and “from” URLS, and then added them back on in the PHP code before the URLs were saved in the database.

Potential issues: The only downside to this is that it won’t properly distinguish between http: and https:, so https: links won’t be tracked. I don’t have any links that include https:, and probably won’t in the future, so it shouldn’t be a problem.

Code:

script.js:

after these lines:

var to = (window.decodeURI)?window.decodeURI(this.href):this.href; var from = (window.decodeURI)?window.decodeURI(document.URL):document.URL; var to_title = (this.title && this.title != ”)?this.title:this.innerHTML;

I added:

to = to.replace(/http:/gi, “”); from = from.replace(/http:/gi, “”);

Classes.php:

after these lines:

$to = $this->escapeSQL(preg_replace(‘/#.$/’, ”, htmlentities($_GET[‘to’]))); $raw_to_title = $_GET[‘to_title’]; $from = $this->escapeSQL(preg_replace(‘/#.$/’, ”, htmlentities($_GET[‘from’]))); $from_title = ($_GET[‘from_title_encoded’]) ? $_GET[‘from_title’] : htmlentities($_GET[‘from_title’]); $from_title = $this->escapeSQL(trim(str_replace(‘n’, ’ ‘, preg_replace(‘/%u([dw]{4})/’, ‘&#x$1;’, $from_title))));

I added:

$to = ‘http:’.$to; $from = ‘http:’.$from;

You should not have to modify the source code. There is nothing wrong with your pages or the way the Pepper works. Your server is preventing the Pepper from ever receiving the request. This is often caused by an overzealous mod_security setting. You can fix it with a simple addition of an .htaccess file (or to if one already exists) in your Mint directory.

Disregard the error number (hosts often send incorrect error numbers to throw off those who might try to circumvent the mod for spamming reasons) but follow these instructions.

Try contacting your host and see if you are triggering a mod_security rule. I tried the .htaccess approach too but it didn’t work for me either as my host had disabled the technique of turning it off through .htaccess files.

Once my host had changed things their end, all worked fine.