Blair Williams

Some of the files required for 1.5.7 were somehow not included in the 1.5.7 zip file.

We’ve just now released 1.5.8 which fixes this problem.

Please upgrade and this issue should be resolved.

Thanks,

Blair

Some of the files required for 1.5.7 were somehow not included in the 1.5.7 zip file.

We’ve just now released 1.5.8 which fixes this problem.

Please upgrade and this issue should be resolved.

Thanks,

Blair

Some of the files required for 1.5.7 were somehow not included in the 1.5.7 zip file.

We’ve just now released 1.5.8 which fixes this problem.

Please upgrade and this issue should be resolved.

Thanks,

Blair

Some of the files required for 1.5.7 were somehow not included in the 1.5.7 zip file.

We’ve just now released 1.5.8 which fixes this problem.

Please upgrade and this issue should be resolved.

Thanks,

Blair

Some of the files required for 1.5.7 were somehow not included in the 1.5.7 zip file.

We’ve just now released 1.5.8 which fixes this problem.

Please upgrade and this issue should be resolved.

Thanks,

Blair

Some of the files required for 1.5.7 were somehow not included in the 1.5.7 zip file.

We’ve just now released 1.5.8 which fixes this problem.

Please upgrade and this issue should be resolved.

Thanks,

Blair

We’ve just released 1.5.8 which fixes this problem. Please upgrade.

I don’t know what happened but www.remarpro.com didn’t zip the file correctly somehow so there are files missing. We’re just working on doing another release — hopefully the zip file will be created correctly this time. For now, rolling the stable version back to 1.5.6 — stay posted for the new 1.5.8. We’ll verify it in our environment before pushing it stable again.

Sorry for the problems … We’ll get this fixed asap.

Blair

I just tried adding this:

define('DONOTCACHEOBJECT', true);

It still won’t update the object in the database.

Thanks,

Blair

This was fixed automatically this morning but please upgrade to version 1.5.2 at your soonest convenience — it contains several fixes related to this issue.

please upgrade to 1.5.2 at your soonest convenience — this issue has been resolved.

You can get these features by upgrading to Pretty Link Pro.

Hope that helps.

This is fixed in the 1.4.56 release …

I’ve never seen this happen before. We have people with thousands of affiliate links that have been running for over a year. My guess is that it would have something to do with either a change in your blog or your web host.

Also, there’s been a change in pretty link recently that converted all cloaked & pretty bar links into redirects for Pretty Link Lite users (read more at https://blairwilliams.com/where-did-pretty-link-cloaking-go/ ). I doubt this was your problem but has been a source of a lot of questions.

I’m sorry you had this bad experience — if you decide to use Pretty Link again and have any issues, feel free to contact us at https://blairwilliams.com/contact …

Hmm, this may indicate a permission issue on your webhost — are you able to install other plugins?