- spexAsked on April 02, 2012 at 07:32 PM
I'm experiencing an issue that appears to be similar to this thread, resolved in April, 2011.
I've added fields to my jotform, and preview looks as I would expect. The Embed Form Wizard suggests I use the following URL to my survey: http://form.jotform.com/form/13112657545
When I click on that link, I get an old version of the survey. Ironically, the Form Preview viewer uses the following URL, which works correctly: http://www.jotform.com/form/13112657545
Unfortunately, the non-working link (form.jotform.com) has already been distributed, and I didn't realize the public URL wasn't updating correctly. Is it possible to get the form on form.jotform.com to refresh quickly? I would prefer to avoid spaming the entire group again to fix the URL.Page URL:
- spexAnswered on April 02, 2012 at 07:35 PM
Amazing - After 45 minutes of freaking out before going home for the day (or 1 minute after posting a request to the forum perhaps), the form refreshed on form.jotform.com. Maybe there was significant backlog.
All appears good to go.
- JotForm SupportMike_TAnswered on April 02, 2012 at 07:38 PM
We are very sorry for the inconveniences.
This slow update problem is already forwarded to our Development Team, and we hope that things will be improved.
Thank you very much for using our services.
- satchkovaAnswered on June 07, 2012 at 05:58 AM
Same cache refreshing problem for me in IMCreator including Jotform form.
Is there a solution ?
- JotForm SupportabajanAnswered on June 07, 2012 at 07:50 AM
Unfortunately, there's currently no other solution than changing the URL from the http://form... version to the http://www... one. It's a caching issue at the former but it's not on your computer. Forms at the http://form... URLs are distributed via a content delivery network (CDN) while those at the http://www... addresses are distributed in the traditional manner. Each type of distribution method has advantages and disadvantages but on balance, the CDN way is better.
Please see the following text and video links for details:
(Caching issue explained at 4:47)