clsimmon

After further testing, there is no need to make any database updates. If you’re using Neve with SiteGround, and are performing a full deploy from staging, you must go back into your production environment and Regenerate Styles within the Otter Dashboard and then purge SG cache. This appears to eliminate any remaining staging references.

Hi Hardeep, this was a good tip. Thank you. I ended up doing something similar but instead using phpMyAdmin and searching for ‘staging2’. I found within the eay_options table and within the option_name of _transient_neve_dash_useful_plugins there appeared to be some type of integration of the Optimole capability.

There, I found several instances of the https://staging2 URL references. Once I changed all of those to https://www. my site seems to be be rid of those references and I can now put staging2 URL under protection without the production environment making any image calls to it. All is now working.

I am thinking that SiteGround for one reason or the other cannot update this table or this option_name during full deploy from staging to production. This is something Neve might want to look into.

When viewing the page using Gutenberg code editor, it appears to not have staging2 references, but does have http vs https. However this HTLM appears to be within a comment. Note the following within editor:

<!-- wp:themeisle-blocks/advanced-columns {"id":"contact","columns":1,"layout":"equal","padding":{"top":"10px","bottom":"10px","left":"20px","right":"20px"},"paddingTablet":{"top":null,"bottom":"150px","left":"15px","right":"15px"},"margin":{"top":"20px","bottom":"20px"},"columnsWidth":1170,"horizontalAlign":"center","backgroundType":"image","backgroundImage":{"id":717,"url":"https://austinsketch.com/wp-content/uploads/2019/07/path.jpg"},"backgroundPosition":{"x":"0.50","y":"0.00"},"backgroundRepeat":"no-repeat","backgroundSize":"cover","backgroundOverlayOpacity":85,"backgroundOverlayColor":"#262732","backgroundOverlayPosition":{"x":"0.00","y":"0.00"},"align":"full","className":"","otterConditions":[]} -->

Hi, yes you are on to something. I was running the latest Gutenberg release but when I deleted the plug-in, the author’s name returned as it should.

Thank you. I will set the header page to No Index with AIOSEO and give that a try.