Update to Delivery Script (important xino changes)

6 posts / 0 new
Last post
puravida's picture
puravida
Jedi Warrior
Offline
Joined: 09/01/2007
Visit puravida's Website

No code changes are required on your part, unless you specifically coded for checking "noretry" on refreshed items in queue. I do not believe anyone is keying off of that response, since it's been wrong for years. So I'm moving forward immediately with the update.

I realized that when refreshing a request, we have returned "noretry" for years. It was in the documentation that way, so at some point, I felt like that was the best way. But presently, I feel like "queued" is the correct status for anything in queue. So, initial requests will continue to return "noexist." Follow up requests, until processed, and refreshes will always return "queued" from now on. I updated the API documentation to reflect this change in behavior.

I also believe (from testing) that I have resolved several, lingering issues with certain types of rare requests that caused problems.

So I wanted to make this announcement, just in case there are "new" issues with this fairly large update to the delivery script. We will be watching closely.

LibertyWeb
Offline
Joined: 09/14/2011
Visit LibertyWeb's Website

Hi puravida:

All of the screenshots on my portfolio page are showing "Account Problem". Not certain if its due to this update or not, but I know everything was fine just a few days ago. Perhaps its a result of the latest WordPress update? I know that I had issues with another plugin because of the update to WP 3.5

Here's the URL: http://libertywebmarketingandseo.com/images/

nunocpinto
Offline
Joined: 09/29/2009
Visit nunocpinto's Website

Hello puravida: i am having the same issue as LibertyWeb; what is happening and how can we solve this?

Thank You.

Check here: http://www.nunocpinto.info/webdesign/

harisg7
Offline
Joined: 02/25/2010
Visit harisg7's Website

I have the same problem.. Sad

LibertyWeb
Offline
Joined: 09/14/2011
Visit LibertyWeb's Website

Looks like its working gain now on my end Smile

puravida's picture
puravida
Jedi Warrior
Offline
Joined: 09/01/2007
Visit puravida's Website

Hello everyone,

That problem was not related to the change I made. It affected PVP (Preview Verification Page) users only, from what I can tell. Somehow, the security hash that gets updated every minute, got out of sync. It was corrected around 1:00pm ET (GMT -0500).

Please note that the PVP method is no longer supported, technically. We did support it in this case, because we want to make sure it at least basically works for the many who still use it or use scripts that integrated it. However, we STRONGLY urge you to use software that is "ShrinkTheWeb Certified" and bypasses the PVP altogether.

We apologize for the inconvenience and will be watching to see if it happens again. Fortunately, our system notifies us when it happens, but there was a delay in fixing it because I have been very ill and we have all been pulling all-nighters lately to work through the migration and some Rackspace issues. We had just called it quits this morning, shortly before the issue occurred.

ShrinkTheWeb® (About STW) is another innovation by Neosys Consulting
Contact Us | PagePix Benefits | Learn More | STW Forums | Our Partners | Privacy Policy | Terms of Use

Announcing Javvy, the best crypto exchange and wallet solution (coming soon!)

©2018 ShrinkTheWeb. All rights reserved. ShrinkTheWeb is a registered trademark of ShrinkTheWeb.