@irishetcher @allextreme the reason why this happened (it’s more common than you might expect) is because you unloaded the CSS that was behind that content. So, on one page you might not need PhotoSwipe at all. You decide to unload everything related to it, including its CSS. However, there are situations when HTML content is also printed by the plugin behind PhotoSwipe. In this case, it was hidden, as long as its CSS was loaded which instructed the browser to have it hidden when necessary. When you unloaded that CSS, there was no rule such as the one you used – .pswp { display: none; }
– to instruct the browser to also hide the content.
It looks like WooCommerce is loading it. Usually, the whole plugin is unloaded to avoid any HTML printing. But, if you need WooCommerce on the homepage for any other reason, then this is not an option to unload the whole plugin via “Plugins Manager”.
The best bet would be to unload all the assets related to PhotoSwipe, except the one that has the rule to make that content hidden which is located in the following CSS: /wp-content/plugins/woocommerce/assets/css/photoswipe/photoswipe.min.css – to be more precise, that’s the CSS that should be kept loaded (you can locate it inside the file): .pswp{display:none;position:absolute;width:100%;height:100%;left:0;top:0;overflow:hidden;-ms-touch-action:none;touch-action:none;z-index:1500;-webkit-text-size-adjust:100%;-webkit-backface-visibility:hidden;outline:0}
So, what you did was good to apply the CSS rule to make it disappear. Or, you could have left /wp-content/plugins/woocommerce/assets/css/photoswipe/photoswipe.min.css to be loaded, which is the easier option if you don’t have access to SFTP or can’t insert custom CSS through the Dashboard via a certain plugin or by editing the theme.
I hope it makes sense! Let me know if I can further assist you! Happy winter holidays!