Al.Janoubie

Hi @molongui

I would be glad to help troubleshooting, but it is a live website and will take some time to give it a try.

Meanwhile, I want to make sure of some points that may help.

• We use classic editor.
• No technical clue that Contributors MetaBox (nor Authors MetaBox) is responsible. It was the first thought as the issue take place with the same version that Contributors MetaBox is start to appear.
  I did disable it with no luck. So, It is not responsible. may be Authors MetaBox who is. (I will make a test asap)
• No AI providers is used. (I use TaxoPress to “Suggest Existing Terms” only) “TaxoPress AI” is just a tool name for TaxoPress plugin (WordPress Tag, Category, and Taxonomy Manager – AI Autotagger) https://taxopress.com/docs/introduction-taxopress-ai/
• As you see on pictures @ the above link, “TaxoPress AI” scans the entire post to show detected tags on boxes. Those boxes should appear with white color initially. And if you want to use a certain tag, you just click it and it would be added, turning the box color to green.
• When the conflict reproduced, TaxoPress Scans OK, but when you click any tag it halts (The Box goes gray & no tag added) looks like something blocks ajax call.

Sorry if I couldn’t express good enough as English is not my native language.
It is also a good opportunity to thank you for your amazing Molongui Authorship plugin (I use it since 4 years and It works great)

Thanks for help

If you allow me to suggest something for the next version. Appearing inside Settings-Footnotes menu is more valid than the stand alone one.

“Set & Forget”, should be your plugin slogan. We use it that way, such as a WP-core function, & it never failed us.

I really LOVE your work.

YES!
I’m using v2.3 now & confirming no issues.

Thanks, and take your time. v1.6 is doing the work fine.

Minor related bug: it dosn’t jump from footnotes to text starting from the 11th footnote. (only the first 10 anchors are working upwards)

and every anchored number is working fine (jumping from text to footnotes / downwards)

Confirming that Issues 2,3 been solved on V2.2 (Thank you for the new option / workaround which is very smart)

about #1 (or maybe two issues now!, and sorry for English is not my native language)

when we type ((some long text here, with some code inside, such as hyperlinked colored complicated text. )) it should envelop everything between (( & )), into something like [1], this is an example.. OK?!

What happened after upgrading, it is repeating some of the enveloped text after the number, to be something like that:

when we type [1] such as hyperlinked colored complicated text. )) it should bla bla bla

Those Bold text after the number, shouldn’t appear.

Also, the counting.. it count in a right way up to [10], then afterwards it count 2, 2, 2, 2, 2 >>> 3, 3, 3, 3,

You may see a live example from: here https://tabcm.net/16828/
It is not English website, but you could read the repeated numbers, or repeated text after numbers.

Thanks again for your fast respond, and please tell me when you done understanding the issues (It is a live website, & I cant stay on the new version for a long time)

What a fast respond from you all.
I’ll test the new v2.2 then be right back. (with all explanation needed for #1 )

Hello,

Any user can unsubscribe from any notification by setting it to “Muted”, Section “Profile > Editorial Notifications”

Yes, and it comes from “Auto Links” module

• Rolling back to 3.10 is a fix.
• Turning off “Auto Links” is a fix.

Yes, and it comes from “Auto Links” module
* Rolling back to 3.10 is a fix.
* Turning off “Auto Links” is a fix.

It worked great,

Thank you, @wpkube

Confirming that rolling back to 3.7.1 will solve this issue

Same issue here.

It happened when I open Auto Links only,
No need to disable the whole TaxoPress to stop repeating. Just remove all checkboxs on page [Enable this Auto Links instance for:] which is found on [TaxoPress – Auto Links – Edit Auto Links – Post Types]

I’ve tried to set many configurations for “Auto Links” to narrow the troubleshooting, but no luck.

And Yes, I’m using non-Latin characters too, but we haven’t face such issues since using UTF charset