I built SponsorsFreak.com in a staging environment by cloning an existing working ListingHive/HivePress installation. Once the site was completed, I migrated it to SponsorsFreak.com using the Softaculous cloning tool, as I have successfully done with other sites.
Since the migration, I’ve been seeing a very strange intermittent issue with the header/navigation.
The dropdown indicators/icons next to menu items sometimes display normally, but at other times they appear as small square boxes or disappear entirely. The site may display correctly on an iPhone while appearing incorrectly on a Galaxy S24.
More importantly, when this problem occurs, the front-end HivePress user/Admin login also does not work, so the issue appears to affect more than just the visual menu icons.
I have also seen the problem on a desktop Mac (see screenshots). Strangely, after I log into the WordPress dashboard as Administrator and update a plugin or make another change, the missing navigation/login functionality almost always reappears.
I have several other HivePress/ListingHive sites using essentially the same plugin stack, and none of them have this problem.
I have already checked some of the obvious possibilities. WP-Optimize was inactive and has now been removed. SponsorsFreak does have more Code Snippets than some of the working sites, so I am comparing those as well, although none appear related to the header or navigation.
Could this be caused by something left over from the staging-domain migration, such as cached CSS/JS, old URLs, fonts/icons, theme assets, or HivePress settings?
Is there anything HivePress-specific that should be reset, regenerated, or refreshed after cloning/migrating a ListingHive site to a different domain?
I previously confirmed with HivePress support that my lifetime license was expanded to allow use on up to 9 websites/domains, so SponsorsFreak.com should be covered under that license.
Since SponsorsFreak was originally built on a staging domain and then cloned to SponsorsFreak.com, could the staging-domain activation or migration have left behind any license/domain information that might cause this behavior? Should I remove/deactivate the license from the staging installation after migration, or would the license have no effect at all on front-end assets, icons, navigation, or login behavior?
Thanks for your assistance.



