Forum Replies Created

Viewing 2 posts - 16 through 17 (of 17 total)
  • Author
    Posts
  • in reply to: Huge Qu-Form error ajax #35611
    adaka
    Participant

    We set the “max_iput_vars” to 5000 and it works so thank you for this information.

    The others problems now are for the backend and the admin front end. we have created a space reserved for a forms “manager” or “admin” that could manage them out of the backoffice. Typically the error is the same as in the backoffice. It loads and nothing is displayed after 10 seconds of loading.

    My question is the following, would it be possible to give me a deadline for the optimization that you are going to do from this weekend?

    Our project is due in mid-July and understand that without displaying forms in the backoffice, it is impossible for us to stay on Qu-form. If you have more ideas to submit to us to solve those problems, do not hesitate.

    adaka

    in reply to: Huge Qu-Form error ajax #35580
    adaka
    Participant

    I am working locally so the acces could be impossible for now.
    We reduce the length of the form, we deleted 3 pages and it works fine. If you have tested for more than 1000+ fields i trust you. We may have more than that with the conditional logics. What is the limit ?

    The problem could come from the field “config” in the database because there 2 millions of characters like i told you is it normal ?

    I ve tested to disabled the ajax and it works fine in the frontend, but for the UX it is not interesting, but in the wordpress backoffice i still have 5 seconds of loading and after, none of my forms created are showing.
    I will try your solution for the next operation in the site.

    Thank you for your answers. Hope we will find a positive issue

Viewing 2 posts - 16 through 17 (of 17 total)
Be inspired. © 2025 ThemeCatcher Ltd. 20-22 Wenlock Road, London, England, N1 7GU | Company No. 08120384 | Built with React | Privacy Policy