Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working on Craft 3.7.17 #21

Open
zehfred opened this issue Oct 20, 2021 · 4 comments
Open

Not working on Craft 3.7.17 #21

zehfred opened this issue Oct 20, 2021 · 4 comments

Comments

@zehfred
Copy link

zehfred commented Oct 20, 2021

When adding tags via the tag manager they don't show up on the list of tags. Neither do those tags created inside the entries. I can only see tags that were added before installing the plugin.

They are indeed created and show up as available inside the entries and they are listed when performing actions like "Replace with" but don't show up in the tags lists. And the deleted tags never disappear, which throws an error when trying to access them.

@mudechs
Copy link

mudechs commented Dec 10, 2021

Same issues here on Craft CMS 3.7.25.1 and Tags 1.0.9. New created Tags only show up after clearing the system-cache.

@membla
Copy link

membla commented Jan 30, 2022

Same on 3.7.29 – would have thought downgrading to version before this fix (1.0.7) would solve it but did not, for anyone considering it.

vnali added a commit to vnali/tags that referenced this issue Feb 12, 2022
for custom element types, Craft manages and invalidates element index cache on adding or editing an element. but for tag element, when you add or edit a tag via element index page or even tag field on entry page, Craft is not aware of this plugin's tag element type so this PR invalidate element type cache for this plugin on after save tag event
@rob-c-baker
Copy link

The above pull request looks like it might work with Craft 4. I might just give that a go!

@BAM-Dennis
Copy link

Any news on this? At the moment, with the current version, we do not see any changes until we clear the cache manually.

Maybe you can go a similar solution as element-api does

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants