hennra

Great, I’ll do that! And setting this to resolved is fine
Have a great day too ??
-henna

Hi, thanks for confirming, that’s what I thought but just checked I didn’t miss something ??
I’ll keep checking on the thread if a solution is found
br, henna

Hi Riza!
Was the problem solved yet? Went through the GitHub issue link thoroughly and it is a very similar problem to mine.
br,
henna

Hei again!
I finally got around to contacting BeTheme support and gathering some new info on why Post Expiration is not working in Portfolio items:

Followup:
– Expiration works perfectly on Pages and Posts, thank you!!! I think you should sell this feature directly to every theme! ??

– Expiration works on Portfolio posts IF you expire to draft or some other option. It does NOT work if you expire to “Replace: Category”, because for some reason Post Expirator ceased to recognize Portfolio categories. Probably this happened some time after December 2021: I checked the WP dashboard and those older posts seem to have expired correctly.

BeTheme’s response to this was:
“I checked the changelog and we did not change anything related to the configuration of the custom post type or categories or even portfolio like 2-3 years, we only added new features like Infinite Load or better support for WPBakery.” and also:
“the difference between categories of posts and portfolio is… none – this is almost the same feature, but with other name.
I think, that if you want to make it work you have to tweak the plugin a little bit, I think it does not have queries(or similar) for that CPT.”

Here’s a link to screenshots showing that when in WP and quick editing a Post the categories available and when editing Porfolio => categories are not available:
Screenshot of Post and Portfolio expiration categories

Here’s also a screenshot / hand-picked compilation on one single Portfolio item’s debugging log on PublishPress Future debug log showing that the Expirator tried to expire the Portfolio post but could not due to missing category.
part of debug log

Putting some effort to this again since expiring to different category is an extremely useful thing to have and despite this not working right now, I think your plugin is really great!!! ??

br,
Henna

Sorry to hear that. But I understand it’s out of your reach.
br, henna

Hi!
I’m using the BeTheme, which has a bundled portfolio in it. I checked and none of the intended expirations had worked.

I did a quick test and on normal articles and there the expiration worked! On the test article the post expiration tool also suggested categories to replace to, as it used to do in portfolio items too (and now doesn’t).

br,
-henna

Thanks for your answer! I was a bit too quick this time and already managed to do most of the redirects on Friday. My solution was adding redirects to the .htaccess file. I used:

RedirectMatch 301 /inserted-page-slug https://domain.fi/
when redirecting single inserted pages to wanted domain
and

RedirectMatch 301 /.* https://domain.fi/
OR
RedirectMatch 301 /top-page-slug/.* https://domain.fi/top-page-slug/
when redirecting multiple inserted pages to one location

Anyways I’m interested in knowing the pros and cons of both of these ways (private pages vs. redirectmatch 301) and would be happy to hear if you have an opinion on my solution.

I’ll definitely look in to the “private page” way on some page too since now that I’m aware of the problem (google indexing inserted pages) I can plan a solution already when designing a site. I now found the “Anonymous users can see this inserted even if its status is private” checkbox you advised. I’ve been using shortcodes with copy-paste and changing the slug so I wasn’t familiar with this option before.

-henna