francis32

@gappiah @rohitmukati

Thx to both of you ! That confirm what I was thinking ??

”if it’s using the correct template (with no title block in the template), there will be no title at all. Remember, a PAGE (as opposed to a POST) will not be displayed on the homepage or anywhere else… unless it’s configured as the static homepage. And if the page is configured as the static front page, as long as it’s using a template with no title block, no title will be displayed on the homepage at all.”

@gappiah If I want to create a custom page… Do you think it is better to :

-Create a custom template in the theme editor and assign that template to a page ?

or

-Create a blank template with the ”post content” block and start from there in the page editor ?

In other words, is it ”normal” to build an entire custom page as a template or should I use the post content block and build with within a page.

Thx !

Francis.

Thx a lot for the answer @jordesign,

Unfortunately, I’ve just spend one hours trying to replicate it with a few new sites in Local but could not, weird !

I’ve look into my theme.json file into my ”bugged” theme, and everything seem fine under settings — typography. Tried to export/import and bug is still here.

Not really sure where the drop-down menu inside the blocks are referencing the font list.

Is it possible to create a bug report by providing a theme.zip if I can’t reproduce it ?

I’ve created a new site with Local, and it indeed seem that deleting all font in the list prior to adding a new one will create a bug where WP doesn’t snow any of the font listed in the addon.