Collaborative Effort to Address Performance Conflict

  • Resolved hassantafreshi

    (@hassantafreshi)


    1 year, 2 months ago

    Hi?NitroPack?team,

    The plugin Easy Form Builder was experiencing disruptions due to caching plugins, similar to yours, causing an unpleasant experience for WordPress users. It could potentially question the functionality of plugins for the end-user. To address this issue, we have collaborated with popular plugins, including yours, and successfully resolved the problem. Other plugins have tackled the challenge of preventing re-submission issues in the form builder, sharing relevant functions in their cache plugins to exclude a page from caching jQuery and JavaScript files. You can find more details on how this problem was resolved by other caching plugins on this GitHub page.

    Please provide a solution for preventing the caching of the page containing the Easy Form Builder by your plugin. I need this information to address the issue as a developer and resolve it in the Easy Form Builder.

    Thank you

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Nikol @ Nitropack

    (@nitronikol)

    Hello @hassantafreshi,

    We have informed our team regarding your request and will get back to you once we have further information!

    Thank you for your patience and understanding so far!

    Plugin Support Nikol @ Nitropack

    (@nitronikol)

    Greetings @hassantafreshi,,


    Following a consultation with our developers, we recommend implementing the?<script nitro-exclude>?attribute within your code.


    The?nitro-exclude?attribute serves to designate specific scripts for exclusion from optimization. Integrating this attribute into your code will automatically exclude the designated resources from optimization.

    Thread Starter hassantafreshi

    (@hassantafreshi)

    Thank you for your response and the suggested solution. Please take a look at the GitHub link, and you’ll understand how we’ve addressed this issue in collaboration with other plugins. We pass values through Ajax from the server to the core.js file, handling necessary matters there. Specifically, regarding the existing issue with identity credentials passed from the back end to the front end with the variable name ‘sid,’ it’s not invoked for the second time after form submission on the back end.

    Plugin Support Nikol @ Nitropack

    (@nitronikol)

    Hello @hassantafreshi,

    We appreciate your prompt response!

    An alternative solution we can propose involves purging the entire post cache using nitropack_clean_post_cache($post). It is important to note that it?takes the first parameter as a post object rather than a post ID.

    Please feel free to select the option that best suits your requirements.

    Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Collaborative Effort to Address Performance Conflict’ is closed to new replies.