If you have troubles since the update to WordPress 4.5 please read this post before opening a new thread.
August 31, 2012 at 3:28 pm #15894
not only in my theme, but also in the demo theme http://www.kriesi.at/themes/corona/portfolio-item/asdf/
I’ve discovered obviously a bug:
In theme options I have set at “Enter a page slug that should be used for your portfolio single items” my own: “portfoliomalerei” (in demo theme it is obviously set as “portfolio-item”).
So far, so good, see it in action here in demo theme:
Now take a look at the URL of this page in the browser:
and you see, that for these category slugs a complete other portfolio”slug” is used, in demo theme “portfolio_entries”.
And now this archive page has – the wrong! – URL of http://www.kriesi.at/themes/corona/portfolio_entries/css/, although in theme settings, the portfolio slug is set as “portfolio-items“.
In my own CORONA version it is exactly the same behaviour.
So what can I do, that also these archive pages uses exactly that portfolio slug, too, that I have set in the theme options for portfolio pages?
Because at the moment, I have set it in theme options -> Portfolio to “portfoliomalerei” and the archive pages for a portfolio category is “…/portfolio_entries/schwebende-bilder/”August 31, 2012 at 4:22 pm #89420
As far as I know this is just how wordpress handles archives. That url is generated based on the taxonomy created by the theme when it creates the new portfolio item post type.
I’m really not sure if and how it would be possible to change the rewrite rules for the portfolio custom post type when displaying archives. I’ll have to tag Kriesi on this to see if it something that can actually be changed and what the best avenue for it would be.
DevinSeptember 2, 2012 at 8:58 am #89421
yes, that would be great asking Kriesi; somewhere must be the “portfolio_entries” set. I’ll wait until what Kriesi says to it, thanks.September 4, 2012 at 3:04 pm #89422November 2, 2012 at 12:12 am #89423
Hey. actually not a bug but the way that wordpress handles custom post types.
The slug you are setting in the backend is the slug for single portfolio items. The archive that is generated by wordpress is based on the post type and the coresponding categories. In this case portfolio_entries. Changing this slug name dynamically like the slug you mention is unfortunately not an option since it will invalidate all the existing categories of this post type which would seriously throw off users…
The topic ‘BUG: Portfolio page slug ignored on archive pages of portfolio items!’ is closed to new replies.