DUPLICATE: Content Type under "Template Settings" not showing any options in the dropdown menu

[Gaby]

Under Template Settings/ Content Type/ no options are available in the drop-down menu

[timmse]

Hi Gaby,
Thanks for your report!

What kind of template type is it?

If it’s a section template, it’s expected that the dropdown is empty, as you can’t directly assign a section template using a condition. Therefore, you can’t preview it in e.g. a single page or post.

Are there any browser console errors that appear after opening Settings > Template Settings > Populate Content?

[Gaby]

Hi, It’s an Archive template for the default posts. It has miracously re-appeared today but now the template is not being applied to the blog listing page. Bricks default template is showing instead despite the fact that I have the setting for showing Bricks default templates disable. Just some quirks of this version I suppose.

[timmse]

This is expected for the WordPress Posts Page.

The Blog page selected in WordPress Settings > Reading is a special page, not a normal archive. To apply a Bricks template to that page, set the template condition to Individual and select the Blog page. An Archive condition for Posts will not target that page.

My Blog page is not using the posts archive template - Known issues

Also, Populate Content only controls what you see while editing the template in the builder. Frontend rendering is controlled by Template Conditions.

If the template still does not apply after changing that condition, please send temporary login credentials and a link to this thread to help@bricksbuilder.io

[Gaby]

Thanks, I should have clarified that this behaviour was despite having conditions set-up correctly.

I have two conditions set-up on this Archive Template: 1) Archive/ All Archives and 2) Individual/ Post/ Blog (page) and despite this the blog page is showing the default template.

I’ll send access via e-mail.

[timmse]

Thanks for the login!
The blog page was set to “Rendered with WordPress” instead of “Render with Bricks”, so I clicked “Render with Bricks” to fix it.

There are two possible reasons for this: you clicked on it by accident, or the blog page was edited using Bricks and saved as “empty”. If the latter is the case, we’ve already received a report about it, and it should be fixed in one of the upcoming versions:

WIP: Page renderer changed when editing Gutenberg page in bricks

Site with single page theme applied to all pages outputting Gutenberg content to the bricks ”post content” widget. If I edit any Gutenberg content only page using bricks (Often just to edit theme settings etc) and then save with no bricks content, then the page is changed to render with wordpress in the front end. Only happens if there is no bricks content.

[Gaby]

Thanks. I think the second happened. I originally was messing around in the blog page creating some sections with bricks so I then deleted everything in the page and went to create an Archive template for the default posts.

[timmse]

Okay—in that case, I’ll mark the report as a duplicate and close it. As soon as the fix is ready, we’ll post an update in the thread mentioned