Update url after moving to production
Hi
I have used Duplicator Pro to move our Brizy powered Wordpress site from development (dev.domain.com) to production (domain.com).
After moving the site, I need to update all urls across all pages that are pointing to dev.domain.com. I have tried with a lot of different "search and replace" plugins, but so far without luck.
If I check the code directly in the database, I can see that the placeholder "{@brizy_SITE_URL_PLACEHOLDER@}" is used in all the places where the development domain still show up, which I guess is why the "search and replace" plugins didn't work.
But my question now is: Why is the placeholder still being replaced with the development domain when a page is loaded on prod, and how do I change it?
(I have of course emptied the cache, and the development domain is also still showing if I edit a page with Brizy on prod and check the url of one of the links)
I very much hope for a quick answer, as this issue is preventing us from going live!
Thanks in advance
-
Hi,
Yes, we know about this inconvenience. When in the URL of the element is added such as link "https://www.site.com/page1" then it is something like added in the hardcode mode and when the site is migrated the links are the same as in the previous site. We recommend using the short syntax of the URL and add the links in such a way "/page1", or if you want to link to the homepage to select the Dynamic URL "Site URL" https://jmp.sh/XfnCBlt.
Best regards,
Sandra0 -
Hej Sandra
Thanks for your answer.
It makes perfectly sense that links that have been entered manually on a Brizy page stay the same when the site is migrated, but I can't believe that it is not possible to update the link through some kind of semi manual operation?As I mention in my original post, I can see from the code in the database that the urls are in fact stored as "{@brizy_SITE_URL_PLACEHOLDER@}/name-of-page". Therefore I am thinking that it must be possible to somehow update the domain by updating the value of that placeholder. I am not able to figure out where the value of the placeholder is stored however. Maybe you can tell me that?
Thanks
Mathias0 -
This "{@brizy_SITE_URL_PLACEHOLDER@}/name-of-page" is working when the URL is added in the shorter syntax like "'/page-name". In this case, Brizy will add dynamically the URL of the site before the "/page-name". When the URL address is added fully, in this case this option isn't applied.
I'm sorry if this created you some inconveniences. Let us know if we can help you with something else.Thanks!
Best regards,
Sandra0 -
I would like more clarification on this. Is it possible to programmatically update the URLs for images after a site goes live? Thank you for your help.
0 -
Hi Seb,
Thank you for contacting us.
Here is my suggestion to fix the issues with your site migration.
While Duplicator is a reliable plugin and is widely used, its migration process is error prone since it follows a partly automated and partly manual process. Mistakes made in the manual part of the process can result in a faulty migration.
If you repeat the migration process using a tool which follows a fully automated process you may not find any error. Please consider using one of these plugins to carry out a fresh migration. Migrations carried out using these plugins hardly ever result in any error.
1. https://wordpress.org/plugins/all-in-one-wp-migration/
2. https://wordpress.org/plugins/wpvivid-backuprestore/
Best regards, Nelea.
0 -
I used all-in-one-wp-migration/ and we have the same issue where the links don't change.. Maybe you can have an option in Bizy menu show the old URL and ask to replace with new.. and execute, Since I assume Brizy would know where all the path names are stored. For a site with many pages this is really not ideal.
0 -
Hi Dan,
Hyperlinks entered manually using the Brizy link element do not migrate when using a migration tool. Brizy does have a tool which can replace old URLs with the new URLs.
In your WordPress Dashboard, under Brizy - Tools, you can access the 'Replace URL' tool. https://jmp.sh/hhczitx
0
Please sign in to leave a comment.
Comments
7 comments