Thanks Ash, Yes this fixes the output conflict. I appreciate the help. Take care

I can happily confirm that it is working properly. Thank you so much Konstantinos!

Dev support has helped to achieve this functionality on a per module basis. They were able to tie it into the cookies set by the "no longer show this popup across the site for 1 day" setting. See the response below: I've made some changes to the code in the functions.php file. The code you'll find now will be like so: add_action( 'wp_footer', function() { ?> <script> ( function( $ ) { function wpmudev_sls_getCookie( cname ) { var name = cname + '=', decodedCookie = decodeURIComponent(document.cookie), ca = decodedCookie.split( ';' ); for( var i = 0; i < ca.length; i++ ) { var c = ca[i]; while ( c.charAt( 0 ) == ' ' ) { c = c.substring( 1 ); } if ( c.indexOf( name ) == 0 ) { return c.substring( name.length, c.length ); } } return ''; } function wpmudev_sls_checkCookie() { var popupCookie = wpmudev_sls_getCookie( 'inc_optin_popup_long_hidden-11' ); if ( popupCookie != '' ) { $( '.hustle_module_shortcode_trigger.hustle_module_11').css( 'display', 'none' ); } } wpmudev_sls_checkCookie(); } ( jQuery ) ) </script> <?php }, 999 ); Everything is about the popup with id 11, as that's the one that is triggered by the button. As mentioned above the button will be visible during the 1st visit of the site but on a refresh / re-visit it will be hidden until the timer passes. So if you find this to be useful for your own use case, you will need to change the module IDs to your own module ID. Since this is how the shortcode button trigger should operate, I would love to see this functionality built into the plugin. From a UX perspective, the button should not be visible if the popup trigger is no longer active. Thank you for your hard work support!

You're awesome! You nailed it spot on. This is exactly what I was wanting to do I just wasn't sure how to tie into the cookies like you have successfully done. I will have to wait till tomorrow to make sure the button becomes visible again properly. But so far it is working perfectly. I made a Features & Feedback post about this. It would be awesome if this functionality could be written into the plugin itself so that the script doesn't have to be set up per module ID. But I understand it would likely be difficult to do. Thank you very much!

Hi Konstantinos! I appreciate the very detailed response. I understand the intricacies of this request. Keeping the popup functionality in mind, Case 1 is the option we want. My reasoning: User visits the website, clicks the button and gets the popup. Closes the popup. Clicks the button again in the same visit, the popup trigger is still active, so we want the button to remain visible. It is not until the page is refreshed/they come back later that the "After Pop-up is closed -- No longer show this message across the site -- for 1 day" setting becomes active and the popup is disabled. So that is when we want the button to hide. Is there a way to build this functionality (the button visibility) into the "After Pop-up is closed -- No longer show this message across the site -- for 1 day" setting javascript of the plugin? I hope this makes sense! Thank you

Hi Nithin, You are correct. I am using the "Click" Pop-up trigger with the shortcode but instead of "Click here" I have an email icon button. If the pop-up is set to only show once per X days (I have it set to once per day) the text/button continues to show even though the click pop up trigger is no longer active. I have a support ticket open but I figured this would be a good feature to have built into the plugin. The text/button shouldn't show if the popup trigger is not active. Thanks!

Absolutely! Thank you guys for your help in this matter.

Hello, The FTP timeout is due to the way our firewall is configured. I forgot about that! We will need to whitelist your IP. What's the best way for you to send me that? I'll pass the cURL info on to the guy who handled the server configuration. Thank you very much for the help so far!

Hello, Konstantinos, I have sent the information. Thank you!

Chatted with support. I needed to add these lines to wp-config.php before the /* That's all, stop editing! Happy blogging. */: define('WP_MEMORY_LIMIT', '512M'); ini_set('max_execution_time', '300');