Pending 1.0.5 release

  • ResolvedPlugin Contributor Michael Beckwith

    (@tw2113)


    The BenchPresser

    9 years, 8 months ago

    I have 1.0.5 almost ready, and would appreciate anyone willing to help test it.

    Changes include:

    • Providing a rewrite slug upon registration, regardless of provided setting. If you provide a custom slug, it will use that, but now if you don’t provide one, we explicitly provide the default which is the post slug/name that you put in the first field. I’m hoping this clears up more issues.
    • Prevent cptui.js from loading where it shouldn’t.
    • Provide default labels for labels that specifically mention the post type or taxonomy, when none are being provided.
    • Clearing up undefined index notice for post type rewrite_withfront values.

    Download link for people willing to test: https://github.com/WebDevStudios/custom-post-type-ui/archive/1.0.5.zip

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

  • Sorry, doesn’t work here. Tried the permalink save, CPT save, CPT change save & change back save. When I install 0.9.5 again that does work.

    After updating last week, none of my CPTs were displaying on my sites. I found that I had to go to “Edit Post Types” and select each CPT from the dropdown and save. This fixed everything. Hope this is changed in the update since it’s very time consuming if you’re updating many sites that use the plugin.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Wish I knew what wasn’t getting converted properly in those cases, which is frustrating for everyone.

    Having similar problems with 404 pages with v1.0.5. Clearing caches/permalinks/saving post types isn’t cutting it. Reverting to using Default permalinks (?p=123) lets me view the pages again, but that’s the only solution I’ve found and not one I want to stick with.

    Happy to experiment for you if you need a guineapig.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    marblegravy, if you would be so kind to test changing the priority on this line, around line 95 of custom-post-type-ui.php from 11 to 10.

    add_action( 'init', 'cptui_create_custom_post_types', 11 ); //Priority 11 so that the taxonomies are registered first.

    and see if that helps fix rewrite issues

    Thanks Michael,
    That change worked on the site I was having difficulty with.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Awesome, yet perplexing why such a tiny change has the effect it has.

    Hey Michael, the change from priority 11 to 10 also works on my test-site with 5 CPTs! Is this it? The permanent fix? Time for a 1.0.6 update?

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    I am bumping it back up to the default 10 priority in 1.0.6, as well as fixing a help icon issue pointed out to me on GitHub earlier. Hopefully pretty soon.

    It’s not a bulletproof fix because I have had people need to go all the way up to priority 1 to get the rewrites to work, but I think that may be a specific install thing until I know otherwise.

    10 has worked the most frequently here.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Unsticky-ing as 1.0.6 is out the door now

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Pending 1.0.5 release’ is closed to new replies.