Thread Starter
Mike
(@mgriffis)
Thread Starter
Mike
(@mgriffis)
I was able to circumvent this problem with a simple hack that I added to my functions.php file.
PROS is the name of my custom content type.
To use this hack on your site, you’ll need to change every occurrence of PROS in the code below to the name of your custom content type.
/* Populate the query variable
------------------------------------------------------------ */
function pros_add_rewrite_rules($aRules) {
$aNewRules = array('pros/([^/]+)/?$' => 'index.php?post_type=pros&name=$matches[1]');
$aRules = $aNewRules + $aRules;
return $aRules;
}
// hook add_rewrite_rules function into rewrite_rules_array
//
if ( !is_admin() ) {
add_filter('rewrite_rules_array', 'pros_add_rewrite_rules');
}
This is a stupid little hack. Your mileage may vary. (You’ll want to remove it when the plugin is updated.)
I need to get this updated in the core — the workaround demonstrates that WP has changed their rewrite logic.
Same problem here. All my Permalinks are leading to 404s. Thanks for the hack, will try and play with that.
Same problem here.
The hack works great, but only on first level posts.
on child posts I still get a 404
I hope this can be fixed!
It’s in the bug-tracker — I just need a paying gig so this can get on my radar.
Hi fireproofsocks
just made a donation, I’m a big fan of your CCPM!
is this below the bug we are talking about?
https://code.google.com/p/wordpress-custom-content-type-manager/issues/detail?id=534
I had actually found the tracker, I was asking if the bug I linked is the very one we are talking about here.
I want to be able to keep an eye on it 🙂
Thanks Mike for the wonderful solution..works perfectly! 🙂
Kudos to FPS for the wonderful plugin!
Bluantinoo – I’m not sure if you were ever able to figure this out but I had some (dumb) luck with a workaround for the permalinks of child pages. I figured I’d write a blog post about it… http://www.tunedevelopment.com/custom-content-type-manager-hierarchical-post-type-issue-workaround/
Did you find a different solution?
Hi msartori,
actually I did not.
I was lucky that in all installations where i used CCTM I never needed hyerarchical custom post types.
the only website where I had hyerarchical CPT I needed child posts just for admin purposes and using Mike’s solution fixed the parent posts… so this issue was not really harmful.
I’ve read your post and I’m sure I will use your workaround if I’ll need to build a hyerarchical CPT. When I’ll do I’ll surely post a feedback in this thread.
I’m quite sorry that fireproofsocks does not have the time to fix this issue, because even if there are others super-awesome plugins for managing Custom post types (free or premium it’s the same, I don’t really bother spending some bucks if the tool saves my time), I still prefer CCTM because it’s not invasive and can be coupled with a lot of other plugins or custom code.
For example: I use very often CCTM to build custom post types but another one (Advanced Custom Fields) to manage custom fields. Never had a problem! All plugins should be granular, I hate the “all-in-one” trend of premium plugins!
I’m working on fixing this — the WP architecture surrounding URLs is not easy to work with, unfortunately. Since the time commitment is considerable, I’m considering implementing this as part of a pro version of the CCTM.
Thumbs UP for fireproofsocks! 🙂
1. bluantinoo – I’m glad you haven’t run into anything that made you stop using CCTM.
2. fireproofsocks – I’m excited to see what a paid version looks like…mostly in terms of support. I suppose you’d need commitments from people before you dedicated all of that time. Count me in.
