Problem: On attempting to preview a content page in the browser, the page does not appear to have any CSS (looks raw and not designed). The page has a layout attached to it both in it’s settings and route - this was meant to be the issue when I reported this in the community recently. See this video:
The configuration: M1 MacBook Pro. Docker (Local) Node JS using Maria DB, all created automatically by Wappler, deployed to Development environment. System check fine. It appears to affect dynamic pages only, not static html files.
But I see your layout page is not saved when the video starts. Then you hit reload page (yes) and the page is being reloaded losing all the changes made to it. Why would you select to reload the page and lose any changes made to it?
When the layout page is reloaded I see body instead of app which means the app connect and Bootstrap frameworks are missing from this page … so the styling is lost on the content page.
It’s really not that hard to use layout and content pages and I already linked to a tutorial explaining how to use them in another topic you created. You just create a layout page, add the frameworks required save the page and then create any content page selecting this layout page.
The blue circle icon means the page is not saved, so you should make the layout page is also saved!
Ok it is now clearer, thanks. Looks like I am not the only one who is confused - pros like Ken Thursedale are also confused - so there is a genuine issue with the UX.
Now, as to that ‘would you like to reload page…’ message, suggest rethink the wording. Most users would say yes to that, given that it does not give any further info (thinking it is a good thing to reload ) and that both buttons are of equal importance.
You just need to additionally state ‘…unsaved changes will be lost’.
I’ve learned to hit on Mac Command+S to Save constantly.
But, yes, a user might assume that the Pop-up opened because Wappler logic intended to HELPFULLY remind the user that if they wanted to see all their last changes applied that RELOAD would do just that.
Ideally the Pop-up would say what @kenlaji suggested or even it would FIRST say, straight in the user/developer’s face,
"Would you like to save your changes now? Or would you like to RELOAD the page and lose those changes?"
) and that both buttons are of equal importance.