Hi there i work with the Node Editor since a few weeks. Sometimes i see a bug that when i add a new trigger like “on page load” i am not able to move that element and after that my changes have no effect on my front end. I got really frustraded and thought i set a setting wrong or anything else. After long dialogs with chatgpt and research i gave up and tried to go on with node editing. But then I thought it could be a caching problem.
After reloading the page without cache (STRG + F5 on windows) all my changes were gone since the time i had the glitch with the “i added a trigger and i was no table to move the element on the node board”.
Ah and yeah i still saved the node with the save button on the upper right corner and also saved and reloaded my bricks page a lot of times. But as i said after reloading without the cache it changed back to the state before i had the issue with the not moveable element.
I had this issue twice so now i want to report that bug because its super frustrating that i currups my work and i dont have a solution. I tried to restart the browser but this is sitll not working.
Can you help us reproduce the problem? I have never observed such behavior before.
Additionally, it would of course be interesting to know which plugins and server environment you are using, since it indeed sounds like a caching issue.
I have a similar issue on a fresh install with Bricksforge 3.1.3, each time the builder is reloaded the node editor is empty, the nodes are still performing actions on the frontend but can’t see them to editor.
Could it be the same problem with the topic creator? So far, we haven’t been able to reproduce it.
Otherwise, maybe you could just try deactivating Wordfence Security as a test and see if the problem occurs again. It’s possible that some REST API endpoints might occasionally be blocked, but actually, I don’t really expect that to be the case.
