Portfolio settings have changed, previous feature not working

Hi!

Sometime during winter/spring 2022 the settings of portfolio articles have changed so that a feature, that previously was there, ceased to work:

I am using a plug-in called PublishPress Future (previously Post Expirator), which expires posts or changes the category of the post on a chosen date, so that the post is then shown in a different part of the site.

The plug-in still works fine on all Pages and Articles on my BeTheme-operating site, but it stopped working in Portfolio articles, which is a huge distress, since the client is an art faculty, with many shows ending at different times - all built as Portfolio items.

What changed and how to fix this?

br,

Henna

Comments

  • Hello Henna,

    All changes made to the theme are mentioned here: https://support.muffingroup.com/changelog/

    But, as I remember, we did not make any bigger changes in the portfolio feature, it was like header and woocommerce season.

    Sorry, but we do not know that plugin which you use and we do not know how it works, so we are limited to help because we just dont know what modifications could interfere with our theme.

    Thanks

  • Hi and thanks for the changelog, went through it a bit and also checked some things on WP end:

    The problem is currently on the page administrator side, that whereas Pages and Articles show available categories when Post Expirator is activated, on Portfolio articles the categories are not available to Post Expirator. So there must be something different in Portfolio Categories settings VS. Article Categories settings.

    This I believe is something you have changed in one or several of BeTheme updates. Could you go through the BeTheme update logs looking for changes there?

    I checked the WP Portfolio dates and now believe that Post Expirator last worked correctly in December 2021, so the change should be in either in late December or early January (or February at latest) updates:

    Maybe on update Version 25.1.8 - January 4th, 2022:

    FIX: Minor PHP Warning: Undefined array key 'HTTP_USER_AGENT' or

    Version 25.1.9 - January 18th, 2022:

    Minor PHP Warning: Undefined array key 's' or

    Version 25.1.9.1 - January 18th, 2022:

    Muffin Live - PHP error preventing opening


    Could be some other fix too since I'm not into php, trusting you know far better than me :)


    For example, below is a part Post Expirotor plugin debugging log, all items concerning Portfolio post nro 5346, which should have expired at 2022-09-04 20:00:04 and did not:

    2022-09-04 20:00:04 Called postexpirator_expire_post with id=5346

    2022-09-04 20:00:04 5346 -> PROCESSED category Array ( [expireType] => category [category] => Array ( [0] => 15 ) [categoryTaxonomy] => [enabled] => 1 )

    2022-09-04 20:00:04 5346 -> CATEGORIES REPLACED Array ( [15] => Menneet näyttelyt Galleria 5 )

    2022-09-04 20:00:04

    2022-09-05 10:43:41 5346 -> CRON EVENT SCHEDULED at su, 04 syys 2022 20:00:00 +0300 (1662310800) with options Array ( [expireType] => category [category] => Array ( ) [id] => 5346 ) no error

    2022-09-05 10:43:42 Called postexpirator_expire_post with id=5346

    2022-09-05 10:43:42 5346 -> CATEGORIES MISSING category Array ( [expireType] => category [category] => [categoryTaxonomy] => [enabled] => 1 )

    2022-09-05 10:50:30 5346 -> CRON EVENT SCHEDULED at su, 04 syys 2022 20:00:00 +0300 (1662310800) with options Array ( [expireType] => category [category] => Array ( ) [id] => 5346 ) no error

    2022-09-05 10:50:30 Called postexpirator_expire_post with id=5346

    2022-09-05 10:50:30 5346 -> CATEGORIES MISSING category Array ( [expireType] => category [category] => Array ( ) [categoryTaxonomy] => [enabled] => 1 )

    2022-09-05 10:50:31 5346 -> NO PAYLOAD ON SAVE_POST

    2022-09-05 10:50:59 5346 -> CRON EVENT SCHEDULED at su, 04 syys 2022 20:00:00 +0300 (1662310800) with options Array ( [expireType] => category [category] => Array ( ) [id] => 5346 ) no error

    2022-09-05 10:50:59 Called postexpirator_expire_post with id=5346

    2022-09-05 10:50:59 5346 -> CATEGORIES MISSING category Array ( [expireType] => category [category] => [categoryTaxonomy] => [enabled] => 1 )

    2022-09-05 10:51:00 5346 -> NO PAYLOAD ON SAVE_POST

    2022-09-05 10:51:28 5346 -> CRON EVENT SCHEDULED at su, 04 syys 2022 20:00:00 +0300 (1662310800) with options Array ( [expireType] => category [category] => Array ( ) [id] => 5346 ) no error

    2022-09-05 10:51:28 Called postexpirator_expire_post with id=5346

    2022-09-05 10:51:28 5346 -> CATEGORIES MISSING category Array ( [expireType] => category [category] => Array ( ) [categoryTaxonomy] => [enabled] => 1 )

    2022-09-05 10:51:28 5346 -> NO PAYLOAD ON SAVE_POST


    br,

    henna

  • edited September 2022

    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.

    You should contact the plugins author in this case, we do not support this plugin so there is no code dedicated for handling that plugin.

    thanks

  • Thanks! Could you tell me a bit more info on how Portfolio items differ from Post items?

    I did ask the PublishPress Future plugin developers for help too, the response was:

    "What portfolio plugin are you working with here?" My answer was that it's bundled up in the theme. They replied: "Sorry this isn’t something we can test as we don’t have a copy of that commercial theme. I would recommend asking BeTheme support."

    So maybe i could get some help from there if i knew a bit more about the differences or the anatomy of Portfolio items :)

    br,

    henna

  • And even more specifically: how are Post categories different from Portfolio categories? Because the expiration plugin works fine, if it expires the Portfolio article to draft. It just can't find the portfolio categories. On the use side this shows like this:

    Post:

    Portfolio:

    Putting so much effort to this since expiring to different category is an extremely useful thing to have. Maybe you could even look into this and integrate expiration in BeTheme at some point? :)


    I have also thought of going around the problem by changing Porfolio items to Post items. Unfortunately Posts do not support BeTheme the Layout-tool, and I have a total of 5 slightly different Layouts for Portfolios, and the client should be able to use them easily. Another propositon due to this is for BeTheme to enable Layouts on Posts too.

    br,

    henna

  • Well, 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.

    If you would like to see that plugin fully compatible with BeTheme, please post your suggestion here:

    thanks

  • Thanks, I left a suggestion for future update :)

    And also contacted again PublishPress Future / Post Expirator.

    all the best,

    -henna

Sign In or Register to comment.