Tag Essentials - with AI auto tagging and XFRM support

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

No permission to buy (£35.00)
Overview Updates (48) Reviews (5) History Discussion
I was finally able to track down an issue where the "Clear All" filter button added by AddonsLab's filter add-ons was always displayed on the filter bar, regardless of whether there was actually an active filter, as well as some odd behavior with other add-ons which touch the filter bar.

1733435298363.webp

I tracked it down to the avForumsTagEss_forum_view template modification which adds <input type="hidden" name="nodeId" value=""> to the filterBar-filters list, even when there are no active filters.

Modifying <xf:if is="$xf.options.enableTagging"> in the template modification to <xf:if is="$xf.options.enableTagging && $filters is not empty"> seems to have resolved the issue, but I have no idea if this is an adequate solution. If so, it'd be nice to have this simple fix incorporated :)
 
Joe Link said:
I was finally able to track down an issue where the "Clear All" filter button added by AddonsLab's filter add-ons was always displayed on the filter bar, regardless of whether there was actually an active filter, as well as some odd behavior with other add-ons which touch the filter bar.

View attachment 315096

I tracked it down to the avForumsTagEss_forum_view template modification which adds <input type="hidden" name="nodeId" value=""> to the filterBar-filters list, even when there are no active filters.

Modifying <xf:if is="$xf.options.enableTagging"> in the template modification to <xf:if is="$xf.options.enableTagging && $filters is not empty"> seems to have resolved the issue, but I have no idea if this is an adequate solution. If so, it'd be nice to have this simple fix incorporated :)
Click to expand...

Stuart Wright said:
Stuart Wright updated Tag Essentials - with AI auto tagging and XFRM support with a new update entry:

Bug fix
Click to expand...

I appreciate the update. unfortunately this is still occurring.

I believe there was a misunderstanding, as we actually do have content tagging enabled. The issue is that this hidden input element is added even when there are no active filters, making other addons behave as if there are active filters (they're checking to see whether the <ul class="filterBar-filters"> list is populated).

1733856273222.webp
 
Joe Link said:
I appreciate the update. unfortunately this is still occurring.

I believe there was a misunderstanding, as we actually do have content tagging enabled. The issue is that this hidden input element is added even when there are no active filters, making other addons behave as if there are active filters (they're checking to see whether the <ul class="filterBar-filters"> list is populated).

View attachment 315396
Click to expand...
The last update wasn't in reference to your issue. Your issue is caused by a different addon though it looks like the TagEss code needs tweaking. I have asked the coder to have a look.
 
Last edited:
Stuart Wright said:
The last update wasn't in reference to your issue. Your issue is caused by a different addon though it looks like the TagEss code needs tweaking. I have asked the coder to have a look.
Click to expand...
The coder has had a look. The fix is not trivial so it’s been scheduled in and will take a while to get to.
 
Stuart Wright said:
The coder has had a look. The fix is not trivial so it’s been scheduled in and will take a while to get to.
Click to expand...

Ah, thanks for the update. Is there something wrong with this simple fix? Seems to be working fine (but I'm not a dev). I'd hate to have the dev rewrite a bunch of code when a simple template modification update would do.

Joe Link said:
Modifying <xf:if is="$xf.options.enableTagging"> in the template modification to <xf:if is="$xf.options.enableTagging && $filters is not empty"> seems to have resolved the issue, but I have no idea if this is an adequate solution. If so, it'd be nice to have this simple fix incorporated :)
Click to expand...
 
I get the following error since I tried to update my resource via bash

Code: 
TypeError: XF\Job\JobResult::newResume(): Argument #3 ($statusMessage) must be of type string, null given, called in /var/www/vhosts/site/httpdocs/src/XF/Job/AbstractJob.php on line 113 src/XF/Job/JobResult.php:34
Generiert von: Phantom 14. Januar 2025 um 20:44
Stack-Trace
#0 src/XF/Job/AbstractJob.php(113): XF\Job\JobResult::newResume(1769367, Array, NULL, NULL)
#1 src/addons/AVForums/TagEssentials/Job/ResourceTagBatchUpdateAction.php(89): XF\Job\AbstractJob->resume()
#2 src/XF/Job/Manager.php(275): AVForums\TagEssentials\Job\ResourceTagBatchUpdateAction->run(8)
#3 src/XF/Job/Manager.php(205): XF\Job\Manager->runJobInternal(Array, 8)
#4 src/XF/Job/Manager.php(89): XF\Job\Manager->runJobEntry(Array, 8)
#5 src/XF/Admin/Controller/ToolsController.php(165): XF\Job\Manager->runQueue(true, 8)
#6 src/XF/Mvc/Dispatcher.php(362): XF\Admin\Controller\ToolsController->actionRunJob(Object(XF\Mvc\ParameterBag))
#7 src/XF/Mvc/Dispatcher.php(264): XF\Mvc\Dispatcher->dispatchClass('XF:Tools', 'RunJob', Object(XF\Mvc\RouteMatch), Object(NF\Discord\XF\Admin\Controller\Tools), NULL)
#8 src/XF/Mvc/Dispatcher.php(121): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(NF\Discord\XF\Admin\Controller\Tools), NULL)
#9 src/XF/Mvc/Dispatcher.php(63): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#10 src/XF/App.php(2826): XF\Mvc\Dispatcher->run()
#11 src/XF.php(806): XF\App->run()
#12 admin.php(15): XF::runApp('XF\\Admin\\App')
#13 {main}
 
Michaelb24179 said:
I get the following error since I tried to update my resource via bash

Code: 
TypeError: XF\Job\JobResult::newResume(): Argument #3 ($statusMessage) must be of type string, null given, called in /var/www/vhosts/site/httpdocs/src/XF/Job/AbstractJob.php on line 113 src/XF/Job/JobResult.php:34
Generiert von: Phantom 14. Januar 2025 um 20:44
Stack-Trace
#0 src/XF/Job/AbstractJob.php(113): XF\Job\JobResult::newResume(1769367, Array, NULL, NULL)
#1 src/addons/AVForums/TagEssentials/Job/ResourceTagBatchUpdateAction.php(89): XF\Job\AbstractJob->resume()
#2 src/XF/Job/Manager.php(275): AVForums\TagEssentials\Job\ResourceTagBatchUpdateAction->run(8)
#3 src/XF/Job/Manager.php(205): XF\Job\Manager->runJobInternal(Array, 8)
#4 src/XF/Job/Manager.php(89): XF\Job\Manager->runJobEntry(Array, 8)
#5 src/XF/Admin/Controller/ToolsController.php(165): XF\Job\Manager->runQueue(true, 8)
#6 src/XF/Mvc/Dispatcher.php(362): XF\Admin\Controller\ToolsController->actionRunJob(Object(XF\Mvc\ParameterBag))
#7 src/XF/Mvc/Dispatcher.php(264): XF\Mvc\Dispatcher->dispatchClass('XF:Tools', 'RunJob', Object(XF\Mvc\RouteMatch), Object(NF\Discord\XF\Admin\Controller\Tools), NULL)
#8 src/XF/Mvc/Dispatcher.php(121): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(NF\Discord\XF\Admin\Controller\Tools), NULL)
#9 src/XF/Mvc/Dispatcher.php(63): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#10 src/XF/App.php(2826): XF\Mvc\Dispatcher->run()
#11 src/XF.php(806): XF\App->run()
#12 admin.php(15): XF::runApp('XF\\Admin\\App')
#13 {main}
Click to expand...
What version of Xenforo and what version of Tag Essentials?
And when does the error occur?
Please add as much information as you can as it's unfeasible to diagnose a bug without knowing more.
 
Alpha1 said:
Some years ago this addon was not yet compatible with @Bob 's addons. Has there been any new development on this?
Click to expand...
No, and there won’t by from my side, I’m afraid. Development is very expensive and unless it benefits me on AVForums, I won’t fund it. If others want to pay for it, they will get a lifetime license, of course.
 
You must log in or register to reply here.
Back
Top Bottom