SOLVED: Archive template conditions issues

Bugs
1

Bricks Version: 1.5b

Hi,

I can’t get a specific archive template applied to the associated post type on frontend.

In the builder, everything looks OK, but on frontend it seems like some default archive template is applied.

If I select “All archives” instead of my CPT’s post type, it seems to work, though, but it is not an acceptable solution because it impacts all other post types.

I’ve resaved permalinks, tried with custom and default archive slugs, there’s no (visible) conflict between archive/posts slugs…

  • Builder:

image
image1195×653 142 KB

  • Frontend with post type selected is NOT OK:

image
image1570×310 18.6 KB

  • Frontend with “all archives” selected is OK (except Bricks post title element which shows first post title instead of term name but maybe the element doesn’t handle CPTs…yet!):

image
image1404×694 148 KB

1 Like
2

Hey Yan,
We had several problems with archives and templates in the beta.

I cannot reproduce the issue with the soon-to-be-released 1.5 RC. Would you be so kind as trying it again once the version is out?

Best regards,
timmse

1 Like
3

Issue still here in 1.5 RC2 :frowning:
I can’t even apply my template to blog archives.
Only works with “All archives” and “Categories & tags”.

Also it looks like if no condition is applied on template, it is applied to ALL archives by default.
So “All archives” option seems useless.

And if I choose “Post type” and I don’t select any post type, it doesn’t default to all post types like indicated.

And when selecting “Categories & tags”, it is applied to all CPT taxonomies archives!

It seems there is a critical design flaw in templating system :frowning:

Finally, it doesn’t seem to be related to 1.5beta because I have the same issues with 1.4.0.2.

Anyone else using archives???

5

Hi @timmse,

My bad, I was not using conditions the right way!!!
I had not noticed that when selecting “Categories & tags”, there was a new dropdown below :frowning:
Sorry for the disturbance!

This can be marked as SOLVED (or even deleted).

2 Likes