Hey,
Can you confirm the by editing your page/posts, and checking its HTML view to confirm the image URL isn’t tied to staging URLs? Let me know if that is the case.
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":"http://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":[]} -->
Hey @clsimmon,
Here’s what I’ll suggest:
– Install this plugin to your WordPress: https://wordpress.org/plugins/better-search-replace/
– Do two search replaces, first to replace staging-url.com to production-url.com to replace all your staging links, if any, to production.
– Second to replace all http://production to https://production to fix the SSL issue.
– Once that is done, go to Otter Dashboard and click on Regenerate Styles button.
Everything should work after that. If it still doesn’t, make sure you’ve cleared any caching you’ve on your website.
Let me know if that helps!
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 http://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.
Hey @clsimmon,
Glad to know that worked. It’s always a good idea to do search/replace as staging to production from hosting might not always work, specially now in WordPress now that images are added as HTML comments in Blocks.
But regardless, glad to know it’s going on great now.
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 @clsimmon,
Thank you for sharing the steps you applied to resolve this problem. This can be a major help for other users with the same setup.
Regards,
Stefan
