Home›Support›English Support›[Resolved] Switch from English to French is either causing a 404 error or a blank page
[Resolved] Switch from English to French is either causing a 404 error or a blank page
This thread is resolved. Here is a description of the problem and solution.
Problem: After launching a new site, switching from English to French with BuddyPress activated causes a 404 error or a blank page. The issue is related to object caching with Redis. Solution: We recommend the following workaround: 1. Ensure you have a complete backup of your site. 2. Access your site's files. 3. Navigate to the
/wp-content/
folder and create a
mu-plugins
folder if it doesn't exist. 4. Inside the
mu-plugins
folder, create a PHP file named
wpml-non-persistent-cache.php
(or any name you prefer). 5. Insert the following code into that file:
We've just launched our new site and running into a couple of issues where the switch from English to French is either causing a 404 error or a blank page - both issues are with Buddypress
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello again,
Thanks for the confirmation.
I have double-checked the problem, but so far I haven't been able to find a fix. I asked my colleagues to take a look to see if there's anything I'm missing.
For your information, just out of curiosity, the problem does not seem to happen in a copy version: hidden link. Right now I am checking internally if this could be a server issue.
If you want to test it yourself, the credentials are the same as in the original website. I also would suggest that your team try to migrate the website to a local server and see if the problem happens there.
Regardless, I'll come back here as soon as one of them answers me (which shouldn't take long). Thank you in advance for your patience!
Yes testing your link and it seems to work fine. Not sure how that's possible if it's a direct copy of the website. I'll wait to hear back from you with your findings.
So strange...would this have anything to do with the switch from the cloudways url to catca.ca?
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hi Darryl,
Thanks for your patience.
As mentioned previously, we suspect it might be a server side issue or something specific to your installation. By chance, would you have a staging version of the website, where we could make more complex tests, like disabling all plugins except the needed ones? We would check as well a possible issue with the .htaccess file.
Please let us know if you have a staging website, or if it is possible to create it. I am marking your next response as private, so that you can enter the login info for it.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hi,
I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at this issue and will try to find a solution.
I will get back to you as soon as I get an answer from them.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello Darryl,
Thanks for your patience, and sorry about the late response.
The redis plugin loaded in the mu-plugins folder was not working for us, and this was the reason why we couldn't replicate the issue in a different server.
We had to deploy another plugin, so that Redis cache is enabled, and this way we could see the issue. So the problem is the object caching.
In the meantime, we have a workaround for you. Please follow these steps:
- Make sure to have a complete backup
- Get access to your files
- Go to /wp-content/ folder on the site and create a folder named mu-plugins if there is not one already
- Inside the mu-plugins folder create a PHP file named "wpml-non-persistent-cache.php", or any name you want, and place the following code on it:
Hi Mateus - thank you for that and we will try the code today. Question for you - could we not just disable the object cache that is within Cloudways. Is it necessary to have installed?
Again, thank you so much for a solution. It's greatly appreciated.
after all that investigation on your end, all that I had to do was flush and turn off the object cache plugin on the main dashboard in the admin panel and it's now working correctly. lol.