Incoming version 1.0.2

What just happened to my website…. I Just updated the plugin now all my custom post types are returning 404 errors?

Can i revert back to previous version?

I have hundreds of pages using custom post types and we have 1000’s of people on the website each day so need this fixed asap.

Please explain what has just happened and how i can fix it please.

Thanks,

Yes you can revert if necessary, but if you could please, try refreshing the permalinks first to see if that fixes the issue at hand. If it does not, continue with the revert using the link in the first post here, and I’d appreciate working with me to figure out what went wrong with the update.

Reverted back to old plugin, switched via FTP and refreshed permalink rules and working again now.

Think i will wait for a while after custom post type plugin releases in the future.

Thanks

Sorry, Michaeal. I just saw your message. Already reverted back to old version now.

Thanks for responding so quickly though, nice to see active developers on this forum.

Keep up the good work.

If you have a staging/dev site that you could use to help test, that’d be awesome, but not a requirement.

We had this same problem.

It may be to do with your old values for instance for ‘rewrite’ being 1 or 0, and the new ones being true or false, and the check to decide whether to do a rewrite_slug?

Simply going in the backend and saving the options seems to correct it, ie. it puts a ‘true’ in the field instead of a ‘1’ for the get_disp_boolean() function to evaluate correctly?

a.

string ‘1’ should have evaluated to true with that one, but I think the issue with that was actually from inside the register_post_type() function, and our code was amended to hopefully fix that in 1.0.2 this morning.

ATTENTION ALL!! I’ve got a simple fix that doesn’t require reverting:

If you’re getting the 404 error issue after applying the new update, simply go into the Edit Post Type screen in the CPT UI admin, choose any custom post type for editing, the hit the Edit Post Type button without making any changes. This will reestablish all of your permalinks for you custom post types.

I had multiple sites that broke because of this and I was able to fix them all quickly with this method.

Michael, this issue aside (shit happens sometimes, I know), I have to say I’m not a big fan of the UX/UI change. The previous version’s presentation for listing out custom post types/taxonomies was more comparable to a basic WordPress interface and, therefore, more familiar and comprehensible. The accordion functionality of the labels/settings fields feels a little clumsy, too, and doesn’t fit well on smaller screens.

Friendly suggestion: make the UX/UI look and feel just the default interface for pages/posts. In other words, just have them list out in the same fashion with an “Add New” button next to the section title. That way you don’t have to teach folks how to use a new interface.

That said, it’s a great plugin and I really appreciate your hard work!

Thanks!
Mark

@markkanning, I posted your thoughts over at https://github.com/WebDevStudios/custom-post-type-ui/issues/225 and feel free to chime in if you want to go into more detail regarding it.

Michael, I updated 1.0.2 on my live site.. Everything works! Great job! Enjoy your holiday!

*thumbs up*

Hey Michael,

I just read the comment by rpkoller on GitHub and I think he’s got some good ideas. The analogy to Advanced Custom Fields was a good one. ACF does a great job of handling a complicated data set in a comprehensive way. Also, the listing of custom fields behaves just like the WordPress pages/posts sections with the familiar group of edit/duplicate/trash buttons for each listing (no UX learning curve!).

One last thing: the import/export functionality of ACF is pretty straight forward, too. On the export screen, you just choose via checkboxes the fields you want to export and hit a “Download” button. The import screen is just uploading the exported file. Voila!

Anyway, I hope this is helpful info. Happy coding!
Mark

Posted it over on the issue as well, so I can keep everything in one place the best I can. Thanks Mark.

@markkanning, I tried your method on a dev site, and while the 404 error disappeared, I’m still not seeing the custom taxonomy listed under my CPT. Has anyone else had this issue? I’ve tried refreshing permalinks as well. Thanks.

mkvgs, the lack of listing in the submenu won’t be permalink related, it may be a case of simply editing the taxonomies and re-checking the associated post type option. Hopefully a very quick task, but do make sure to take care of it on version 1.0.2 as there was a fix between that and 1.0.1 related to the checkboxes.