Skip to main content

Image urls in global blocks don't update after deployment

Mathias Hoffmann

Our website is hosted on Siteground, which has a built-in staging service. When deploying the staging website to the production url, the urls in the image paths in global blocks are no longer updated to the new domain. The issue started last summer, when the new and "improved" Brizy compiler was launched.
Since then, I've tried every "search and replace" tool out there (including the one that comes with Brizy), but nothing seems to work.

The only work-around is to manually edit and save all the global blocks, which is not feasible on a large website like ours,

I have tried to look for the content of the global blocks in the database, but I am not able to find them. Can you please enlighten me on how the content of the global blocks is stored - or better yet, provide me with a fix to this extremely annoying issue?

Thanks in advance

0

Comments

5 comments

Date Votes
  • Ariel H.

    Hi Mathias,  

    Thank you for reaching out to us.  

    We sincerely apologize for the inconvenience this issue may be causing. At the moment, we don’t have a solution to share, as our team is still working on it. Rest assured, we will keep you updated as soon as we receive any progress or insights.  

    Thank you for your understanding and patience.  

    Best regards,  
    Ariel H.

    0
  • Mathias Hoffmann

    Hi Ariel,

    Thank you for your answer.
    Just be sure that I understand you correctly: This is a known bug, but after six months (if it was introduced last summer, as I suspect) you still don't have a fix ready? 
    This is quite alarming I must say, that a serious bug like this, can remain unresolved for that long 😯
    I really hope you will soon come up with a solution!

    You also didn't answer my question: How and where are the global blocks stored? 

    Best regards,
    Mathias

    0
  • KC George

    Hello Mathias,

    You mentioned "I've tried every "search and replace" tool out there (including the one that comes with Brizy), but nothing seems to work" Have you tried using the WPVivid free plugin to migrate your staging website to production? This is an option worth experimenting as this tool seems to migrates file paths better than other tools. The Brizy "Replace URL" tool has a limited scope of migrating external URLs added as hyperlinks to buttons, text, images etc.

    Your question about "how the content of the global blocks is stored" is beyond scope of our support. We only provide assistance for using the product's user interface.

    0
  • Mathias Hoffmann

    Hi K C,

    Last night I did a thorough analyze of a dump of the entire database, and the wrong file paths are nowhere to be found in the dump. This of course makes me even more curious about the inner workings of the global blocks. Is the html code of the global blocks actually stored in the cloud (in other words: on your servers), and is that why it is so impossible to find and update the code manually?
     
    I don't have a problem with the global blocks being stored on your servers (just like the saved blocks obviously are), but it would definitely be nice to know if that is the case.

    Best regards,
    Mathias


    0
  • Ariel H.

    Hi Mathias,

    Thank you for the update.

    The paths for global blocks are not stored directly in Brizy Cloud. Instead, they are based on the paths defined in the WordPress options table in the database. However, when global blocks are used, the paths need to be recompiled. This explains why manually editing and saving all the global blocks resolves the issue—it triggers the recompilation process to update the paths correctly. 

    To resolve this issue, please try this approach before migrating your site:

    1. On your staging site, downgrade Brizy and Brizy Pro to the versions provided in this link:  
    https://drive.google.com/drive/folders/1i-HcSLch4ED2HfMznXIgDOT7TAXXsVsG?usp=sharing  

    2. Disable third-party plugins except Brizy and Brizy Pro

    3. Verify that all pages are working, update any page so the database registers the version change.

    4. Proceed with the migration.  

    5. Once the migration is complete, update Brizy and Brizy Pro to their latest versions.  

    6. Re-enable all plugins and test your site to ensure everything is working as expected.  

    This is demonstrated on this screencast - https://youtu.be/eAy5Uu4K--4

    Please give this a try and let me know how it goes.  

    Best regards,  
    Ariel H.  

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

Ask a Question