OK thanks.
I need h1s for all the category archives and “…/page2/3/4/whatever” of the blog index page.
So I need to create a duplicate header, with the addition of a div element set as h1. That I can do.
Adding 3 headline elements, not a problem. But setting separate conditions for each of them? I haven’t a clue.:
Thank you for the update. Why do you need to set conditions for the elements within the header? If you can provide the site URL and login details in secure note, we’ll take a look.
i only need the h1s to appear on category archive pages. Not on posts, not on the initial blog index page, If that can be done without conditions on elements, then that would be great. I simply read the thread I referenced in my initial post.
Login creds are in a secure note here.
We tried logging in but the password for the username is incorrect. Please check the password carefully or provide another admin account.
password regenerated.
We added another Headline element in the Hero Post section of the Blog Index layout, then applied the condition category > in > {{dc:url:full_path}}, so the element is only visible on the category pages.
Let us know if this is what you’re trying to do.
The entire blog index page is now broken. I’ve cleared cache, but it’s not returning to normal.
As I mentioned, the h1s are for
The h1s also need to be unique. “[category description] [page n] [blog name]” for example
Can you please revert the blog section back to when it was working?
Would you mind providing a screenshot of the issue? The blog looks the same on our end except for the category pages with the added Headline H1 element.
Main Blog
Business Category Blog
Looks like I have a DNS issue from my side.
From what I remember there shouldn’t be a hero image on …/blog/page/2/ and all following pages.
Anyway, can you please explain how to add custom h1 text for each category archive. For example, posts given the “business” category might have “Articles on business | Page 1”
I had to restore the site from the last backup point to get the blog to work, which suggests my issue is more than just DNS.
As an aside, …/blog/page/2/ should not have a hero image as per your screenshot.
Here’s how it should look:
Why would that be?
To display a headline with the pattern Articles on Business | Page 1 , you can use the dynamic content {{ term.name }} and {{ query.current_page }} . The content of the headline would be:
Articles on {{ term.name }} | Page {{ query.current_page }}.
To learn more about dynamic content and conditions, please check the documentation below.
– https://theme.co/docs/dynamic-content
– https://theme.co/docs/conditions-and-assignments
If you need this to display this headline only on the category pages, you can apply the same condition (category > in > {{dc:url:full_path}}) that we added previously.
Thank you. I will try this and come back to you if I have problems.
To confirm: Is that example code correct? Is there an extra } after {{ term.name }} ?
The extra “}” is not necessary – it’s a typo. We’ll keep the thread open.
I created a row and put a headline element in there. I set the row to {{dc:url:full_path}},
but it’s not appearing on blog archive pages (e.g. …/blog/page/3/) or category archive pages (e.g. …/category/business/page/1/). Can you let me know what I’ve done wrong?
In the first field, you have to add the string "category ". What it means is that when the path “category” is in the URL or full path, the element will be displayed, otherwise the element is hidden. You can check out the conditions documentation that we mentioned above.
Thanks. Now the headline appears, but it’s not pulling in the db query result
Also, if the h1 only appears for category archive pages, how do I get it to appear for blog archive pages ( e.g. …/blog/page/2/, …/blog/page/3/, etc.)? Do I add an “or” condition group with ‘blog’ as the string?
OK, I’ve got further ahead.
Query should be {{dc:term:name}}, not {{ term.name }}. Similarly {{ query.current_page }} should be replaced with {{dc:query:current_page}}
However I still can’t get blog archive pages to work. I tried adding an OR condition of {{dc:post:permalink}} IS /blog/page/(.*) but that didn’t work.
