• Resolved rjparrar

    (@rjparrar)


    I had to rollback to the previous version of the plugin (free) because after the newest update I realized that there was a taxonomy that was missing. I tried to create it again, but the old key was still registered.

    Any ideas on why this is happening?

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

    (@stevejburge)

    Hi @rjparrar. Thanks for using TaxoPress. Please share more details. There aren’t enough details here for us to give feedback.

    Thread Starter rjparrar

    (@rjparrar)

    I have a taxonomy created for content types (webinars, e-books, etc.), and it was created using TaxoPress. Today, after updating the plugin to the newest version, the taxonomy stopped appearing as an option when creating new resources (pages, custom post types) and all of the widgets that were using that taxonomy as a source for a query stopped working. I had to rollback the version and the taxonomy was there again.

    • This reply was modified 3 months, 1 week ago by rjparrar.
    lquilter

    (@lquilter)

    Same problem. I had an extensive taxonomy, working as of last night; the auto-update happened this morning, and when I came back to my blog this evening, the entire taxonomy was deleted. I rolled back to the previous version (from November 2024) and voilá, my taxonomy is back.

    Plugin Author Steve Burge

    (@stevejburge)

    Thanks @lquilter. We can see this problem now and will release a fix tomorrow with an updated version of TaxoPress.

    pladaak

    (@pladaak)

    After scratching my head over night, rolling back to the previous version and disabling the auto update does restore my custom taxonomy terms. Thank for you report.

    Plugin Author Steve Burge

    (@stevejburge)

    @rjparrar @pladaak @lquilter Thanks for the reports. This should now be fixed with version 3.28.1.

    Thread Starter rjparrar

    (@rjparrar)

    Thank you so much @stevejburge

    murbnai

    (@murbnai)

    Cheers @stevejburge I was having this issue too and it has been fixed now.

    Plugin Author Steve Burge

    (@stevejburge)

    That’s good to hear. Thanks for the quick bug reports, everyone.

    lquilter

    (@lquilter)

    Thanks for the rapid attention and fix!

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.