Jake Goldman
Forum Replies Created
-
No… but my money would be on the GD CPT plug-in. Not sure how it implements custom post types, but this plug-in is strictly designed for WordPress 3.0’s built in custom post type implementation.
There are a few plug-ins that just “wrap” that implementation, like Custom Post Type UI. Not sure about GD CPT.
I just tested it again on 2 different sites, and pagination works as expected…
Are you doing any post queries inside your template?
Does it work if you add a trailing slash? http://www.mysite.com/archive-type/page/2/
Hallenberg – given the way built in post types work, I’m not sure why the post type – as passed to that function – would ever be an array. Can you explain why this would even happen? The check is easy enough, but I’d like to understand before I add any excess weight to the plugin.
I don’t follow your question about the title, though I do think I should probably elevate the priority for a variety of reasons. Are you using a plugin or your own filter that tacks on the blog name? That’s not done by default…
Roy – I’ll investigate the error.
With regard to the taxonomy permalink, define “should.” WordPress is behaving as it’s designed, and the plugin doesn’t alter that.
Here’s what you’re overlooking – what if your custom taxonomy is assigned to multiple post types, say posts and quotes? What should the permalink be? Remember, if you’re sharing the taxonomy across multiple types, archives for that taxonomy should show all posts (irrespective of type) in the archive.
That said, when you register a new taxonomy you have can define the slug with an argument. You could register a quotes taxonomy and define the slug as “quotes/author”.
I may add some native permalinks for logical browsing of taxonomies within post types in a future update. But I’m debating whether that should really be left to a separate plugin.
I think the confusion is coming from the naming of the template file.
Remember – you need to use the post type *name* (the first parameter in register_post_type), not the slug in your template file. To mitigate confusion, I’ll probably add support for type-slug.php in the next update.
pescadito01 – this plug-in is built to work with WordPress 3.0’s native “register_post_type” functionality. Plug-ins like Custom Post Type UI are a wrapper for this functionality. It is not tested with nor built for plug-ins that have their own custom post type implementation.
Let me know if 0.8.5 fixes this for you!
Forum: Fixing WordPress
In reply to: Custom Posts Types and TemplatesIf you’re still struggling, I’ve put together a plug-in that, er, “plugs” this missing piece in WordPress 3.0.
http://www.cmurrayconsulting.com/software/wordpress-custom-post-type-archives/
Adds template files, permalink support, and some other tweaks for custom post type “archives.”
Forum: Plugins
In reply to: Custom post type as an archiveFYI, I created a plug-in that adds fully baked “archives” support to custom post types.
http://www.cmurrayconsulting.com/software/wordpress-custom-post-type-archives/
Forum: Plugins
In reply to: [Plugin: Secondary HTML Content] Minor coding errorsI’m not sure why the widget would screw up the alignment of anything. Can you elaborate?
I tend to think the secondary content should be cleaned up (filtered) just like the primary content. While this does mean plugins that inject sharing buttons into the content will effect other content blocks, it also means that plugins that do things like decode special short codes or add special formatting will work for all content areas. Perhaps I can investigate some advanced options allowing users to selectively disable filters.
Thanks for sharing your feedback!
Forum: Plugins
In reply to: Unlimited HTML Content BoxesWish granted. The plug-in now allows up to 5 HTML blocks on posts and / or pages.
Forum: Themes and Templates
In reply to: my tweets were updated 1 and 40 years ago !!!Time zones definitely in sync on my site / Twitter account as well.
Forum: Themes and Templates
In reply to: my tweets were updated 1 and 40 years ago !!!You know, testing this a bit harder today, I think it also has to do with the time of your last update. If I have a tweet on the current day, it (usually) displays without an issue. If I haven’t tweet for a day or two, the error shows up. Either way, wish the developer would get on top of it.
Forum: Themes and Templates
In reply to: my tweets were updated 1 and 40 years ago !!!I too am having this problem. I haven’t had time to debug the code, but I think it has to do with the AJAX requests being timed out by a poor shared host (Bluehost in this case).
An option to use the old, non-ajaxy widget would probably solve it. Alternatively, I have a feeling a better host wouldn’t stop these requests.
Forum: Requests and Feedback
In reply to: Version 3.0 FeaturesThere’s a lot on my WordPress wish list for the API, but I actually think 3.0 should be almost exclusively focused on WPMU merge. Let’s do one big thing, and do it well, particularly since I think WPMU’s underpinnings and API calls need some serious polishing.
I’ll also go on record saying that a new theme is, in my view, a waste of time. There are plenty of extraordinary themes already out there, and anyone who is serious about their blog isn’t going to stick with a stock theme anyhow. Rather than reinvent a wheel that’s been “well-invented” elsewhere, I’d suggest a mechanism – during install or setup – to choose from a random series of 20ish of the best themes provided by the community. If we’re worried about support for these themes, it’s not unreasonable to hold the developers of those themes to a certain set of expectations or threshold of quality to remain on that premium list.
Once the MU merge is finished, I’d say there is a lot of backend / API maturity needed around taxonomies and custom post types before we start worrying about creating a glitzy UI for managing those.
The way custom, non-hierarchical, post taxonomies get handled should be the standard (well, permalink bugs aside). We should be able to define new hierarchical (category-like) taxonomies, and assign taxonomies to pages, and “all the magic” of automatically adding new menu items and new meta boxes appearing on the editing screen should similarly happen.
I envision a similar future for custom post types. Imagine integrating the “add menu” calls with new post type definitions. So that if we define a “news” type, a new menu items (a la Posts or Pages) gets created, with an edit and add new list.
Granted, I speak from the perspective of someone really trying to push the API to the limits (not just a blogger). But I think we really need to hunker down and grow the core API’s ability to compete with the likes of Drupal on custom types and taxonomies before we worry about more UI polish, which (with a capable API) can be accomplished just fine with plug-ins anyhow (in most cases).
Forum: Plugins
In reply to: [Plugin: Recommended Reading: Google Reader Shared] Issue with date of itemsThanks for the note – I’m aware of the issue. It’s a bit hard to peg down since it seems related to timezones, and my local time zone seems to be fine. We will put out an update very soon to address this.