• Resolved symop

    (@symop)


    Hi i’m using contact form 7 in this site https://www.autonoleggiosemplice.it and randomly on some link like a https://www.autonoleggiosemplice.it/auto/audi-q2-1-6-tdi/ (in this case) appear this error.
    {“mailSent”:true,”into”:”#wpcf7-f1273-p1872-o1″,”captcha”:null,”message”:”Il tuo messaggio \u00e8 stato inviato correttamente.”,”onSentOk”:[“location = ‘http:\/\/www.autonoleggiosemplice.it\/confermarichiestapreventivo’;”]}

    I notice that error depends by the slug of page, if I rename my permalink return to working fine but something in DB break and I can’t use old slug ever…result message in the top……

    Can you help me please ?

    CF7 version: 4.3.1

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    Try switching to the default theme, deactivating all other plugins, and clearing all cache.

    Thread Starter symop

    (@symop)

    Ok, you think that solve db broken data ?

    Thread Starter symop

    (@symop)

    Hi Takyuki,
    after make what you tell me, I think that I’m solved issue. Today the same problem again on my form “contatti”, only after changing permalink name it return to work. What else can I do ?

    Same problem here!!! Only changing the permalink make the page work again.
    In my case the message is:
    {“mailSent”:true,”into”:”#wpcf7-f10854-p10810-o5″,”captcha”:null,”message”:”Obrigado! Em breve nossa equipe entrar\u00e1 em contato.”}

    The number highlighted is the ID of the form. I tried uninstall the plugin, changing the theme, even deleted and recreated the forms but, the page loads the same error!

    Any solution found in the meantime?

    When it first happened I recreated the page (with another permalink) the error was another.
    {“mailSent”:false,”into”:”#wpcf7-f10853. The number was of the other form.

    The pages still returns the errors, even though I deleted the pages:
    https://www.kraaften.com/solicite-orcamento/
    https://www.kraaften.com/orcamento/

    Thread Starter symop

    (@symop)

    Hi I found my problem, if can help you. I’ve a managed server and Caching Service enabled. I’ve solved flushing cache on Supercacher Dashboard on my Server Panel.

    Just after flushing it, al became to work.

    Is a problem because I cant flushing cache every week, but it solve my critical problem at the moment.

    Hi symop!
    What a coincidence!

    My problem was just solved by my host service support (www.siteground.com). By the way, not the first time they saved my ass!

    Look at what was causing the problem according to the SiteGround expert Miroslav Andreev:

    Hello Greison,

    My name is Miroslav Andreev and I am one of the Techincal Support Supervisors in SIteGround. While I was working on a different ticket earlier today, I have noticed that you started a thread on www.ads-software.com regarding the issue that you have encountered on

    kraaften.com

    During my work on the other ticket I have managed to resolve a similar issue and I have decide to post a short follow up in your ticket as well.

    The issue was caused by the Google PageSpeed cache that you have activated for your site. In order to resolve the error and bring the site up, I have taken the liberty to deactivate that caching mechanism.

    In order to avoid any further issues, I would recommend you to use the static caching of our SuperCacher. You could activate it through cPanel –> SuperCacher.

    Should you have any further questions or comments, please do not hesitate to contact us again.

    Best Regards,

    Miroslav Andreev
    Technical Support Supervisor

    Hope this can help somebody else with the same problem!

    Thanks symop!

    Thread Starter symop

    (@symop)

    ?? I’ve solved with the same method, Siteground support is very qualitative service support. I’m very sorry to cannot use GPspeed ??

    thanks for posting how to solve it, it can help someone else for sure ??

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Random error {“mailSent”:true,”into”:”#wpcf7’ is closed to new replies.