OK, I understand now. You have installed the very first fleXon as component. Can you go to preferences and addons like below.
You will find there a fleXon 1.0.1. Deselect it and remove it like below
Then scroll to fleXon v2. deselect it by clicking on the checkbox and then select it again. Close preferences an you now you should find only fleXon v2 in your templates
Thanks - keep up the good work
Dear all,
I just uploaded a new Build (2) of fleXon. The name should now be correctly listed as fleXon 2 and I added also 2 new template sections.
We are now at 204 sections in total.
Hope you like it!
Hi @dan and @tpbradley
can you please jump in. Thatâs what we discussed in another thread this morning. Does not seem to work.
@logrunner
thanks for reporting it.
Hi all,
Iâve identified the issue and Iâm working on a fix!
Cheers
Thanks for the latest update! - The additional sections show up now. âŠbut after installing the update and closing and re-opening Elements the update is shown again as pending. Sounds like a similar problem, as with the first release of v2.
Update: Just tested and this is not fixed with 2.2.10. Not sure if this is for @tpbradley or @WeaverPixel to look at.
Is this meant to be fixed in 2.2.10 (i.e. The Developer Pack display name is now loaded from info.json) because if it is, it isnât fixed - still not showing flexon 2.
Maybe that update is referring to something else?
Hi @logrunner,
Yes, that fix is included in 2.2.10. However, for it to take effect, a new build of fleXon needs to be submitted using that version of Elements. The current fleXon build was created before the fix was added, so it wonât show correctly until itâs rebuilt and re-submitted.
OK, but I have seen and done two updates of fleXon since I installed the Elements update (one just after the update and the last one just now). 
Hey @logrunner, as mentioned above, @WeaverPixel will need to submit a new build of fleXon 2, once that update goes live youâll finally see the â2â in the fleXon name.
Thanks @tpbradley and @dan for reacting so fast.
And thanks for @logrunner and @herbing for reporting the issues.
I just uploaded build 4 created with Elements 2.2.10. So it should work now. Build 4 should then state fleXon 2 under file names and has 2 new sections. It is in the approval process so we need to wait until it is through.
Awesome!
@WeaverPixel build 4 of fleXon 2 is now live, hopefully @logrunner and @herbing can confirm itâs fixed 
When I start Elements, I am seeing there is an update for fleXon 2, which I thought I had already installed.
I do the update and it says installed.
When I next start Elements, the same update is back again?
I have logged out of the Store and restarted Elements logged back in again and it is still asking me to update the same version of the template. So I update it and quit Elements but when I next start Elements the same update is back again.
Try uninstalling the component, restarting, then installing again.
Hopefully that should fix it for you
No it doesnât, unfortunately. 
I uninstall fleXon 2 and Elements says it is uninstalled. If I look at my purchases, I can see fleXon 2 with a button saying Install.
So having confirmed that it is uninstalled, I then quit Elements and restart it.
On Elements restart, fleXon 2 is showing as installed and pending an update? I havenât re-installed it, it did it automagically?
Hey @logrunner
that sound a bit like a problem another user had. I had a conservation with him about his solution. The conversation was in German but I translated his solution here below. Thanks Kai-Uwe @herbing for the detailed description.
Iâve managed to figure it out now. In the âhiddenâ folder where the Elements packs from the Store are stored in encrypted form, there was not only the current com.weaverpixel.flexon-v2-b4.elementspack but also a com.weaverpixel.flexon-v1-b1.elementspack. It had been there since April 30, 2026, at 11:00:00 AMâexactly the first version I had purchased from the Store on April 30, 2026, at 11:00 AM.
I first deleted the current package via the Elements GUI, closed Elements, then deleted the v1-b1 in the terminal using rm, and then reinstalled the current v2-b4 from the store in Elements. Now everything is fine.
Before the manual cleanup, the header fleXon (without the 2) was always displayed in the template view for me as well, and Iâve now resolved that at the same timeâfleXon 2 is now displayed correctly there.
So, to summarize: somehow the ID of the Elements pack changed from v1 to v2 along the way, and when updating to v2-b4, Elements doesnât delete v1-b1. After a restart, it always sees v1-b1 because it appears first in the sort order.
Hope it helps!
Thanks to you and @herbing - problem solved! 
I eventually found com.weaverpixel.flexon-v1-b1.elementspack and deleted it. Restarted Elements and now all is OK.
It was obviously the old version that was causing Elements to go adrift.
Hopefully this info will be useful to @dan / @tpbradley to resolve this bug for the future. 
Where can I find these âhidden filesâ? I have the same problem.
