Img urls not updating on migration

Ryan Putman

• April 02, 2025 16:45

A client on wpengine pushes from staging to production. 

When they do so some images show the old site url. Additionally it's an http address. I've fixed that issue with an action but it's still not great to have production serving images from staging.

I tried using your Replace URL tool to no affect. Nor did I see those urls when trying another search and replace plugin.

For reference you can see the src urls of images on this page: https://www.rigado.com/rigado-2024-newsletter/

Brizy 2.6.14
Brizy Pro 2.6.8

Thanks

0

• 

  Ariel H.

  • April 03, 2025 09:41

  Hi Ryan,

  Could you also please provide temporary access the second website so we can take a closer look? Kindly add us as an Admin user in your WordPress Dashboard and send the details to communitysupport@brizy.io: 

  Community Post link: https://support.brizy.io/hc/en-us/community/posts/25766434996882
  WordPress Admin URL:
  Username:
  Password:

  Best regards,
  Ariel H.

  0
• 

  Ryan Putman

  • April 03, 2025 16:27

  Hi Ariel,
  
  I'll reach out to the client for permission first but for clarification, which site are you referring to when you say "second website". 
  Production the "to" ==> https://www.rigado.com/
  or
  Staging the "from" ==> https://rigadostaging.wpengine.com/
  
  Thanks
  
  
  

  0
• 

  Ariel H.

  • April 04, 2025 09:03

  Hi Ryan,

  Apologies for the confusion in my last reply. We need access to https://www.rigado.com/.

  Best regards,
  Ariel H.

  0
• 

  Ryan Putman

  • April 04, 2025 16:08

  Hi Ariel,
  
  Will this access be used to make any changes or simply for discovery? We're a little worried about breaking changes/updates.
  
  If it's only for read-only type interactions I can create an account for you on Monday.
  
  Cheers,
  Jason

  0
• 

  Ariel H.

  • April 04, 2025 16:21

  Hi Jason,  

  Thank you for the update.

  The access will be used for both discovery and making necessary changes if needed.  We want to understand how the site was migrated. Could you let us know if any built-in tools from your hosting panel or a migration plugin were used?  

  Best regards,  
  Ariel H.

  0
• 

  Ryan Putman

  • April 07, 2025 16:13

  Hi Ariel,

  
  The client uses WPEngine and pushes (overwrites/clones) from a staging environment onto production with their managed hosting mechanics, ie doesn’t use a plugin.
  
  Since we’ve had Brizy updates cause critical errors in the past we’d prefer you don’t make any changes. If you have some suggested changes perhaps you could pass them along and we could do testing on our end.
  
  As a developer I can understand that this isn’t ideal but since any changes you made would be overwritten by the next staging push we’d need to know about them anyway.
  
  If you can assure me that no changes/updates will be made I can send a secure one-time link with a new admin user to communitysupport@brizy.io.
  
  Thanks,
  Jason

  0
• 

  Ariel H.

  • April 08, 2025 10:32

  Hi Ryan,

  Thank you for the update.

  It’s possible that WP Engine may not be fully compatible with how Brizy stores and references certain page data when pushing to the live site—especially media links and compiled content. This can sometimes result in broken layouts or missing assets after the push.

  To address this, we recommend trying the following on the live site after a staging push:

  1. Open the affected pages in the Brizy editor.  
  2. Make a minor change — for example, add 1px padding to a block that isn’t displaying correctly.  
  3. Save the page, then remove the padding or change it back if needed and save again.

  This process helps trigger Brizy to recompile the page content, which can often resolve issues like missing images or broken layouts caused during the push.

  Please give this a try and let us know the outcome.

  Best regards,  
  Ariel H.

  0

Please sign in to leave a comment.