Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

All other Modules /

Discuss all other Modules here.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

[SOLVED] UserForms 3, loading, saving, sending Issue


Reply


365 Views

Avatar
pinkp

Community Member, 168 Posts

13 May 2013 at 12:35am

Edited: 04/06/2013 10:32pm

UserForms 3 with SS3.05

I have a very long and in depth form which I created. You can view it currently [url=http://www.handmadeinbritain.co.uk/apply/]here[/url]
It works on the front end and the submissions are saved in the CMS but it has only successfully sent to an email address once. It no longer sends even though it goes to the finish page.

Not only that but that page takes AGES to load in the CMS and in FireFox I get:

Warning: Unresponsive Script
A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.

Script: http://www.mycode.co.uk/assets/_combinedfiles/lib.js?m=1367872375:292

Not only that the page no longer saves and instead gives me a Bad Request

I've created another form on a another page and this works fine, saves and sends. It this simply a case of the form being to longer for the server to cope with? even though it worked once...

I cant run the site in DEV mode as the locks me out of the Admin area... it freezes on the splash page SS logo and none of the bug fixes for this work for me (i.e. changing the CHMOD of assets etc).

Im stuck on what to do next.. I could build the form again but worry it will just be the same and waste my time. Any thoughts? thanks

EDIT

Solved this by downloading a newer version from Github which allowed me to send the files.
Solved the saving issue by deleting some form fields. It seemed to only stop saving at 57 fields 56 was fine. This was also effected by the show/hide rules.

never solved my Unresponsive Script error but thats a separate issue.