Madhusudan

Hi @bmcinternet,

Apologies for the delayed response, and thank you for your kind words.

The options “Don’t Show Again” and “Keep Notification Bar Closed” are designed specifically for the Notification Bar (legacy module). These settings do not apply to the Announcement Bar, which is why you’re seeing it appear on each page.

For the Announcement Bar, this behavior is controlled separately. You can manage it using the “Expire After Close” option under the Cookie Duration settings within the Announcement Bar configuration.

If it is set to “Show on each page reload (no cookie)”, the bar will appear every time you open a new page, even after closing it. To prevent this, please select an option that enables cookie-based persistence.

Please refer to the screenshots below for better understanding:
https://prnt.sc/-0Y-9wYGfdmv
https://prnt.sc/9Hb8VTr_Y0yA

If you need any further assistance, feel free to let us know—we’re always happy to help.

Best regards,
Madhusudan

Hi @bsoftde,

Thank you for your suggestion and for sharing your feedback.

We understand the use case you described, where disabling the plugin on a parent page would also apply to its child pages. This could indeed be helpful in certain scenarios.

We will discuss this with our development team and evaluate whether it makes sense to include it as a feature. If it is considered a logical and useful enhancement, we will look into adding it in a future update.

We appreciate your valuable input and helping us improve the plugin.

Best regards,
Madhusudan

Hi @catwingz,

You’re very welcome! 😊

We’re glad to hear that updating the plugin resolved the issue and that everything is working properly now.

If you have any other questions or need assistance in the future, please feel free to reach out. We’ll always be happy to help.

Thank you again for your feedback and for using the plugin.

Best regards,
Madhusudan

Hi @catwingz,

Thank you for reaching out to us.

We’ve looked into this and can confirm that the plugin sets a cookie related to some of our advanced features like A/B Testing. Since you’re only using it for basic notifications, this cookie isn’t needed for your setup.

We’re already working on an update that will optimize this — the cookie will only be set when those advanced features are actually in use. This should resolve the caching conflict with SiteGround.

We’ll include this improvement in our next release. In the meantime, if you need an immediate fix, please feel free to reach out and we’ll be happy to assist you.

Thank you for bringing this to our attention!

Best regards,
Madhusudan

Hi @shinde77,

Thank you for sharing the detailed information.

We’re currently in the process of recreating your environment to investigate the issue further. Our team will review everything carefully to identify any potential conflicts or causes.

We’ll update you as soon as we have more findings.

Thank you for your patience and cooperation.

Best regards,
Madhusudan

Hello @jhonnyrubio,

Thank you for the update.

I can see that you’ve already contacted our support team, and they’ve provided guidance on this issue. Based on their findings, it appears that the problem is related to the content or configuration on your website itself.

We appreciate your patience and cooperation as our support team continues to assist you through the ticket.

Thanks again for your understanding.

Best regards,
Madhusudan

Hello @florentmissire,

Thank you for contacting us and for your kind feedback on the HT Mega plugin.

We’re sorry to hear about the issue you’re facing with Elementor’s Maintenance Mode. We’ve noted that the problem only occurs when HT Mega is activated, and we’ll begin investigating this compatibility conflict right away.

Our development team will review how HT Mega might be interfering with Elementor’s maintenance page rendering and will work on a fix to ensure smooth compatibility.

We truly appreciate your patience and will keep you updated on our progress. If we have any findings or updates, we’ll reach out as soon as possible.

Best regards,
Madhusudan

Hi @mrshafaq,

Thank you for reaching out and for reporting the issue.

I’m really sorry to hear that updating to version 2.8.6 caused your site to go down. We’ve tested the update on our end and everything seems to be working as expected, so this might be a conflict specific to your site’s environment.

To help us identify and resolve the issue, could you please let us know:

• Which theme you’re currently using
• Any error messages or logs you received when the site went down

You can also try temporarily deactivating other plugins to see if there’s a conflict when activating version 2.8.6.

For a more efficient resolution, we recommend creating a support ticket where we can communicate directly and analyze the error logs in greater detail. Please submit your ticket here:
Support Ticket

In the meantime, it’s perfectly fine to continue using version 2.8.5 while we work on finding a solution.

Looking forward to your reply and helping you get this sorted!

Best regards,
Madhusudan