Was this in any of the release notes? I don’t remember seeing this ever.
I have always thought this is how its supposed to work. Because you can’t open layout pages in the browser, and creating a content page without layout meant an app could work with just one page. But not anymore!
Now I would have to make two pages, just to have a home page.
Is there any other way to work without a layout page?
Thanks Teodor.
This is a really vague and incomplete text:
I had no idea this was a bug. There is no link below which would have some explanation as to what has been “improved”.
So, is there no way to just create a simple page directly in NodeJS anymore? I always have to create two pages?
Sid, content pages are just content pages, as their name suggests. They should be loaded inside a layout page.
I understand that.
But you still haven’t answered my question: I have to create two pages to create a simple single pager website in NodeJS?
Also, I am not sure why you guys are not clear about such huge changes like these. The way this was handled is not at all developer friendly.
A similar thing happened when the validation message mechanism “bug” was fixed.
Let alone all the apps in production that are using content pages as simple single page, this change has directly affected the very tutorial that helps users get on-board with Wappler.
And whats even more concerning is when I create a new NodeJS project in Wappler 3.9.7, a default content page is created, with all regular tags and no layout page!!
If you guys would have been more open about such changes, someone would have shared this new project issue in community and it would have been fixed in 3.9.7
I did question this on another thread but nobody responded.
I don't understand why there is the option for Layout None if you can't have a page without a layout.
Well you can always create a static html page and not use templates.
@George will check this.
Because you can choose to attach it to a layout later or change the layout page later.
None, in my opinion, should link to a basic layout, created with new projects that contain the standard frameworks set by the project and just the view component. At the moment, having the option to select None suggests that it should work in this state but it doesn’t. If you’re familiar with this little ‘quirk’ it is fine, but if not can easily waste a user’s time trying to work out what’s going on and increase frustration.
Alternatively, if you don’t like adding a blank layout page to a project, have a warning secondary text message when ‘None’ is selected saying something like ‘Content pages need to be linked to a layout to work when published’:
Added into that it used to work differently than it does now, it is not clear at the moment. I am pretty familiar with Wappler and recently lost a whole chunk of time to this so I think it could and should be improved.
The problem is that full pages and content pages have a very different structure. So if you create a full page first you can’t then convert it to content page and assign a layout.
That is why we decided to go for content pages being just as the name says - content only and not full pages.
Content pages are ment to be included somewhere, so they never function on their own.
It can be in a layout page but also just with a regular content page include.
Thanks @george,
I appreciate the difference between layout and content structures but having the option to select none in the UI makes it easy to think that it is an acceptable option that will show your content page as a working page but with no extra layout-based components.
As I suggest, if you added a default ‘None’ layout page to the Node project when first created (that just included the frameworks and a view component) when someone selected None that page would then work.
