If CF has to look for your custom tag (i.e., it's outside the current dir), CF will 'remember' where it found the tag. If you then move the custom tag, to either another custom tag folder or even to the current directory, CF will not be able to find the tag anymore. The only way to get CF to find the tag again is to restart the service. This is an old bug too (well, maybe not a bug since CF caches the location for performance reasons) that affects MX as well.
(This post is more than 2 years old.)
Custom Tag Caching
Hire Me!
I'm currently looking for my next role in developer evangelism and advocacy. I have a long history of helping companies work with developers and love to write, create demos, and present at confereneces. You can find my resume to learn more and drop me an email (raymondcamden@gmail.com) to reach out.
Support this Content!
If you like this content, please consider supporting me. You can become a Patron, visit my Amazon wishlist, or buy me a coffee! Any support helps!
Want to get a copy of every new post? Use the form below to sign up for my newsletter.