Urgent! Quform error on Chrome and MS Edge

Home Forums Quform PHP Urgent! Quform error on Chrome and MS Edge

This topic is: not resolved
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #31337
    aixtreme
    Participant

    Hi.
    I’ve got a reproduced on multiple servers problem in browser MS Edge and Chrome. While my forms are working without problems on Firefox and Opera. Reproduced this problem with your untouched example files (beside entering email addresses for $config[‘recipients’] and $config[‘from’]) Error is always the standard “There was a problem An error occured…” note. Since I’ve tried this on multiple servers with your example files, I do not think error is on my side.
    Do you know this issue? How to fix this?
    Thanks for your answer
    Harald

    Attachments:
    You must be logged in to view attached files.
    #31351
    Ally
    Support Staff

    You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

    #31358
    transam
    Participant

    Hi Ally,

    Can’t get it working. Added the code. Did Ctrl+F5 and Ctrl + Shift + R.
    And removed all history and clicked cache off in the console.
    Also made a test form with the latest quform updates in it, but no luck!

    Example form: https://www.allmedialab.nl/contact Captcha= ALLMEDIALAB

    I have a huge problem with my clients!

    Regards and Thanks,
    David

    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    • This reply was modified 4 years, 5 months ago by transam.
    #31386
    Ally
    Support Staff

    You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

    #31391
    transam
    Participant

    Hi Ally,
    Thanks for pointing that out! Your the best!
    Can I leave that code in the script also after the update?
    Thanks again!
    David

    #31392
    Ally
    Support Staff

    You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

    #31459
    markko
    Participant

    We have the exact same error and your .js file modification fixed this for us, thank you.

    We only found out about this today unfortunately – so lost some customers who gave up before contacting us.

    Is there a mailing list we can subscribe to for this product that will show us of any URGENT upgrades / errors so that we can be ahead of the curve?

    Many thanks

    • This reply was modified 4 years, 5 months ago by markko.
    #31470
    Ally
    Support Staff

    You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

    #31481
    markko
    Participant

    Hi Ally,

    Thanks for your reply.

    I am subscribed to this already but I didn’t get an email about this bug. Have I missed something here?

    Regards

    #31486
    Ally
    Support Staff

    You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.
Be inspired. © 2024 ThemeCatcher Ltd. 20-22 Wenlock Road, London, England, N1 7GU | Company No. 08120384 | Built with React | Privacy Policy