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

[kailew]

With the new update for me the blacklisting issue is gone, thx @Stuart Wright

 

[rdn]

We still suffer this kind of error when adding new tags to existing threads.

Some tags are not permitted in this forum. Please change the following tags: xxxxxx

This only started happening with the recent addon update.

 

[Stuart Wright]

We still suffer this kind of error when adding new tags to existing threads.

This only started happening with the recent addon update.

Investigating

 

[Xon]

We still suffer this kind of error when adding new tags to existing threads.

This only started happening with the recent addon update.

Can you check if the tag can if it has been limited to a given forum? And provide a screenshot of the config from the tag for that?

 

[rdn]

Edit...

We still suffer this kind of error when re-using existing tags in existing threads.

Some tags are not permitted in this forum. Please change the following tags: xxxxxx

This only started happening with the recent addon update.

 

[rdn]

Can you check if the tag can if it has been limited to a given forum?

I don't have any tags that use this option.
Restrict addition of tag to threads in these forums:

And provide a screenshot of the config from the tag for that?

Just the default settings for each tag, none of them has been customized.

 

[rdn]

sample tag that I cannot re-use; all of my tags have these settings, the default.

 

[Stuart Wright]

We still suffer this kind of error when adding new tags to existing threads.

This only started happening with the recent addon update.

What is happening exactly?
Are you trying to add a new tag which previously didn't exist?
Or are you trying to add an existing tag to an existing thread?
If you are having trouble with a specific tag, what does this setting look like for that tag?


[Edit : we cross posted. Ok, investigating].

 

[rdn]

Are you trying to add a new tag which previously didn't exist?

No.

Or are you trying to add an existing tag to an existing thread?

Yes.

If you are having trouble with a specific tag, what does this setting look like for that tag?

screenshot above, but I don't have "None" selected for all the existing tags.
Should I select (None) for all the existing tags for this to work as expected?

It's doable via SQL query as I have 43k tags :|.

 

[rdn]

Ok, investigating

Is it reproducible on your side?

 

[Stuart Wright]

Is it reproducible on your side?

No, I don't have any problems, but @Xon is investigating.

 

[Joe Link]

This error only shows up if you have debug mode enabled, which is strongly not recommended for a production site.

This feature is related to the 'tag watching', and when the debug flag isn't enabled will just silently fail for non-supported types.

Please start a ticket on my site for full support for AMS/Showcase.

Aside from the member not receiving notifications when watching the tag, do the tags work as normal for non-supported types?

 

[Xon]

Aside from the member not receiving notifications when watching the tag, do the tags work as normal for non-supported types?

Yup.

We still suffer this kind of error when adding new tags to existing threads.

This only started happening with the recent addon update.

This isn't reproducing as expected, I'm started a conversation with you to get some more details

 

[Joe Link]

Great, thanks

 

[Stuart Wright]

Stuart Wright updated Tag Essentials with a new update entry:

Bug fix

- Fix incorrect "Some tags are not permitted in this forum" error when adding an existing tag.
With thanks to those who reported the issue

Read the rest of this update entry...

 

[kailew]

I've installed the Bug fix, but the half of my several 100 tags now have the "Restrict Addition" setting. It costs a lot of time to revert this manually ... please, I need a solution.

 

[Xon]

This will bulk reset the forum restrict list:

update xf_tag
set allowed_node_ids = null;

 

[Joe Link]

@Stuart Wright

Any chance of updating this so the watch button on tag_view reads unwatch tag when the tag is watched (like default XF watch buttons)? It's a bit confusing for members.

<xf:if is="$tag.canWatch()">
    <xf:button href="{{ link('tags/watch', $tag) }}" class="button--cta" overlay="true" icon="preview">
        {{ phrase('avForumsTagEss_watch_tag') }}
    </xf:button>
</xf:if>

Watch thread example

<xf:if is="$thread.canWatch()">
    <xf:button href="{{ link('threads/watch', $thread) }}" class="button--link"
        data-xf-click="switch-overlay"
        data-sk-watch="{{ phrase('watch') }}"
        data-sk-unwatch="{{ phrase('unwatch') }}">
        <xf:if is="{$thread.Watch.{$xf.visitor.user_id}}">
            {{ phrase('unwatch') }}
        <xf:else />
            {{ phrase('watch') }}
        </xf:if>
    </xf:button>
</xf:if>

 

[Stuart Wright]

@Stuart Wright

Any chance of updating this so the watch button on tag_view reads unwatch tag when the tag is watched (like default XF watch buttons)? It's a bit confusing for members.

<xf:if is="$tag.canWatch()">
    <xf:button href="{{ link('tags/watch', $tag) }}" class="button--cta" overlay="true" icon="preview">
        {{ phrase('avForumsTagEss_watch_tag') }}
    </xf:button>
</xf:if>

Watch thread example

<xf:if is="$thread.canWatch()">
    <xf:button href="{{ link('threads/watch', $thread) }}" class="button--link"
        data-xf-click="switch-overlay"
        data-sk-watch="{{ phrase('watch') }}"
        data-sk-unwatch="{{ phrase('unwatch') }}">
        <xf:if is="{$thread.Watch.{$xf.visitor.user_id}}">
            {{ phrase('unwatch') }}
        <xf:else />
            {{ phrase('watch') }}
        </xf:if>
    </xf:button>
</xf:if>

This will need doing properly with a new phrase and release by @Xon who develops this for me.

 

[Stuart Wright]

Stuart Wright updated Tag Essentials with a new update entry:

Bug fix

Fix 'watch tag' button which didn't dynamically update itself like the 'watch thread' button does

Read the rest of this update entry...

With thanks again to @Xon for fixing this so quickly, and @Joe Link for reporting.