I suddenly get an error I don't have permission to access this resource.

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was experiencing a 'Forbidden' error when switching languages on their website. They were concerned that updating plugins might cause the issue to recur.

Solution:
We first asked the client to check if the issue still occurred, suggesting it might have been a temporary caching problem. If the problem persisted, we recommended a step-by-step troubleshooting process:
1. Ensure a full backup of the website and database.
2. Deactivate all plugins except for WPML and its addons, then check if the issue still occurs.
3. Reactivate each plugin one by one, checking for the error after each activation to identify any conflicting plugin.
4. If the issue continued, we advised repeating the steps with a default WordPress theme.

Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Exception

This topic contains 4 replies, has 2 voices.

Last updated by Waqas Bin Hasan 1 year, 2 months ago.

Assisted by: Waqas Bin Hasan.

Author	Posts
February 20, 2024 at 3:37 pm #15323931
philipv-13	If I go this website hidden link And change the language to antoher language. I get an error: Forbidden You don't have permission to access this resource.
February 21, 2024 at 10:24 am #15326866
philipv-13	I did an backup. It works now, but the plugins are not updated now. Im afraid the problem will occure again when I do the updates. Not sure what the cause of the problem is.
February 21, 2024 at 10:25 am #15326867
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Hello Philip, Thank you for contacting the support. I just visited your website and switched to other languages without any problem: - hidden link - hidden link Can you please check again? Perhaps it was a caching problem or if there's a particular case when it happens (i.e. logged in to the site). Please let me know and I'll try my best to further assist you on the matter. Regards.
February 21, 2024 at 11:16 am #15327321
philipv-13	I did an backup, and now it works. So it should be a plugin that is conflicting. Im not sure if it is a WPML plugin. Couldn't you see something in the logs I send you? I see that there is also a 403 issue known. Could that be the case? https://wpml.org/errata/403-error-for-non-admin-users-in-wpml/
February 21, 2024 at 12:12 pm #15327724
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for the updates. I didn't find any logs except the debug info which doesn't point to such errors. If it could be another plugin, you can try the following steps to find out: IMPORTANT: Take full backup of your website and database beforehand. It is highly advised to try the following on a staging/dev site first, so your live website isn't compromised. - Deactivate all plugins except WPML and its addons and check for the issue. - Activate each plugin one-by-one, while keeping check on the issue after a plugin is activated. This way you'll be able to pinpoint a plugin having a conflict (or problem), if any. - If the problem persists, repeat the above steps with a default theme of WordPress (i.e. 2021 or 2024). Besides this, the other errata discusses about the issue with logged-in non-admin users and refers to the Advanced Translation Editor (ATE) jobs synchronization. I am not sure if your issue was the same. If it was the same and you can reproduce the problem, you can try the workaround mentioned in there.