No, they’re having the same issue and Jon asked me to make a post here about it but also that he is not working till next wednesday otherwise he would be here replying.
What I’m saying is, Jon has recognized this may be an issue with how n8n is handling community nodes, this is not about support for specific community nodes, I’m just giving the full context so someone can try to reproduce my issue.
I posted the similar issue with that. Still can’t figure out what the problem is.
I got the suggestion to clear the cache of my browser, but haven’t tested it yet, hopefully i will get the chance on the weekend to work on my private system again.
Maybe this helps you.
Thanks for your comment, I was having the same issue with all my community nodes and relogging using an incognito window solved it so probably related to browser cache.