I tried to create a category.
I get a javascript error :
"wp-seo-premium-quickedit-notification-352.js
Uncaught TypeError: Cannot read property 'replace' of undefined"
In the js function wpseo_get_item_id(), the wpseo_get_active_editor() never returns "" (empty string).
Same for me, all latest versions, affects attribute creation too. Can't create either with Yoast SEO Premium activated
Uncaught TypeError: Cannot read property 'replace' of undefined(…)i @ wp-seo-premium-quickedit-notification-352.min.js?ver=3.7.2:1f @ wp-seo-premium-quickedit-notification-352.min.js?ver=3.7.2:1g @ wp-seo-premium-quickedit-notification-352.min.js?ver=3.7.2:1k @ wp-seo-premium-quickedit-notification-352.min.js?ver=3.7.2:1(anonymous function) @ wp-seo-premium-quickedit-notification-352.min.js?ver=3.7.2:1dispatch @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:3r.handle @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:3trigger @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:3a.event.trigger @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:9(anonymous function) @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:3each @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:2each @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:2trigger @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:3n.fn.(anonymous function) @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:4fetch_complete @ acf-input.min.js?ver=5.4.4:3complete @ acf-input.min.js?ver=5.4.4:3i @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:2fireWith @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:2y @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:4c @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:4
I'm having the same problem. I think it's only happening where I have Advanced Custom Fields on the Taxonomy.
Other Taxonomies that I'm not extending with ACF still get the error, but it's allowed to continue to create the term.
+1 for this issue. Trying to create a new category and it's blocked by this JS error.
Can also confirm the same error. Wordpress 4.6.1 and Yoast Premium 3.7.2
Hey guys, come on! It's been a month passed since this issue has been reported. This is a critical error as it breaks WP functionality!
Same for me. Any results?
Is support going to fix this problem?
I get the same error...
+1
+1
+1
If these issues are specific to the _premium plugin_, we ask that you please contact Premium support via [email protected]. When you respond please include the following:
This repository primarily handles the free plugin.
+1 Same here. I know guys you love emails but 13 people having reported the issue, would be useful to have at least a private forum or post about the solution if this doesn't apply to the free version.
Well, for anyone following this the safest temporary workaround is to disable javascript just for the time needed to create a new category.
Something like
https://github.com/maximelebreton/quick-javascript-switcher comes really in hand to do the job quickly.
Temporary workaround:
function yoast_bug_5949_tmp_fix(){
// # only register and queue scripts & styles on POST edit screen of admin
$current_page = get_current_screen()->base;
if($current_page == 'edit-tags') {
wp_dequeue_script('wp-seo-premium-quickedit-notification');
}
}
add_action('admin_enqueue_scripts', 'yoast_bug_5949_tmp_fix', 99999);
First, we want to apologize for not responding to this issue any sooner. As my colleague Pat pointed out, this is a bug caused by our premium plugin, therefore the communication about it has been done in a private repository. Nevertheless we should've responded to you, for that my sincere apologies.
The issue has been fixed and will be shipped with Yoast SEO Premium 4.6, which is scheduled for next week. Thanks for your patience.
Most helpful comment
Temporary workaround: