I need a bit more information then this, can you let me know the website urls. Is it a post/page.
We had to revert the site to a backup, so we could use the earlier version, but the site is http://picturepark.com/
It only affected all the single blog posts, which are linked to here:
http://picturepark.com/category/dam-blog/
and here:
http://picturepark.com/category/news/
It’s fine now, as we’re running the older version.
There is a staging server I can re-upgrade to the new version so you can see the problem in action, and/or login.
-Michael
I updated the plugin on the staging server, and it’s exhibiting the problem. Please let me know where I can send you links to that privately.
Thanks,
Michael
Did you get the staging server URLs and credentials I sent?
Sorry I didn’t, I’ve been checking.
Can you tell me the version number that does work.
I sent you an email:
From: “Michael P. McHugh” <mchugh@digitalfusion.net>
Subject: http://picturepark.staging.wpengine.com
Date: April 30, 2014 at 7:31:52 PM PDT
To: web@marketingmix.com.au
Right around that time you should have gotten the login credentials from the wordpress installation. I’ll resend in a single email form my address.
Version 2.0.3 is broken on the staging server I’m giving you access to.
Version 2.0.1 is working on the live site.
-Michael
Can you please test the staging server now.
If I’ve fixed it, I will merge with the next release.
Thank you
Yes it seems to be working there.
However, the plugin seems to be at version 2.0.1, not 2.0.3 which exhibited the problem. Did you downgrade it to 2.0.1 and then apply a fix? Shouldn’t that have been done on 2.0.3?
I didn’t play with the version number. I have just deployed 2.0.4 for you.
Thanks! I’ll give it a try on our staging server and see how it goes.
I just updated our staging server to the new 2.0.4 version, and it’s still exhibiting the redirect looping problem on blog posts. Which is odd, because the modified version you had in there previously seemed to have fixed the problem, but it’s back with 2.0.4.
I’ve enabled your account again, so you could take another look, and I emailed you a sample link.
Thanks,
Michael
Try again. I think 2.0.5 should fix your issue.
That seems to have fixed. Successfully updated to 2.0.5.
Thanks!
-Michael
