Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter kenzik

    (@kenzik)

    @mateuszgbiorczyk – Thanks for this, I’ll give it a try.

    I want to be clear that I made no configuration changes after upgrading to 3.0, so the 3.0 version did have a breaking change.

    I would recommended either updating your readme.txt file to make the point about the potential issue with setting hierarchical URLs twice (such as with Toolset Types’ defaults) and/or having your plugin detect if a taxonomy is already hierarchical before your plugin does the same.

    Thanks for your asssistance and thanks for the plugin. It’s been helpful.

    Thread Starter kenzik

    (@kenzik)

    Again, my description of the problem twice was very clear to me.

    I created a CPT and Taxonomy using Toolset types, using their default settings, on a new/stock WP install.

    I do not believe this has anything to do with Toolset Types.

    Here is a very easy to follow set of screenshots. Some screenshots are annotated to help you understand this very obvious bug.

    CPT Config 1: http://prntscr.com/jfvbv6
    CPT Config 2: http://prntscr.com/jfvc1o
    CPT Config 3: http://prntscr.com/jfvc5y
    (Spans multiple screenshots due to scrolling.)

    Tax Config 1: http://prntscr.com/jfvbif
    Tax Config 2: http://prntscr.com/jfvboi
    (Spans multiple screenshots due to scrolling.)

    Plugins (v.2.1.4): http://prntscr.com/jfvcd3

    Category URL without permalink (WP DEFAULT) config: http://prntscr.com/jfvd6w

    Permalink config: http://prntscr.com/jfvdyt

    Category URL with 2.1.4 with permalink config (EXPECTED): http://prntscr.com/jfveq3

    Upgraded plugin (v.3.0.0): http://prntscr.com/jfvf3x

    Upgraded plugin config (no changes made): http://prntscr.com/jfvf9k

    Category URL with 3.0.0 immediately after upgrade (EXPECTED): http://prntscr.com/jfvfkc

    Category URL after changing category name or description (REPORTED BUG): http://prntscr.com/jfvgbx

    Thread Starter kenzik

    (@kenzik)

    There is no code that I need to provide. It’s an obvious bug. To reproduce on a clean/new WP install:

    – Create a custom post type
    – Create a custom taxonomy and assign it to CPT
    – Add a new term (to be parent)
    – Add a new child term (of previously created parent)

    – Install v.3.0.0 of your plugin
    – Use plugin to configure new permalink for your CPT selecting the new taxonomy
    – Click on view on the child term. The archive URL is wrong.
    – Uninstall 3.0.0

    – Install 2.1.4
    – Use plugin to configure new permalink for your CPT selecting the new taxonomy
    – Edit one of the terms (eg. change it’s name)
    – Click on view. The URL is correct.

    I thought I was very clear in my initial report, so I hope the step-by-step helps you, or at least lets others who may have the same issue know that they are not alone.

    In any case, if you do not want to dig into this on your own, which in my experience is usually the case with low-use (but valuable) plugins, then I’ll just continue to use 2.1.4. I currently have it configured to not prompt me to upgrade, so I’m go to go.

    I can confirm that version 2.0.7 does not work in my current environment, nor in a default setup with just ACF Pro and the plugin. It worked prior to upgrading. Unfortunately, I don’t recall the previous version that I had installed.

    I had the first stable version of the plugin (1.0.0) installed on an old development site, and used it instead — it works. I changed the version number on the plugin to 20.0.0 to prevent updates until this is resolved.

    Perhaps the author can (1) Make older versions available; and (2) Install a default setup and attempt to duplicate the issue as I and @websnextlevel have.

    If this goes unresolved, and/or when I have the time and inclination, I’ll fix it in 2.0.x — but for now using an old version is my workaround.

Viewing 4 replies - 1 through 4 (of 4 total)