Can you please let me know if this issue happens even when only the WPML plugins are active and you are using a default WordPress theme?
Please try the following steps so that we would test for a compatibility-related issue:
- create a full website backup
- disable all plugins except WPML and its add-ons
- check if the issue is happening again
- if it's not, reactivate your plugins one by one, checking every time if the issue shows up again so that you can understand which plugin is causing that issue
If the issue happens even with the non-WPML plugins disabled:
- leave all the non-WPML plugins deactivated
- switch to a default theme like TwentySeventeen
- try to recreate the issue now
If you have the chance, it would be best to do this in a staging (testing) environment.
Please let me know how that goes and if following any of these steps solved your issue or brought any change.
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of the site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box.
This is WordPress trying to guess the URL that you are trying to access.
In the main menu, in the BE language, the "Blog" page sends to the correct "be/blog-be" version, and also all the posts on that page send correctly to the "be/blog-be" version for each post.
Also, if you go into post (this one for example: hidden link) and click "edit post" in the top bar, you will be taken to the backend, in the page where you can edit the post and you will see at the top that the permalink shows correctly the "be/blog-be" version (attaching screenshot).
So this is just WordPress trying to serve you the content no matter if you manually type that URL in that way, is not coming from WPML.
You can also scan the database and you will see that there will not be "be/blog" versions anywhere.
I can also see that you are experiencing an error in the last reply that you sent, together with the credentials and the screenshot.
Per our Support Policy, we can handle only one issue per ticket.
Continuing with one issue per ticket helps not only supporters to focus on one issue at once, but also enables other users to find solutions to their questions faster.
Hi, We had provided you the credentials, but you didn't told me what changes you have made, can you please tell me all the tasks done by you as there's new plugin added in the site
No, I did not touch that setting as that would make your site indexable by search engines and that's not something someone would want when this is a staging/testing site.
We never touch settings like that on our customers' websites.
As I confirmed above, that URL shouldn't exist in the database (please check the database and see if you find links that contain "/be/blog") - that's just WordPress guessing automatically what it thinks you want to see.
