Problem: The client was experiencing issues editing pages after starting to use WPML for translations. The conflict was identified with the WP File Manager plugin. Solution: We determined that deactivating the WP File Manager plugin resolved the access issue to the pages. This issue has been introduced in WP File Manager 7.2.3 and fixed in 7.2.4 that was released on the same day.
Updating WP File Manager to the latest version resolves the issue.
Ref: https://wordpress.org/support/topic/access-denied-99/
However, please note that the solution might be outdated or not applicable to your case. If the problem 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. Should you need further assistance, please do not hesitate to open a new support ticket with us.
Problem:
The client is facing issues with translations not appearing correctly on the live site, although they work fine on the staging site. Specifically, the problems are with Product Add ons, ACF labels for products, and footer widgets not being translated. Solution:
If you're experiencing similar translation issues, we recommend you follow these troubleshooting steps after ensuring you have a full site backup:
1) Navigate to WPML>>Support page and click on the Troubleshooting link.
2) On the Troubleshooting page, under the *Clean up* section, sequentially click and process the following options:
- Clear the cache in WPML
- Remove ghost entries from the translation tables
- Fix element_type collation
- Set language information
- Fix WPML tables collation
- Assign translation status to duplicated content
- Fix terms count
- Fix post type assignment
- Cleanup and optimize string tables
- Show custom MO Files Pre-generation dialog box and Generate .Mo files
- Synchronize local job ids with ATE jobs
- Synchronize translators and translation managers with ATE
3) If the issue persists, go to WPML>>String Translation and resave the translations for the strings in question.
4) Clear all types of caches.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem continues, 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. Should you need further assistance, please open a new support ticket.
