No Longer Analyzing Post Content

  • Resolved mikemac29

    (@mikemac29)


    2 years ago

    Not sure if this is something related to a plugin conflict or what, (though I will note that I haven’t added any new plugins) but in the last week or so, there are no longer any Suggested Terms or Auto Terms being applied to the post content. The only time a term gets suggested or added automatically is when it is in the post title. Previously, it worked for both. (Note the setting is to look for terms in the Post title and Content, it hasn’t changed.)

    Also seeing similar behavior when doing an “update existing content”, the only terms added were terms from the title of existing content.

    • This topic was modified 2 years ago by mikemac29.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Steve Burge

    (@stevejburge)

    Hi @mikemac29

    Thanks for using TaxoPress.

    We’ve had one similar report this weekend from a user who blames it on Jetpack: https://www.ads-software.com/support/topic/the-suggested-terms-are-no-longer-compatible-with-the-new-version-of-jetpack/

    Could that be possible with your site?

    Thread Starter mikemac29

    (@mikemac29)

    Thanks for pointing out the other thread Steve. It’s definitely related to the recent update of Jetpack – it works fine if I disable that plugin completely. Not sure that I can go down that route easily, but I’m trying to turn off some of the features -no luck so far. It is currently using PHP version 7.4.33 but I may try changing that soon too and see if it makes a difference.

    Plugin Author Steve Burge

    (@stevejburge)

    Thanks @mikemac29. I don’t see that yet, but Jetpack isn’t the easiest plugin to test against.

    Do you see anything in your site’s error logs?

    Do you see any errors in the browser’s “Console” tab when you try to load a post with “Suggest Terms”?

    Thread Starter mikemac29

    (@mikemac29)

    Steve, I started to poke around with Jetpack without finding any solution but when going into the console to look for errors I sort of accidentally discovered that the suggested terms work when using the Block Editor, but they do not work when using the Classic Editor (I use that plugin because I like writing in that interface better, it’s familiar.) So while there may be some conflict with Jetpack perhaps the “real” conflict is with Classic Editor.

    • This reply was modified 2 years ago by mikemac29.
    Plugin Author Steve Burge

    (@stevejburge)

    @mikemac29 The other reporter of this issue says that it’s fixed in the latest Jetpack. Can you check to see if that helps?

    Thread Starter mikemac29

    (@mikemac29)

    Thanks for that, just updated my Jetpack and see the same thing. Whatever was blocking Suggested Terms on the Classic Editor is fixed now.

    • This reply was modified 2 years ago by mikemac29.
    Plugin Author Steve Burge

    (@stevejburge)

    Thanks @mikemac29, that’s good to hear

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘No Longer Analyzing Post Content’ is closed to new replies.