Hi @josemorenocanwilltech,
Thank you for sharing the feedback. Can you please share more details about the exact caching issues you are experiencing with the module? Additionally, I viewed the doc, and it appears that the option to display assets inline is meant to fix caching issues with the Beaver Builder plugin, and that, too, in some rare cases.
Let me know if I am missing anything.
Kind regards,
Aradhy 😊
Hi there,
The caching issues I was experiencing were that because of Beaver Builder’s cache, your module was not showing changes (Displaying or Hiding content) properly.
Deactivating this:
Render CSS/JS assets inline
Solved the issue.
Just FYI.
Kind regards.
Hi @josemorenocanwilltech,
Thank you so much for the follow-up and for sharing these helpful details!
We now understand that Beaver Builder’s CSS/JS assets inline rendering setting was preventing our Timed Content module from reflecting changes in visibility (show/hide) properly due to caching behavior. We’re glad to hear that disabling that setting resolved the issue for you.
While that Beaver Builder setting is designed to address certain edge-case caching problems, your case highlights a scenario where it may actually interfere with dynamic content like ours. We’ll certainly pass this along to our development team for further testing and potential improvements.
Your input is very much appreciated—it helps us make the module more reliable for all users. If you run into any other issues or have more feedback, feel free to reach out anytime!
Kind Regards,
Ankush 🙂
