Forum Replies Created

Viewing 15 replies - 46 through 60 (of 62 total)
  • Plugin Author prettyboymp

    (@prettyboymp)

    Terms should already have a description field when editing them directly in the /wp-admin/edit-tags.php?taxonomy={taxonomy} page. Is there something not working as they do for built in taxonomies?

    I’ll try to set aside some time to get the hierarchical post type features added this week. I’ve been holding off just because I haven’t tested it much and have yet to run across a need myself for a hierarchical post type.

    As for the registration not working, its probably a timing issue. CMS-Press registers the post_types on the ‘init’ action. So if you’re trying to link to the post_type before then, it isn’t going to work.

    Yes, the template handling is built in with the following templates:

    home-{post_type}.php
    index-{post_type}.php
    single-{post_type}.php (how core handles this now)
    {post_type}.php (for cms-press backwards compatibility)
    date-{post_type}.php

    The save_post action runs on autosave as well, but autosave doesn’t post back custom fields. You need to check against wp_is_autosave($post_id) and wp_is_post_revision($post_id) before updating the meta values.

    I’ve only ever seen this error on a server running PHP4 with PHP only code. Is there a chance that instance is running 4? Try adding the following temporarily to your wp-config.php to be sure.

    phpinfo();
    die();

    This is fixed in 0.1.6. Thank you for the notification.

    add_theme_support( 'post-thumbnails', array( 'post', 'page' ) );

    Add the above to your theme’s functions.php, but replace ‘post’ and/or ‘page’ with the name of your custom post type.

    Wow, lots of questions.

    1) I haven’t looked at the custom-post-type-ui plugin much, but from what I have seen, my understanding is that it does exactly as it says: providing a user interface to creating custom post types. While this is cms-press’s main functionality at the moment, the end goal for cms-press is different in that I’m trying to use cms-press to make WordPress a more robust content management system. I need to do a much better job of documenting the things that cms-press does beyond just adding the post type like adding handling for custom date, home, search, and index templates for the post types and more robust URL building.

    2. Yes, it does support pretty permalinks. In fact, I haven’t done enough testing to even know that it works without pretty permalinks.

    3. The custom post types aren’t added to the main feed on the site, but they are given their own feed. When cms-press builds the permalinks to support the custom post type, it includes the feed permalinks as well. So if your ending permastructure is /foos/bar-post/ then you can go to /foos/feed/ to get the feed for the foo posts

    4. Re: Linking built in taxonomies to custom post types, I have this on my to do.

    Are you running this in PHP5 or PHP4. Only PHP5+ is supported.

    Those are both bugs. I haven’t had as much time to keep up with the changes going on with custom post types that last few weeks. I’ll get a new release out soon.

    Yes, cms-press takes care of this. Instead of using the default permalink handling for custom post_types, cms-press takes the permastructure you setup for the post_type and breaks it down so that the pieces that make up that URL should be browse-able as well. So if your permastructure for a ‘movie’ post_type consisted of example.com/movies/movie-name/, example.com/movies/ would just do a query against post_type=’movie’.

    To theme these pages though, you wouldn’t create a new theme called /movies/. Instead, you would add a single-movie.php to your current theme. So far, 3.0 doesn’t have post_type specific filters for all the page types yet, and I haven’t yet taken care of these in cms-press, so for now, you would need to add a filter to use a custom archive page for movies. I have a ticket setup to fill in the missing template_loads that I will hopefully include in the next release, http://github.com/voceconnect/cms-press/issues/issue/39.

    Not at the moment, but it will be implemented soon. I don’t have a timeline for this feature yet though.

    Ability to add meta box types defined (by plugin) to post types in the same way that you add taxonomies?

    This is in my future plans, but it probably won’t be included until WordPress 3.1 is out. My goal is to simplify the handling of meta boxes in WordPress so that they meta handlers will register with WordPress allowing other plugins to know there there. This will give CMS-Press the API to see what meta boxes are available to support.

    Ability to create meta box types through a separate form under CMSPress (which then could be added as above

    I haven’t completely decided yet. Once the meta box handling is improved in core, I’ll see how well other plugins out there that allow you to create custom meta boxes are using it to see if I need to add that to cms-press or just suggest to also add plugin X for building custom meta-boxes.

    The custom post type handling built into WordPress 3.0 doesn’t allow end users to create their own custom post types. It only makes it easier for developers to add custom post types via code. The cms-press plugin uses the functionality that is built into WP 3.0 (and extends what was in 2.9) to give end users the ability to create their own post types without having to write any code. This is fully compatible with WP 3.0.

    Version 1.0 with these fixes has been released.

Viewing 15 replies - 46 through 60 (of 62 total)