Payment form endlessly saving, rendering incorrectly on iPhones

[jenberger]

Hello -- I noticed that my Payment Form was rendering incorrectly on my iPhone, with the text breaking in odd places and some headers not showing properly. So I went to edit the form, and now when I click Update Form, it is just endlessly saving and never brings me back to the edit page. Screenshot attached.

This is pretty bad and looks bad for our organization to have our Donate page looking this way... Please send me some tips ASAP.


Account: 25900, form for "End Media Misogyny" Campaign

[CnP.Support.AM]

Good day @jenberger

We see the issue regarding the text breaking which will be fixed in the next update. However, we unable to replicate the issue with saving the form. Would you please share the iPhone/OS/Browser name and version#s?

Also the images you have provided is PNG and this forum does not show it in full scale. I only see a thumbnail. Would you please post this as a JPG so we can review?

Looking forward to hearing back from you.

[jenberger]

It's absolutely unacceptable for the text to break that way, and it should not be fixed in the next update-- it should have been fixed before. Our donation page still looks pretty awful, and now our donors are getting a notification that the form is insecure.

The form-saving issue: All it was was a blue square animation endlessly moving instead of resolving to saved. The PNG wasn't very helpful.

[CnP.Support]

Good day jenberger

The issue you are reporting is due to your browser cache that may be corrupted.

Please clear your browser cache and I assure you this issue will be fixed. We have seen this before where a browser has cached an old version of our scripts and once you clear your cache this issue will go away.

This is not your browser history but the cache. For example in Chrome it is the following:



I recently had the exact same issue with Microsoft Office online and saving a PowerPoint. To speed up the web Google Chrome (the most aggressive of all browsers) cache sites, even though strict commands are included for a page not to be cached. The caching saves a version of CSS and scripts that later, when the front end updates it is not updated by the browser.

The following is a good example on how to do this for other browsers: https://askleo.com/whats_a_browser_c...uld_i_want_to/

Hope that helps. If doing the above does not clear it please let us know and we will investigate the issue further, but I am 99.99999999% sure this will resolve the issue.