Hi Kor, I just tried to push staging 13 (the copy we've been working on) live, and immediately all of the old issues -the ones we just spent weeks repairing- popped up again... I've had to restore a backup. It is really unworkable this way. I can't have a perfectly working staging copy break upon pushing to the live website..
hidden link hidden link hidden link hidden link hidden link
I'm sorry to learn about the situation. However, it appears that the actions taken may not align with the process of "transitioning the site from staging to production." Ideally, the website should remain functional without any disruptions and should mirror the content found in the staging environment.
To address this issue, I would recommend taking the precautionary step of creating a backup first. Afterward, I suggest reaching out to your hosting provider for guidance and assistance in executing the proper procedure to seamlessly push the site from staging to production.
Hi! It's around midnight, so I've done some testing to narrow down the issue while everyone is asleep. It seems that the issue is not related to moving the site ground staging to live after all. It looks perfect right after the migration. Rather, the pages break only after switching from translations on different directories (worlmasterpianists.nl/en) to using different domains. My original language is on worldmasterpianists.nl and the English translation should be on worldmasterpianists.com. Please advise 🙂
Hi Kor, I can't really show you on a live website... I did this VERY quickly in the middle of the night, so hopefully I avoided visitor traffic. On the staging copy I don't have a .com available. I have asked Siteground for assistance, but it is not possible to use different domains since the staging websites come with a specific server configuration that cannot be changed or modified.
The only way I would be willing to do it on the live is if we do it around 1AM Amsterdam time... But it would be better if you downloaded the site and tried to reproduce it on your end.
Certainly. I pushed the website live (full deploy). Website looked perfect with the directory /en for english. Then I went into the WPML settings to set the english translation to the .com. After that old the old issues were back (screenshots from previous message)
Ok, you mentioned that the issue only shows up when you "set the English translation to the .com". I need more information about this as I cannot configure this on a local dev site.
Alright, let's consider implementing these steps either during a maintenance window or when the website experiences low traffic:
1. Modify the "Language URL format" to "Different languages in directories"
2. Perform a thorough website inspection to ensure all functionalities remain intact.
3. If the site functions correctly, transition the staging site to the live production site.
4. Verify that everything still functions as expected.
5. If all is well, update the "Language URL format" to "Language name as a parameter"
I don't want to set up the name to parameters though. It has to be set to different domains. I did this last night (after migration to live) and things broke (see screenshots)
1. pushed staging13 to live
2. checked the translated pages, they looked good
3. changed the URL structure from "Different languages in directories" to "Different domain per language"
4. checked the translated pages again. They were broken.
Please understand, I cannot put a broken website live. As I explained earlier, I would only be willing to do it at night, and very quickly. We would have to be on a call or something and it would have to between 1AM and 5AM Amsterdam time. I would be willing to sacrifice a night's sleep for it. But it would be easier if you download the website, set the language to different domains and see for yourself.
I comprehend your message. Regrettably, attempting to download the website and configuring the "Different domain per language" option will not function on our development sites or local installations. Could you verify if you can reproduce this problem on your staging site at hidden link ?
Moving forward, here are the troubleshooting steps you can follow during your nighttime:
2. Create a backup of the site and perform a migration from staging to production. Trigger the error by using the language to different domains option.
3. Navigate to your server's wp-content folder and make a copy of the debug.log file and share over using dropbox or google drive.
4. Send me the debug log file, and I will investigate the root cause of the issue.
5. While waiting for me to analyze the debug log, restore the live site.
The topic ‘[Closed] Website breaks after pushing the site to production from staging.’ is closed to new replies.
