-
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
404 on single post page #62
Comments
@sijones-uk have you found any workarounds for this? I tried, but was unsuccessful. For now, are you just using an earlier release? |
@danielshields Unfortunately not, so I can't update the plugin for now, It seems to have been the removal of the line |
I've exactly the same issue - thanks @sijones-uk for the tip to fix in the meantime! |
@sijones-uk @danielshields @Trenbania Replace Sample code https://gist.github.com/torounit/86c3c140071d29cd1b2fd2900f23c813. |
Thanks @torounit. Will this fix be folded into the master branch? |
This seems to be still open with 3.0.0? |
Version 3.1.1 still with this problem. :'( |
Review my comment on #79 for my solution with a 404 handler. |
Since version 2.1.0 I'm getting 404s on all of my single post pages for custom post types. My custom post type (wpbb_job) is defined inside another plugin (WP Broadbean) and has a rewrite slug of 'jobs'. Before v2.1.0 I was able to define the permalink as:
http://<domain>/jobs/%wpbb_job_industry%/%postname%/
where
wpbb_job_industry
is the taxonomy. This would be transformed into something like this:http://<domain>/jobs/marketing/digital-marketing/project-manager/
Since v2.1.0 the permalinks are being converted correctly, but clicking on them results in a 404. Previously the correct post would be displayed.
I've narrowed the problem down to
Rewrite.php
, in particular where you tidied up the code in theadd_hook()
function and removed theadd_action( 'wp_loaded', array( $this, 'add_rewrite_rules' ), 10 );
after v2.0.2. I can't work out why this is causing the 404 though.The text was updated successfully, but these errors were encountered: