hierarchical taxonomy – Selection error

  • Hello,

    Thank you very much for the new version 2.5.1.

    Please look at the below error due to the ‘if (sizeof($taxonomies) == 0)’

    Error: More than 1 heirachical taxonomy detected. You must assign a default taxonomy on the settings screen.

    Most of the sites are working with custom taxonomies. in that scenario, it creates an error.
    I have tried to use general taxonomy “categories” for category replace. but no use.

    Please solve this error. In the previous version, there was no problem.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Steve Burge

    (@stevejburge)

    Hi @nviews

    Thanks for using Post Expirator.

    Can you explain this is in more detail, please? What is happening to show this error? What screen is it on? Can you change settings to make the error disappear?

    Thread Starter Prabakaran Shankar

    (@nviews)

    Hello,

    Thank you.

    To debug this issue, I have enabled the PostExpirator’s – debug log.
    Before update, the plugin the log files are below:

    2021-09-28 14:31:06 1879 -> CATEGORIES COMPLETE Array ( [367] => Ongoing )
    2021-09-28 14:31:06 1879 -> CATEGORIES REPLACED Array ( [367] => Ongoing )
    2021-09-28 14:31:06 1879 -> PROCESSED category Array ( [expireType] => category [category] => Array ( [0] => 367 ) [categoryTaxonomy] => current-status )
    2021-09-28 14:29:39 1879 -> SCHEDULED at Tue, 28 Sep 2021 14:31:00 +0900 (1632839460) with options Array ( [expireType] => category [id] => 1879 [category] => Array ( [0] => 367 ) [categoryTaxonomy] => current-status ) no error
    Note: post id 1879 is custom post type/classic editor

    After being updated to version 2.5.2:

    I’m getting errors as follows in the classic editor (custom post type)

    Expiration Categories:
    More than 1 heirachical taxonomy detected. You must assign a default taxonomy on the settings screen.

    So, I have disabled the filter to use Gutenberg editor. After disabled the classic editor, the above-said error has been disappeared. But, postexpirator does not function its work.

    The debug logs are:

    2021-09-28 15:03:28 2527 -> SCHEDULED at Wed, 29 Sep 2021 00:05:00 +0900 (1632873900) with options Array ( [expireType] => category [category] => [categoryTaxonomy] => ) no error
    2021-09-28 14:53:37 1879 -> SCHEDULED at Tue, 28 Sep 2021 23:55:00 +0900 (1632873300) with options Array ( [expireType] => category [category] => Array ( [0] => 368 ) [categoryTaxonomy] => current-status ) no error
    2021-09-28 14:53:37 1879 -> EXISTING FOUND – UNSCHEDULED – no error
    2021-09-28 14:39:20 1879 -> SCHEDULED at Tue, 28 Sep 2021 23:41:00 +0900 (1632872460) with options Array ( [expireType] => category [category] => Array ( [0] => 368 ) [categoryTaxonomy] => current-status ) no error
    Note:
    post id 1879 is custom post type/Gutenberg editor
    post id 2527 is standard post/Gutenberg editor

    Thank you.

    Plugin Author Steve Burge

    (@stevejburge)

    OK, thanks @nviews

    We’re going to move this issue to a bug report: https://github.com/publishpress/PublishPress-Future/issues/144.

    We may ask for more specific details when we look for a fix.

    Thread Starter Prabakaran Shankar

    (@nviews)

    Thank you very much for your consideration.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘hierarchical taxonomy – Selection error’ is closed to new replies.