For some reason embed scripts from the staging test site do not work on QC such as the QC Ice Cream test page. The embeds work on other sites including local Docker developer test rigs, the LanceCleveland.com blog site, and
This issue appears to have been temporary, and may be cause by a Web Application Firewall (WAF) on AWS blocking requests due to too many requests.
The issue is that any staging.storelocatorplus.com URL was coming back as a 404 but only when the request was made from the qc.storelocatorplus.com domain.
We need to keep an eye on this issue.
Summary
Turns out it makes a big difference how you test this. If you are logged into the staging site as any user, that login cookie is attached to all other browser sessions if you are using the same browser (ie Safari). If that is the case , your tests results will be skewed.
To avoid this you need to use a different browser or access the QC site while testing via an incognito or private browser session to ensure the cookies are not present.
If you do not log out of staging or have a way to clear the cookies (incognito/staging) then the URL request will cause WordPress to automatically attach the request to the logged in user. This will cause a mismatch between the requested map (in the case below the “Freshy” map) and the backend processing (in my case I was logged in as “Ice Cream” on staging), causing all kinds of odd issues.
Findings
Odd, the test embed for Ice Cream works, but the “Freshy” staging test on QC now fails with a 500 error with the theme file missing:
