Could you check the contant page root node properties to see if the head page is correctly linked?
You can’t we have to implement that first.
Do note that the regular includes and user stylesheet like style.css are already included.
So only very custom css isn’t
You mean this:
Take a look at this page:
Many languages other than English can potentially encounter the UTF-8 problem. All those who start using Fw7 will potentially face other identified problems.
And Yes, there are also individual solutions in the form of custom fonts or any third-party connections, which are also not displayed at the moment, due to the lack of connection of the full header.
This leads to the user doing completely ungrateful, APE-like work. To build a page correctly, you either need to make a lot of clicks in the browser to see how the page changed after each design change. Either create all the pages on the main page (since it is the only one that is displayed correctly in the Wappler editor), and then cut the code and paste it into the desired pages. Don't you think that Wappler is Capable of more than offering to copy-paste from one page to another to its users?
Yes indeed - but now I see you are using Framework7 on a regular web project?
We have implemented the main page data picker for mobile projects only. Will add it for the web ones as well in the next update
This is weird - you should have utf-8 and fw7 icons included just fine on content pages as well. @patrick will check it.
Great. This will do a lot of good.
Well. But I still encourage you to think about including the full header. Or make a choice so that the user can connect a full header in case of individual project features.
I'll explain my motivation so you don't think it's a whim. I am guided primarily by common sense. You are currently creating incomplete functionality in Wappler, wasting your energy and time on it. This functionality is only useful in certain circumstances. And if only the conditions change a little, your functionality ceases to fully perform the task for which it was created. This is very bad from an engineering point of view.
Given example. The visual design function in the Wappler editor allows you to visually see how the page design changes and build further work with this page based on this. If the visual representation of the editor can't clearly convey the design or does it incorrectly, then in fact this functionality stops working for the user, because the user can't rely on it.
Now imagine that a user makes a project with some custom connections on the main page that affect the design. There are a lot of examples, but the most banal thing is non - standard fonts. For example, these fonts are very stretched in width. Accordingly, they strongly affect the design, especially the design in mobile resolution. And this user builds a page, relying on the visual editor Wappler, and after many hours of work and settings, he goes to the page in the browser and his heart starts to bleed... Everything that he did for so long looks like a piece of garbage, because the visual editor of Wappler did not take into account all the connections that affect the design.
I am convinced that it is a design error to waste time and build functionality that does not work properly and can betray the user. This of course applies to those cases when there is a rational solution to make the functionality complete. That's my motivation.
