WTF!!!
All day yesterday was a ‘broken’ day because of that.
That was it…
I closed wappler and also quit from the tray icon. When I opened again both serverconnects run as they should…
Maybe it is not a good practice to duplicate pages or apis in NodeJS?
As a matter of fact, I have watched every video from @ben and @Hyperbytes and that was a question that I had… “Why they don’t just duplicate that api or page and do a few changes?”
Instead of close and quit wappler, maybe just restarting local server is better?
I quess NodeJS is kind of sensitive…
And since my thread excuses more questions, can I ask if there is a way to duplicate a page (layout or content?
I quess it it the definition and relation of layout and content that makes that difficult?
Anyway, I can live with that… Create a new page and just copy/paste the code…
Thanks brother
Thanks Ben, but this way we loose the rooting functionality that is automatically handled from wappler…
Right?
*By the way, talking about files->Duplicate page… Where is the config.js file located? (in PHP-> dmxAppConnect/config.js)
I’m asking because when I wanted to dublicate a page in PHP (with a different/new APP ID), I was first creating a new node in config.js with the new App ID that I was going to use in the new page and then change the App ID of the duplicated page…
Otherwise the old content of the config.js node was overwritten by the new (and that meant it was an empty node until I add a new compnent, tablerepeat, datastore etc)
I have seen this issue several times in the past, I thought it was random but maybe you have localised the issue,if so, that’s great.
To be honest, any strange behaviour In Wappler my number one action is to restart wappler. Fixes most usual glitches.