This topic has 9 replies, 3 voices, and was last updated 4 years, 3 months ago ago by Olga Barlow
Hey support team,
I have an issue with breadcrumbs in archive pages. There is .. nothing. No margin-top … just content below the header. They are disappeared. No breadcrumbs there in archive pages. Whats wrong with my setup? Everywhere else breadcrumbs are working.
I also can’t find an option panel where I can set up.
I need breadbrumbs (with titles) in archive pages too. How can I achieve this? Is it possible?
Thanks in advance
Stefan
Hello,
Theme Options > Breadcrumbs, or Edit page > [8theme] Layout options > Breadcrumbs Style http://prntscr.com/qr3wqp
Regards
This breadcrumbs panel I found already. All breadcrumbs working fine … EXCEPT portfolio archive pages (portfolio categories). There are no breadcrumbs appearing. I can’t find a panel or option for this case. Inside breadcrumbs panel is no archive page function or something else.
Archive pages are generated by wordpress and have no “edit page” link.
Hello,
We do not have this problem on our test site. Please provide temporary FTP access, so we can take a closer look.
Regards
I already posted it in my first post here. Ok, here it comes again …
Hello,
You have disabled the breadcrumbs for the blog page in page settings http://prntscr.com/qr8ov8 and it caused the issue with the portfolio categories breadcrumbs.
Do you want to remove breadcrumbs for the blog page or disabled them by mistake?
Regards
Aha! Ok! Thanks for your answer. I don’t know yet that wordpress generated (portfolio) archive pages depends by my custom blog page options. I never mind single page options (with blog (archive) inside) would have an influence to portfolio archive page properties. Good to know.
Thanks for your explanation!
Now it works. Great! Nice job! I was starting to go crazy at first. Thank you!
Hello,
We’ll try to fix this issue in one of the next updates. But keep them enabled until this happened.
Regards
The issue related to '‘portfolio: breadcrumbs & archive pages’' has been successfully resolved, and the topic is now closed for further responses