eforms stopped working with latest upgrade

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Hai Zheng?

    (@hailite)

    Try to disable JS combine. Its not the issue about cache but optimization, so simply excluding that page from cache won’t help. Excluding from optimization may help if you want to still keep optimization on.

    Thread Starter mamasiga

    (@mamasiga)

    I have disabled JS combine, and it helped. eForms are now loading correctly!

    MANY THANKS FOR LIGHTNING FAST RESPONSE and LIGHTNING FAST CACHING!!!

    LiteSpeed is really the fastest caching solution out there…

    Thread Starter mamasiga

    (@mamasiga)

    1/ Do you recommend excluding forms from caching?

    2/ What is correct URL format to exlude all pages that are under “/exlude-url/” path? I mean, what URL should I write to exlude all pages like “/exlude-url/page-1″,”/exlude-url/page-2″,”/exlude-url/page-3”,etc.

    Thank you.

    Plugin Support Hai Zheng?

    (@hailite)

    1. Depends. If the form didn’t have any issue with caching, you can cache them always. The only issue it may have is the token/nonce which may have a expiration. In this case those form should deploy with our ESI func which can solve that perfectly.

    2. You can just use /exlude-url/.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘eforms stopped working with latest upgrade’ is closed to new replies.