Updated and now 404

Is anyone willing to help me test 1.0.3? Specifically anyone that’s already on 1.0.2 and has it working? There are some rewrite rule logic changes that I’m worried about for people who got back to a good place, and I would love to have it confirmed that these changes do not break something again. If you have a dev site that you can try it on, I would appreciate you for forever.

Doing what I can to prevent more issues on a mass scale, if possible. Please let me know and I’ll link you to the appropriate zip file.

I have a development site that’s not currently working, and I’d be happy to help use it to figure out why – I’m having what I believe is the same 404 error, though I didn’t update the plugin, I installed new and the custom post slugs have never worked. Listing their contents works fine, but not viewing an individual one.

I’ve used this plugin on other sites, though, and love it.

majorredbeard, see if https://github.com/WebDevStudios/custom-post-type-ui/archive/master.zip proves to be a working solution at this point.

I’m holding off on updating the .org repo until I’m more assured that things will work as expected.

Thanks for the quick reply!
Unfortunately, it doesn’t seem to have corrected the issue. I moved the old plugin to another folder, installed the Master one, and after enabling it, I still had the 404 error for the “case” custom post type. I also tried re-saving the permalinks a couple of times (switched to numeric permalinks, and then back), and still the 404 error is happening.

Would it help to have access to the website?

It would, as I’m not sure what’s going wrong off the top of my head, and I’d need to see things first hand.

Out of curiosity, before we send any login creds my way, have you tried with no other plugins enabled? They can have effect, but ideally they wouldn’t.

Which version did you upgrade from before? 0.9.5? or 1.0.0/1.0.1 ? Before trying the master copy above at least.

Yes, just before I sent the last reply I tried disabling everything, and also re-saved the permalinks while things were disabled just in case. No dice.

There are many other plugins on the site, though none specifically that I thought would conflict with things.

I thought it might be the theme – the theme does have it’s own custom post types, which I often dislike, but we chose it because of looks, and not necessarily functionality/compatibility, unfortunately ??

michael @ webdevstudios.com will reach me for any sort of temporary admin login creds.

Credentials sent – thanks so much for having a look. I hope I can help. The site is planned to go live tomorrow, and I actually just had the thought to switch the custom posts to regular posts, since we’re not using the site as a blog at all, and display them that way.

That could work, as we don’t have much custom data for the custom posts.

If the theme is causing a conflict, that’s probably what I’ll have to do.

will try to get to it soon, but i can’t promise right away. That said, if you don’t hear back from me as early as tomorrow evening, nudge me.

majorredbeard

Not sure what happened, but when I tried to set the permalinks to the default “ugly” ones, in order to test some things, I got logged out and seem to be in an infinite loop trying to get back on. Hopefully you know what’s going on there and perhaps why. I do apologize if I caused any major issue with this, it was not my intent, as I was wanting to get your post type back in working order.

Hey, no worries, this happened to me too when I was trying to edit permalink settings earlier to troubleshoot. The .htaccess file gets wiped out for some reason, and I have to restore the .htaccess settings, and then edit the database to restore the permalink structure.

As the site is going live late this week or early next, I may flip the custom posts to regular posts, and display them that way.

Just so I’m clear, at least with your current setup, there’s no way to just have the default ugly permalinks? Or there just needs to be some specific steps to get to that? The reason I was trying was to see if it was a rewrite issue or a larger querying issue.

hi

I also faced the same problem. make sure you have selected has_archive to true. Hope it help someone

Many thanks for posting info about setting ‘has_archive’ to true. This has fixed the issue (pages returning 404) for me after updating to version 1.02, but it is now showing old posts as well as new.

Where can I get an older version of the plugin?

Got this to work by enabling ‘has_archive’ to true, then setting it back to false. Had to do this for each of the custom types I had.