Devtard

So if I understand you correctly, it seems that APT uses term names when searching posts, even though it should only search for related keywords, correct?

Yes, I have received your email; now I also have a better idea what the problem is.

There’s an important difference between ACA and the latest APT version – when using the “category” taxonomy, term names should no longer contain category IDs. Categories are now automatically created if the term name doesn’t exist in the particular taxonomy.

So basically you need to replace these IDs in your keyword sets with category names – then categorizing posts should work as expected.

Since you have quite a lot of keyword sets, doing this manually would take forever, so I suggest the following:

1) Find a way to export your category names and their IDs.
2) Export your keyword sets.
3) Import both to some spreadsheet editor, sort these items so that category IDs correspond with term names, replace the term name column in your keyword sets with the other column containing category IDs.
3) Save the file as CSV and import it back to APT.

Ah. Could you please provide me with some sample keyword sets and post content, so that I can try to replicate the issue? (You can also send it to my Gmail address – I use the same handle there.)

Hi, have you tried using the newest version of APT for adding categories to posts? ACA is obsolete and will no longer be developed or supported in the future.

APT doesn’t work with slugs at all, so unfortunately this plugin can’t help you with that. You’d have to include the prefix in the term name in order to have the slug prefixed.

The message in the At a glance widget is shown when there aren’t any keyword sets or processable posts (posts with statuses specified by you, for example).

Try changing the Allowed post statuses option to the following:

publish,draft

There should be only names of post statuses separated by the string separator (usually a comma).

By default wildcards match everything; you can change this behavior by modifying the “Wildcard pattern” option. What you want might be possible with some clever regex that doesn’t match certain characters.

But since the current version supports using only one regex for all keyword sets, unfortunately I’m not sure if this will be very useful to you. Full regex support for related keywords should be implemented in future releases.

Hi, the easiest solution is probably using a different wildcard character and removing the asterisk from your word separators.

(Although you can use HTML entities in related keywords, currently there’s no way to escape characters; the latest version unfortunately isn’t able to distinguish wildcard characters from their HTML entities. This should be fixed in v1.9.)

Hi, that’s correct. APT uses its own keyword database, so if you delete taxonomy terms from WP, keyword sets in APT won’t be affected. You’ll have to remove these keyword sets as well if you don’t want their terms to be automatically added to posts. Or you can disable their configuration groups.

That can be done, of course. See FAQ #7 for more information: https://www.ads-software.com/plugins/automatic-post-tagger/faq/

Cool, glad to hear that. ??

Click on the button “Save changes” to update the number; then the plugin should work just fine.

The number should have been updated during the plugin update. I’ll look into it, thanks for letting me know about this.

The number of keyword sets belonging to the particular group isn’t displayed if the CSV editor mode is enabled; switch the “Item editor mode” to “Classic” and scroll down to the group editor. The “KW sets” number for the group should be higher than 0. Is it?

Check out the Configuration group editor. Is the default group enabled? Is the KW sets number higher than 0?

Try using the bulk tagging tool (click on the button “Schedule bulk tagging” or “Process posts now”); an error message telling you what’s wrong should be displayed.