[wp-hackers] Please help diagnose custom post type permalinkproblem
Philip M. Hofer (Frumph)
philip at frumph.net
Sun Dec 12 16:27:29 UTC 2010
Are you using register_taxonomy() on the "rsvpmaker-type" ? I noticed you
using taxonomy => in the register for the post type instead of
You're also using 'rewrite' => true - instead of 'rewrite' => array( 'slug'
=> 'rsvpmaker' ) which is fine; of course I would do: 'rewrite' => array(
'slug' => 'comic', 'with_front' => true ), to make sure that just in case
if someone is using subdir installation of wpms can attach /blog/ at the
front .. (as far as I understand how that works)
I've done a lot of work with custom post types recently and only encountered
something like that if I wrote something out of place when it was trying to
create the rewrite rules .. or some other plugin was interferring.
There are a few themes and plugins that check all post types instead of just
the one they're working with.
for example they're doing this:
$args = array(
'public' => true,
'_builtin' => false
$output = 'names';
$operator = 'and';
$post_types = get_post_types( $args , $output , $operator );
which basically gets all custom post types then working with them, so what
is happening is its creating a different set of rewrite rules then the ones
intended (if they work with it afterwards), ... so could you look at what
else is running on her setup and see if it could be conflicting?
----- Original Message -----
From: "David F. Carr" <david at carrcommunications.com>
To: "wp-hackers" <wp-hackers at lists.automattic.com>
Sent: Sunday, December 12, 2010 6:39 AM
Subject: Re: [wp-hackers] Please help diagnose custom post type
> You can see the website that's experiencing problems here:
> <http://lvrunningscene.com/events/special-events/>The headline and RSVP
> button both have a link generated with get_permalink, which seems to be
> correct. But if you try to follow the link, you get a 404 error.
> On Sat, Dec 11, 2010 at 10:41 PM, Vid Luther <vid at zippykid.com> wrote:
>> Can you share the site url? The problem you describe is hard to
>> diagnose as a thought problem. If we had the url, we could inspect the
>> headers, and try to see if we can replicate the issue, or possibly find
>> an isuse on the server itself..
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers