Andreas W.
Sostenitore di WPML dal 12/2018
Lingue:
Inglese (English )
Spagnolo (Español )
Tedesco (Deutsch )
Fuso orario:
America/Lima (GMT-05:00)
|
Hello,
According to my test, this error only occurs when creating new content and saving it for the first time.
After closing the WordPress Editor and opening it again the error does not longer occur.
Can you please confirm?
Further, I do not believe that this is a serious issue, further, the JS error is not referring to WPML, it is referring to a script inside WordPress Core, which means, that it could be that you will have a similar issue with another plugin when running WordPress in its current version.
The issue occurs in the WP Core file:
/wp-includes/js/dist/core-data.min.js?ver=d8d458b31912f858bcdf
Take note, that this further is minified (cached) file.
Similar issue in WP 5.9:
https://core.trac.wordpress.org/ticket/54553
https://core.trac.wordpress.org/changeset/52316
Now, if you insist I can offer to escalate this internally for further revision, but I need you to confirm that we speak about the same issue.
The issue only occurs on content creation, but is no longer visible when editing the content for a second time in the WordPress Editor, correct?
- Issue only occurs on first content creation
- Closing and opening the WP Editor solves the issue
- Even refreshing the bowser and editing and saving the post again solves the issue on my test after the first content creation.
Best regards
Andreas
|
christianc-8
|
Hi,
I confirm that the error occurs only when you add a new post/page/cpt before saving it for the first time. Then it disappears. And - as previously said - it seems to be effectless for now.
I read those posts on WP forum before contacting WPML assistance, but that error was a little bug in WP core fixed in the latest version. I can say that I've never seen it before.
Then the fact is that now - according to my experience - only latest WMPL causes that error again. I've been using some of the most common plugins like Wordfence, SEO by Yoast, ACF Pro, but none of them causes similar errors. Only WPML. It should be investigated.
Thank you indeed for you support.
Regards.
|
Andreas W.
Sostenitore di WPML dal 12/2018
Lingue:
Inglese (English )
Spagnolo (Español )
Tedesco (Deutsch )
Fuso orario:
America/Lima (GMT-05:00)
|
Hello,
Thank you for your confirmation.
Yes, indeed - it is an odd error but actually occurs in a Script that comes from WP Core, and only occurs when WPML Multilingual CMS runs on the site - anyhow, it could be that similar issues occur with other multilingual plugins as well.
I have escalated this issue internally for further revision and I will let you know once I received feedback from the team on this matter.
Best regards
Andreas
|
Andreas W.
Sostenitore di WPML dal 12/2018
Lingue:
Inglese (English )
Spagnolo (Español )
Tedesco (Deutsch )
Fuso orario:
America/Lima (GMT-05:00)
|
Hello,
As workaround:
Add this code to the functions.php of your child theme (if you do not have a child them use any code snippet plugin.)
function wpmlsupp_10460_fix($q) {
if ($q->is_main_query()) {
$q->set('suppress_filters', true);
}
}
if (
!empty($_GET['_wp-find-template'])
&& !empty($_GET['p'])
&& !empty($_SERVER['HTTP_REFERER'])
&& strpos($_SERVER['HTTP_REFERER'], 'wp-admin/post-new.php') !== false
) {
add_action('pre_get_posts', 'wpmlsupp_10460_fix');
}
The issue has been escalated to our development team and should get solved in a future version of WPML Multilingual CMS.
Take note, that you might run into a similar issue on translated posts if the post shares the same slug as the original content. Usually, the slug is by default created based on the post title, so you should not really run into this problem unless both contents have the same title.
Best regards
Andreas
|
