This feature works only with activated JavaScript. Activate it in your Web brows

So, further information ??

This error is shown on the post edit screen (classic editor) for the Suggested Tags Box

It appeared after the last update

It occurs in Edge & Chrome Browsers

The following error information appears in the console. Please let me know if you need more info

Uncaught TypeError: Cannot read properties of undefined (reading 'suggest_term_use_local')
    at HTMLDivElement.<anonymous> (helper-suggested-tags.js?ver=3.6.2:8:48)
    at Function.each (load-scripts.php?c=0&load%5Bchunk_0%5D=regenerator-runtime,wp-polyfill,wp-hooks,jquery-core,jquery-migrate,utils&ver=5.8.4:12:3003)
    at s.fn.init.each (load-scripts.php?c=0&load%5Bchunk_0%5D=regenerator-runtime,wp-polyfill,wp-hooks,jquery-core,jquery-migrate,utils&ver=5.8.4:12:1481)
    at HTMLDocument.<anonymous> (helper-suggested-tags.js?ver=3.6.2:3:34)
    at e (load-scripts.php?c=0&load%5Bchunk_0%5D=regenerator-runtime,wp-polyfill,wp-hooks,jquery-core,jquery-migrate,utils&ver=5.8.4:12:30038)
    at t (load-scripts.php?c=0&load%5Bchunk_0%5D=regenerator-runtime,wp-polyfill,wp-hooks,jquery-core,jquery-migrate,utils&ver=5.8.4:12:30340

Thanks for reporting this @michael98

– Is happening on a Windows computer?
– Have you tested to see if this is a theme or a plugin conflict, and not just Classic Editor?

Thanks for the reply.

It happens on browsers on both Windows and Android.

It happens in both the classic and block editors.

It only occurred after the last Taxopress update.

I am currently going through a testing process with other plugins to see if I can find which may be conflicting

Thanks @michael98

Yes, please let us know. We’ve had 2 reports of this but can’t recreate it in our testing.

@michael98

It looks like you’re using the legacy option.

Try upgrading to the “Suggest Terms” option:
https://taxopress.com/docs/introduction-to-suggested-tags/

@stevejburge Thanks for the possible solution.

We have never used the legacy options and currently only use the Suggest Terms option, to suggest Tags for posts. We use the ‘Suggest existing terms on your site’ option, and do not use the show existing terms option.

I have tried removing and reinstalling Taxopress but the options are already set to how we had them before. I was wondering if there was a way to remove everything and have a complete fresh install to try?

(In the meantime we have reverted to 3.6.1 and all is working as it did before)

• This reply was modified 2 years, 5 months ago by michael98. Reason: Added info on reverting

Thanks @michael98

This remains something we can’t recreate in our testing.

Are you sure your browser(s) isn’t blocking Javascript?

No, we have tried multiple browsers and operating systems as we have multiple authors around the country, all getting the same issue.

We will have a look again at plugins/cache settings etc see if we can find anything.

There is some issue preventing the script from running/loading (as seen in the console error above) Not sure what changed between 3.6.1 and 3.6.2 but we are working fine with 3.6.1

@michael98 Can you re-create the issue on a second site?

We will try creating a test site with similar plugins etc to see if the issue occurs there

I had the same bug. The problem is at metabox function of inc/class.admin.suggest.php
There the plugin adds the container attributes using esc_attr_e instead of esc_attr. esc_attr_e retrieves the translation for the key_index, and when there are translations for “0” the metabox logic will fail.

Hi @sarhugo @michael98

We have a release coming up on monday that fixes this issue but pending the time, here’s a beta package you can test to confirm this issue is fixed.

https://drive.google.com/file/d/1Mb8cHze7cS5U89luxbBIT6GTcf580CF6/view?usp=sharing

Just to confirm this appears to have fixed the error, thankyou !

I know you couldnt recreate this in your testing, are there any clues as to why some of us had the problem but not everyone? (I am thinking was it because of the WP version or classic editor or something?)

Hi @michael98. From what we can tell, this appeared only on sites that ran in certain languages. It was related to a recent update which allowed more than one “Suggest Terms” metabox.