Archived topic
category displays twice for each post on archive pages
7 replies · Started by qpaq on November 10, 2020
Hi,
My archive pages for categories, custom post types and tags... they display the meta name (category,tag etc) twice on the listing page; one is above the featured image as UL list, and the other one as it should be underneath the post.
How can I get rid of the repeating meta information of posts in the archive pages and how can I style this page without using WP Show posts as described by here.
https://docs.wpshowposts.com/article/use-static-pages-as-category-archives/
Hi,
They don't seem to display the same thing.
The one above the featured image displays the content type(custom taxonomy perhaps?) while the one on the bottom is the default category used by WordPress.
To clarify: Which one of the two would you like to be removed?
The one above the featured image is added inside your Header element.
The one below is added by default by the theme which you can easily remove by going to Dashboard Appearance > Customize > Layout > Blog.
Click on the Single tab and uncheck "Display post categories".
Hi Elvin, I would like to get rid of the first, the ones above the images. However, there is no sign of the category or content-type meta in the header elements I could find. the category archive pages also have the same problem.
Hi there,
I'm not sure I'm seeing an issue on that page - can you share a screenshot of what you're seeing?
Hi Tom,
I got rid of them with the following lines. I don't know if that was the right way but it seems working. (before it was like this https://www.dropbox.com/s/03y4q5osxxtp0s5/Customise%20Projects%20Archives%20-%20ArkiBee%202020-11-11%2017-51-33.png?dl=0)
/* Archive pages double Category tag display */
.post-categories {
display: none;
}
/* End pages double Category tag display */That looks like you have a function added to your website that's adding the categories into the featured image container.
If you find and remove that function, you shouldn't need the CSS.
I've found it. Thanks Tom, this issue is resolved. You and your team are great!
Glad we could help :)
