- drprickettAsked on February 12, 2013 at 02:23 PM
I have an embeded code on a wordpress page. But when I edit the JotForm and save, the new edits are not visiable on the page. Cleared caches with the same result, am I missing something?
- JotForm SupportWelvinAnswered on February 12, 2013 at 03:38 PM
It takes effect instantly, however, sometimes it takes a delay because the form will be serve first by our CDN Network.
Changing the form URL to the embedded codes to start with http://www from http://form or fromhttps://secure to https://www will solved that.
Try that and update us for results.
- drprickettAnswered on February 12, 2013 at 04:34 PM
That did not seem to work but when I was in chat someone reset my forms caches internaly. I believe I have everything set up properly and just need that done one more time please. Thank you!
- KadeJMAnswered on February 12, 2013 at 06:16 PM
We do apologize about that. I have gone ahead and cleared your form cache again to see if that helps. Are you able to provide us with a link or screenshot if it still gives you further trouble so that we can further investigate this matter for you.
Also I would like to recommend these 2 wordpress guides for reference which offer 2 different embed methods to ensure that the form was embedded correctly -
- pinoytechAnswered on February 13, 2013 at 01:34 AM
Sorry for the inconvenience that may have caused. Can you please share to us the URL of your website where your form embedded to investigate the issue and for further assistance?
- drprickettAnswered on February 13, 2013 at 07:37 AM
Clearing the forms cache seems to help however the problem seems to still be there. After a few additional changes were made and are not reflected in the embeded wp page (http://www.sunglowphotography.com/details-questionnaire) or the direct url: http://form.jotform.us/form/30426170307141.
- drprickettAnswered on February 13, 2013 at 07:55 AM
I also just tried to submit the forms and received the error below after a long "please wait..." on the submit button. They were working yesterday. Thank you and I am very sorry for the trouble.502 Bad Gatewaynginx/1.0.10
- pinoytechAnswered on February 13, 2013 at 09:06 AM
We apologize for the inconvenience that may have caused. Let me forward this issue to our dev team for further investigation since I was able to replicate the issue on my end and we will inform you immediately as soon as they fixed this.
We would like to ask for your patience while our dev team working on this.
- drprickettAnswered on February 13, 2013 at 02:18 PM
- drprickettAnswered on February 13, 2013 at 02:24 PM
Just gave it a go on my own and it seemed to respond instantanily to saved changes and submitted properly. Thank you.