Out of nowhere the node browser stopped showing the components of my page. I have restarted, updated app… tried everything but still nothing showing beyond main element. Any ideas?
Glad to hear I’m not the only one experiencing this issue. Please don’t get me wrong—I’m actually dealing with exactly the same problem and already sent screenshots to Dan yesterday.
What’s interesting about this issue is that it keeps coming back, even if you completely recreate the tab component from scratch.
I assume the rw-Crew is already looking into it. However, they’re probably quite busy at the moment with preparations for the store relaunch and CMS 2.
Have you by any chance noticed more frequent crashes in Elements when using the tab component?
I’ve observed this myself, and it might help narrow down the issue.
@pegasus i haven’t had a problem with crashes - did at first (few months ago) but not in last couple months. Just the disappearing nodes.
Thanks for the feedback on this, we have a ticket open here to make sure this gets fixed.
Can you share a small sample project that shows the issue? or is it too intermittent?
‘s not letting me upload - gives message of too many files; also no zip allowed
thanks! done!
Perfect, got the project, thanks 
I am seeing the same issue with the tabs component in the node browser.
elementsapp://downloadDocument/GSgGYqBVnI8A
US Air Force Beret Badges page
Yup, we’ve reproduced it here and will get it fixed — Sorry for the delay!
@floodstone @floodstone @Pegasus, this should be fixed in the latest build — version 2.2.5.
Let me know how you get on 
elements!It’s good to read that the fix seems to be working for some users. So I don’t like to say it, @dan, but in my project it still isn’t working after the update.
At the latest, after restarting the project, the problem always comes back.
Hello Pegasus,
That was similar for me, because nothing changed after installing the update. I had to completely close and quit Rapidweaver Elements.
Then, after a short time, I restarted Rapidweaver Elements. When I then opened the project, all the tab subnodes were visible again.
I should have described that better, please excuse me. I hope it’s working for you now too.
Thanks for the feedback. @RELAX-IT
That is of course standard procedure for me whenever a new update is installed: Elements is completely closed and then restarted.
And that seems to be where the problem lies, at least for me.
When I completely close Elements and then open a project, the tab sub-items are not visible. However, if I then open another project, the sub-items in the newly opened project are visible.
So that means: if I open a project directly after launching Elements, the tabs are not visible. If I close the project and then open it again, the tabs are there.
Interestingly, this also happens in the previous Elements version. So it’s still not running entirely smoothly.
@dan I’ve attached a video showing the issue — I hope it helps. Otherwise, let me know if you need a new copy of the project. But I saw that you still have an older version, and it should be reproducible with that one as well.
Thanks @Pegasus,
I’ve been able to reproduce this here, I’m diving in now to figure out what’s going on.
Thanks!
I have the same problem, and this is how I solved it: I converted the tab to a “Global” tab, moved the Global tab to the page, and deleted the original tab. That way, you can edit the tab until the next time you launch Elements.
For me, the problem only occurs with tabs that have a lot of elements. Tabs with 3 or 4 elements don’t cause any problems.
Expect a new build on Monday with a proper fix for the tabs!