Tag Essentials - with AI auto tagging and XFRM support

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

No permission to buy (£35.00)
Thanks for the update. Now I'm getting this one. Any ideas? Thanks

  • GuzzleHttp\Exception\ClientException: OpenAI connection error: Client error: POST https://api.openai.com/v1/chat/completions resulted in a 429 Too Many Requests response: { "error": { "message": "You exceeded your current quota, please check your plan and billing details.", (truncated...)
  • src/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113
  • Generated by:
  • Jul 17, 2023 at 3:25 PM

Stack trace​

#0 src/vendor/guzzlehttp/guzzle/src/Middleware.php(65): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response))
#1 src/vendor/guzzlehttp/promises/src/Promise.php(204): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response))
#2 src/vendor/guzzlehttp/promises/src/Promise.php(153): GuzzleHttp\Promise\Promise::callHandler(1, Object(GuzzleHttp\Psr7\Response), NULL)
#3 src/vendor/guzzlehttp/promises/src/TaskQueue.php(48): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}()
#4 src/vendor/guzzlehttp/promises/src/Promise.php(248): GuzzleHttp\Promise\TaskQueue->run(true)
#5 src/vendor/guzzlehttp/promises/src/Promise.php(224): GuzzleHttp\Promise\Promise->invokeWaitFn()
#6 src/vendor/guzzlehttp/promises/src/Promise.php(269): GuzzleHttp\Promise\Promise->waitIfPending()
#7 src/vendor/guzzlehttp/promises/src/Promise.php(226): GuzzleHttp\Promise\Promise->invokeWaitList()
#8 src/vendor/guzzlehttp/promises/src/Promise.php(62): GuzzleHttp\Promise\Promise->waitIfPending()
#9 src/vendor/guzzlehttp/guzzle/src/Client.php(182): GuzzleHttp\Promise\Promise->wait()
#10 src/vendor/guzzlehttp/guzzle/src/Client.php(95): GuzzleHttp\Client->request('post', 'https://api.ope...', Array)
#11 src/addons/AVForums/OpenAIShared/OpenAI.php(40): GuzzleHttp\Client->__call('post', Array)
#12 src/addons/AVForums/TagEssentials/XF/Repository/Tag.php(446): AVForums\OpenAIShared\OpenAI->chat(Array)
#13 src/addons/AVForums/TagEssentials/XF/Entity/Tag.php(166): AVForums\TagEssentials\XF\Repository\Tag->getAiDescriptionByTitle('running up thst...')
#14 src/XF/Mvc/Entity/Entity.php(1366): AVForums\TagEssentials\XF\Entity\Tag->_preSave()
#15 src/XF/Mvc/Entity/Entity.php(1219): XF\Mvc\Entity\Entity->preSave()
#16 src/XF/Mvc/Entity/Entity.php(1323): XF\Mvc\Entity\Entity->save(true, true)
#17 src/addons/AVForums/TagEssentials/Job/WikiFixup.php(36): XF\Mvc\Entity\Entity->saveIfChanged()
#18 src/XF/Job/AbstractRebuildJob.php(42): AVForums\TagEssentials\Job\WikiFixup->rebuildById(99)
#19 src/XF/Job/Manager.php(260): XF\Job\AbstractRebuildJob->run(8)
#20 src/XF/Job/Manager.php(202): XF\Job\Manager->runJobInternal(Array, 8)
#21 src/XF/Job/Manager.php(118): XF\Job\Manager->runJobEntry(Array, 8)
#22 src/XF/Admin/Controller/Tools.php(122): XF\Job\Manager->runByIds(Array, 8)
#23 src/XF/Mvc/Dispatcher.php(352): XF\Admin\Controller\Tools->actionRunJob(Object(XF\Mvc\ParameterBag))
#24 src/XF/Mvc/Dispatcher.php(259): XF\Mvc\Dispatcher->dispatchClass('XF:Tools', 'RunJob', Object(XF\Mvc\RouteMatch), Object(XF\Admin\Controller\Tools), NULL)
#25 src/XF/Mvc/Dispatcher.php(115): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(XF\Admin\Controller\Tools), NULL)
#26 src/XF/Mvc/Dispatcher.php(57): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#27 src/XF/App.php(2487): XF\Mvc\Dispatcher->run()
#28 src/XF.php(524): XF\App->run()
#29 admin.php(13): XF::runApp('XF\\Admin\\App')
#30 {main}

Request state​

array(4) {
["url"] => string(24) "/admin.php?tools/run-job"
["referrer"] => string(127) "https://www.welovetheeighties.com/admin.php?tools/run-job&only_id=4723&_xfRedirect=/admin.php?tools/rebuild&success=1"
["_GET"] => array(1) {
["tools/run-job"] => string(0) ""
}
["_POST"] => array(3) {
["_xfRedirect"] => string(67) "https://www.welovetheeighties.com/admin.php?tools/rebuild&success=1"
["_xfToken"] => string(8) "********"
["only_ids"] => string(4) "4723"
}
}
The error message indicates you ran out of quota for chatgpt api calls:
You exceeded your current quota, please check your plan and billing details
 
Hi Stewart - question: is it possible to adjust any of the Tag Essentials code so that tag filters (e.g., clicked on from the tag cloud widget) refine existing results from any prefix filters used (i.e., work as an AND operator with prefix filters)?

Case in point, this page you previously linked (https://www.avforums.com/forums/lg-tvs-forum.91) uses both prefix filters (on top) and tag filters (in the tag cloud sidebar widget). On that page, I can filter for threads with "Question" prefixes or I can filter for threads that use the "television" tag, but I can't readily filter for threads involving questions about televisions. That is, if I filter for "question" prefix threads, then try to filter for "television" tag threads, the filter will reset and I'll only see results of the tag filter.

On my forum, it would really be great if these filters stacked on top of each other using an AND operator, giving users the ability to narrow threads using both prefixes and threads. Is there some easy way to manipulate the code for the Tag Essentials add-on (the add-on I'm using right now; I'm not currently using Prefix Essentials) to make this work? Would you consider adding this functionality to Tag Essentials (and/or Prefix Essentials) in a future update?

Thanks!
 
How would you propose that the UI for both the prefix filter and the tag cloud be changed so that users can choose to replace the existing filter (as we have now) or add to it?
 
How would you propose that the UI for both the prefix filter and the tag cloud be changed so that users can choose to replace the existing filter (as we have now) or add to it?

I'd say that, at minimum, it'd be great if this option was provided to the admin in the ACP (maybe as part of the tag cloud widget settings). Maybe have a checkbox labelled something like "tag filter queries against existing filters" in the widget that the admin can check or leave unchecked to control tag filtering behavior. I'd wager admins generally know what makes the most sense on their forum in terms of prefixes and tags being mutually exclusive or if they should be used together when filtering. It might also be nice for the user to control these settings in the UI but like I said, at minimum I'd make it an admin option and I think that would address most use cases. I appreciate you considering my thoughts on this!
 
It would be a bad idea to change the way it works site wide because people are used to how it currently works and some people will prefer it that way. So you have to give people an option. So how would you give people an option each time they use a search filter in the prefix filter and the tag cloud?
 
It would be a bad idea to change the way it works site wide because people are used to how it currently works and some people will prefer it that way. So you have to give people an option. So how would you give people an option each time they use a search filter in the prefix filter and the tag cloud?

For me, I don't really have any traffic yet, so I'd be happy to just make that the way filtering works site-wide or on a widget-by-widget basis. But my needs may not be representative of everyone so I'll definitely defer to your experience on this :). Good point about giving people the option in the UI...I'd personally be hesitate to add an extra bell+whistle because I tend to be conservative in terms of design and want to keep things as simple as possible...so not sure. I personally wouldn't want people to have the option at all, since I think querying prefixes and tags together makes more intuitive sense for the type of filtering people would be doing on my site. So for that reason I'd prefer just having an enable/disable option in the ACP (site-wide or for each widget) and avoiding extra clutter in the UI. But that's just me 🤷‍♂️.

Anyways, please just consider this a "suggestion box" item. Again, I really just appreciate you taking the time to consider it!
 
Stuart Wright updated Tag Essentials - with AI auto tagging and XFRM support with a new update entry:

Improvement to blacklisting tags

First of all we've fixed a bug where newly blacklisted tags are not removed from the system.
This would sometimes cause an error if a blacklisted tag existed and was automatically suggested in a new thread.
From 2.5.1.2 on, when a new blacklisted tag is added, existing matching tags are deleted.

Because there could be existing blacklisted tags, we've added a new batch process to remove orphaned tags.
It should only really need to be run after upgrading to 2.5.1.2.
It can't deal with regex...

Read the rest of this update entry...
 
Can it scan the contents of the first post to suggest/add potential tags? AI should scan it and compare what words in the first post is relevant to the thread title.
 
Can it scan the contents of the first post to suggest/add potential tags? AI should scan it and compare what words in the first post is relevant to the thread title.
If you read the description you will see that it does.
It actually suggests tags based on the forum name, thread title and first post text. This way we’re getting more useful results even if the title and first post are garbage.
 
I did check it out for a while but I missed that part, going through the release notes also. Anyhow good to know, I might be buying a license for it in a couple of days.
 
I saw a few posts from 2022 - Did any development for AMS/Showcase (Bobs addons) get any closer to completion?

I saw that the expense of getting Bobs addons was a problem too - I'm sure Bob would help out in some way. He usually does with developers, I believe :)
 
Top Bottom