Эта тема решена. Вот описание проблемы и ее решения.
Problem: After moving your site from a local environment to a live server, you are encountering 405 (Method Not Allowed) errors in the console. These errors are affecting site functionality, including updating permalinks and localization issues for translations. Solution: We recommend updating your WPML to version 4.8.3, as this has resolved similar issues in our tests. You can find the latest version in your account under My Account → Downloads. For detailed instructions on updating WPML, please visit http://wpml.org/faq/install-wpml/. If the update isn't visible, click the Check for updates button under Plugins → Add New Plugin → Commercial.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket at WPML support forum.
Это форум технической поддержки WPML – плагина для многоязычной WordPress.
Доступно для чтения всем, но только клиенты, купившие WPML, могут оставлять сообщения. Сотрудники WPML отвечают на сообщения форума 6 дней в неделю, 22 часов в сутки.
Предыстория вопроса:
I moved my site from a local environment to the main site at скрытая ссылка. After the move, I started experiencing issues with 405 errors in the console. This is affecting the site's functionality, including the inability to update permalinks and issues with localization for translations. I followed the usual process, moved the site using a method I always use, reconnected the key, but the error persists.
Симптомы:
405 (Method Not Allowed) errors are appearing in the console, preventing proper site functionality and updates to permalinks.
Вопросы:
How can I resolve the 405 error after moving my site?
Why is the site not functioning correctly after the move?
How can I fix the localization issues for translations?
Could it be that your server is blocking the requests? Also, could you please share how you performed the migration?
A 405 means the server/WAF disallows POST. Check if the Firewall is not blocking the requests. I would also check/test the .htaccess file in the WordPress root with the default WP block:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
If you’ve moved the site to a new location, you should see a migration banner when you try to access WPML → Translation Management. Please follow the steps there to complete the migration to the new URL.
I have the default htaccess, just like you sent, there was a banner. I did everything as usual. If the vpm plugin is enabled, it doesn't matter what I do, whether I update permalinks or something else, I get a 405 error. As soon as I disable the plugin and update everything, it works correctly. Is it possible to understand where the error is coming from?
Yes, when the wpml plugin is enabled, a conflict arises and these errors occur. When it is disabled, everything works correctly.
The migration was done using the wpvivid plugin, which I use all the time, and I have never had any conflicts with your plugin or any other. I can try to do the migration again, or reinstall all the plugins from scratch.
I recommend starting by replacing plugins first. Then, if possible, try migrating using the Duplicator plugin, which I use regularly because it transfers the entire site, including files and the database.
If there is an opportunity, try testing it on an alternative server.
I completely reinstalled WPML from the website and connected the key on the local server (which should be error-free). The error persists. I am attaching a screenshot.
I need to request temporary access (wp-admin and FTP) to your site—preferably to a test site where the problem has been replicated if possible—in order to be of better help. When you log in to leave your next reply, you will find the needed fields below the comment area. The information you will enter is private, meaning only you and I can see and access it.
Please include the steps where the problem can be seen.
Can we talk on the phone or resolve this via text so that access is not granted?
I can provide all the necessary information. Let me explain the problem again.
Everything works on the local server, but the error shown in the screenshot above occurs. On the actual website, /wp-admin/admin-ajax.php 405 (Method Not Allowed) appears in the console, but if you just go to the URL, everything works correctly. Similarly, if you disable wpml, the website works correctly.
Yes, I understand the problem. I still believe it might be related to a server configuration issue — for example, the 405 (Method Not Allowed) error on wp-admin/admin-ajax.php.
Could you please try adding the following constant to your wp-config.php file and see if it helps?
