Tag Essentials - with AI auto tagging and XFRM support

Tag Essentials - with AI auto tagging and XFRM support [Paid] 2.10.1

No permission to buy (£35.00)
Has anyone else had a problem with tags not appearing in the sitemap? I have the sitemap generated with tags enabled in my Xenforo settings. The tags are also visible to unregistered users.
 
My databse has these tables:
xf_tagess_blacklist
xf_tagess_category
xf_tagess_synonym
xf_tagess_tag_watch

I'd expect a vendor prefix after xf_ so these seem wrong?
 
My databse has these tables:
xf_tagess_blacklist
xf_tagess_category
xf_tagess_synonym
xf_tagess_tag_watch

I'd expect a vendor prefix after xf_ so these seem wrong?
Sounds like having a vendor prefix is a more modern standard which predates the addon. Checking.
Does it really matter?
 
An option to set og:image per tag would be ideal. As would a dedicated meta-description field - we aren't seeing CTR for tags, and I figure both would improve that.
 
Folks please update the model that Tag Essentials uses rather than let it use a deprecated one and get errors.
Remember to press the Refresh models button and always test your prompt using the tool we have provided at
/admin.php?tags-test-openai/
before making the change.
We’re using gpt-5.6-luna right now.
 
Last edited:
Folks please update the model that Tag Essentials uses rather than let it use a deprecated one and get errors.
Remember to press the Refresh models button and always test your prompt using the tool we have provided at
/admin.php?tags-test-openai/
before making the change.
We’re using gpt-5.6-luna right now.
gives me an error trying to do that :unsure:

 
Coder says
Doesn't appear to be a issue with the implementation, but if there's ever a networking issue, or a authentication issue, or the OpenAI API is down, they'll end up getting an error like this.
Can you try again please?
It’s not us ☹️
 
When creating an Open AI API Key, is there specific permissions required? I usually avoid doing "All" if possible.
 
When creating an Open AI API Key, is there specific permissions required? I usually avoid doing "All" if possible.
The OpenAI setup is at
/admin.php?options/groups/serviceProviders/
and permission to visit that page is in the administrator permissions. Super admins have permission to do everything. So if you're setting permission for a regular administrator, you need to tick Manage options because it's under the options section.
 
The OpenAI setup is at
/admin.php?options/groups/serviceProviders/
and permission to visit that page is in the administrator permissions. Super admins have permission to do everything. So if you're setting permission for a regular administrator, you need to tick Manage options because it's under the options section.

Sorry, I'm referring to the Open AI API Setup (on Open AI's site, not XF admin panel). You can choose a variety of setups, all / read only / specific permissions as an example.
 
Sorry, I'm referring to the Open AI API Setup (on Open AI's site, not XF admin panel). You can choose a variety of setups, all / read only / specific permissions as an example.
I don't know what page you're referring to. It's always handy to share a URL or screenshot to save time.
I don't recall having to make that choice. I just logged in to the API platform and created an API key.
 
I don't know what page you're referring to. It's always handy to share a URL or screenshot to save time.
I don't recall having to make that choice. I just logged in to the API platform and created an API key.
When creating an Open AI API Key, is there specific permissions required? I usually avoid doing "All" if possible.

As mentioned, creating the actual API Key.

I had Claude just examine the add-on and guide me. It mentioned this would be the appropriate setup (again, I was avoiding all if possible).

1786810372218.webp

I'm assuming this is the minimum requirement for the API key.
 
Is the tag cloud linking to forum tag filter rather than tag pages intended?

So the cloud is linking to;

/forum/forums/forum-name.1/?tags=name

rather than;

/forum/tags/name

I'm pretty sure it is intended, but I wanted to check whether there's a reason for it I'm not seeing?

The reason I'm asking is a crawl one. The widget renders on every page of every node, and the link inherits the current page number, so I'm also getting:

/forum/forums/forum-name.1/page-2?tags=name

Google have started showing them in Search Console under "Alternate page with proper canonical tag" (rather than as duplicates) but I'm thinking, just that node has 2,050 pages and the cloud carries 27 tags, so I figure uit's exposing something like 55,000 crawlable combinations from one node alone? I figure/think (could be wrong?) across the rest of the forum it's a lot of crawl budget spent on URLs that will never be indexed?

Would it be better, or would there be any issue to changing the cloud linking to the tag page, rather than the filter?

Thanks
 
Last edited:
As mentioned, creating the actual API Key.

I had Claude just examine the add-on and guide me. It mentioned this would be the appropriate setup (again, I was avoiding all if possible).

View attachment 342962

I'm assuming this is the minimum requirement for the API key.
I chose all. I haven’t looked at what the other options are or the consequences of choosing them.
 
Back
Top Bottom