So in the first link you can see the blog page as it is supposed to look. The hero section shows page title and featured image (and breadcrumbs)
The German version’s hero section however displays the content of the latest post.
This happened out of the blue. I suspect it happened due to the latest update from 1.5.4 to 1.5.5 but I can’t say for sure.
I thought it’s Polylang causing the issue but deactivating it did not solve the problem.
Also I deactivated all plugins. That also did not resolve the problem so I guess plugin conflicts can be ruled out.
If you use the archive title {archive_title} instead of the post title {post_title} on the blog archive, it works as it should The English version is not an archive, it’s a regular page, and that’s why {post_title} works.
Your answer explains why it does that, but the problem is they are in fact identical. They are both pages - not archives. I just checked: there is no blog-archive-template set up for any page.
Also I checked in both the english hero-template as well as the german hero-template. They both use post-title. Which makes sense because these hero-templates are used sitewide but the german blog-page is the only one being confused. ^^
The body classes of the pages tell a different story. There is indeed a difference between the pages. The German version seems to be some kind of archive (see screenshots attached).
I’m aware it somehow shifted. The page has an identity crisis. That’s part of the problem I guess.
In the Wordpress dashboard you won’t find the template though. You will only find the page. It’s weird. It’s a bug.
By the way I deleted it once, created a new blog page and the same thing happened: It behaves as if it is an archive.
I don’t mean to be disrespectful and yes I can’t rule out that I’m making some sort of stupid mistake but your response suggests that you are not reading what I wrote.
I summarize:
I am aware that you think it’s an archive
but it’s not
it is a page, as in the dashboard I can only access it in pages, not in templates
Yet on front end, it behaves like an archive. As you can see it even has the archive tag and that’s why it displays the wrong content in the header
Now, granted: I could simply just set the hero to display archive_title but that would just be some sort of workaround hack and I would still have the problem of my page identifying as an archive – which it is not.
I think this has to be solved as there’s no telling what implications this has for the installation. And frankly, if this is happening to me and it turns out to be not my fault , then it might be quite relevant for bricks to be aware of this too.
I thought I could fix it by just switching to Archives altogether but that raised a whole new set of issues (default template being forced despite having deactivated them; Page ID being displayed in URL)
So now I’m at the point where the page (not archive) displays the default template instead of the page content.
Hi Adrian,
I don’t think it’s an archive, but it’s being displayed/treated as such. Why this is, I do not know.
I tested it again and created a German translation for my blog/posts page (default English), and neither of the two pages is output as an archive, giving me the correct result in both cases.
Since I am not able to reproduce the problem, I cannot create a task for it.
On the left is the German version, and on the right is the original English version:
Whether it is an archive or a page depends on whether you define it by what it’s named in dashboard or how it is treated. I wouldn’t know. I was just trying to explain, since you explained how I would find out what it is and told me my page was an archive – which suggested that I had not been able to make my problem clear.
So, at least now I feel like I have managed to get across what my problem is.
Yeah, I was afraid you weren’t gonna be able to reproduce the problem since I seem to be the only one having it.
The “protocol” says that we need problems to be reproducible so that they can be fixed and unfortunately that is not the case.
Can you possibly set up a new test installation, install Polylang and test if the problem is still the same? If so, the steps up to that point (in form of a screen recording showing and explaining) would be helpful.
I’m pretty sure I won’t be able to reproduce the problem either on a new test aka an empty site. It’s this specific installation.
This site in question actually is fairly new (launched around 2 weeks ago). It’s a rebuilt of a formerly WPBakery-Site. Obviously, I’m not very into the idea of building the whole site from scratch again, especially if we don’t even know what caused it and how I can prevent it from happening again if I just rebuild it.
In the following video you can see another weird behavior related to this blog page:
me entering that german blog page. Note how it’s obviously not an Archive, at least not from this perspective.
the bricks builder shows me the correct layout (which is not displayed on front-end) . As I wanna return to Gutenberg-view I magically end up in a post.
So the problem was theslug of one of my categories was identical with the slug of my blog page.
I can totally see a Wordpress site pulling the category template instead of the page in this case.
But I wonder how Wordpress doesn’t prevent people from accidentally doing so.
The English version is not an archive, it’s a regular page, and that’s why {post_title} works.
