-
Posts
-
We have a staging server and production server, and when migrating from staging to www, the production server has references to staging for the favicons and logos. I suggest an update to remedy this as relative links, as some are relative and some are not. If this is something we can resolve temporarily with our child theme in functions, please instruct us in detail on how we can resolve this issue.
This reply has been marked as private.Hi There,
Thanks for writing in! You can simple reset the Favicon and Logo on the Customizer.
Replacing all the instances of
staging.bluetriangletech.comwithwww.bluetriangletech.comin database should be done on migration process.Hope it helps, Cheers!
I appreciate the response, but this doesn’t solve the static links issue with the theme itself. We’re trying to avoid any extra plugins for simple fixes.
Our Ops guy takes care of migration, but it’s not with a tool like this. Everything is migrated by copying from one server to another, essentially, with everything intact. What we’re asking is for an update to the theme to include relative links to these files – not static. That would be best practice. In the meantime, we wanted to know where in the theme files that this can be changed to reflect a relative link for the logo and favicon files.
Thanks!
Hey there,
Thanks for updating! Regretfully, this particular customization request is outside the scope of our support as this is not related to an issue with the theme and instead has to do with your customization of it. As such, you will need to investigate this particular issue on your own or seek help from a developer should you not feel comfortable making these changes yourself. If you have any further questions about the theme, we are more than happy to provide you with assistance on these inquiries.
Thank you for your understanding.
This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.Hello Again,
Those links are the very basics of inserting an image in WordPress. In X, we always abide what is the standards of WordPress to avoid any other conflicts. I would simply suggest that you do the migration from staging to the production site the correct way. With WordPress, you cannot simply migrate it by copying from one server to another. You have to do other steps like search and replace after doing your manual migration. In our knowledge base, we have laid out a very detailed instructions on how you can migrate your site from one server to another without any hustle.
Based on the method that you used in migrating your site, you have done a manual migration (copying from one server to another). This method will only works out if you are transferring to a new host with the same domain name. There will be no changes in the urls since you will still be using the same domain name. In your case, migrating from staging to production would require more added steps which is the search and replace. By doing a search and replace for the old domain and replacing with the new domain you’ll also be altering the site_url and home url values in the database (Changing the Site URL) which will ensure that when you try to log into your site on the new domain it doesn’t try and redirect you over to the old domain.
Perhaps these links could give you more insight when doing migration especially with WordPress from one server to another:
https://community.theme.co/kb/cornerstone-migration/
http://www.wpexplorer.com/migrating-wordpress-website/Hope this explains it briefly.
Thank you very much for you understanding.
