Forum Replies Created

Viewing 5 replies - 346 through 350 (of 350 total)
  • Just to clarify. On a new installation (of v2.0.1) there is no “Key dropdown menu”. Putting “_wp_page_template” in the “Key” textbox and something in the “Value” text area, and hitting the “Add Custom Field Button” will cause the drop down box to appear with “_wp_page_template” as a choice.

    However, while that was my first attempt, I really don’t think that’s enough information to get Custom Fields working (they don’t appear in the Key/Value/Action table on the page editing screen), and it’s not the answer to the question here. [And since I don’t need Custom Fields for anything else at the moment, I’ll ignore that problem.]

    THIS question, as I understand it, is how to get the page template menu to appear (on the right hand side of the page editing screen). The answer is relatively simple. Create a new template, my_template_name.php, in the theme directory AND be sure it has the following lines at the top:

    <?php
    /*
    Template Name: My Template Name
    */
    ?>

    The documentation IS clear, see
    http://codex.ww.wp.xz.cn/Pages
    but may not be “heard” correctly by those who are new to the whole process.

    See also
    http://ww.wp.xz.cn/support/topic/52511

    Thread Starter converting2wp

    (@converting2wp)

    Thanks, podz. That does seem to speed things up significantly.

    I’m seeing similar problems on a clean install.

    See http://ww.wp.xz.cn/support/topic/61593

    After some time searching, I have found some leads:

    PostRestriction Plugin – http://soeren-weber.net/post/2006/01/01/121/#restrict; as of 2/14/06 is not WP 2.01 compatible. Would also be awkward to have to set the restriction on *every* post.

    PrivateCategories Plugin – http://gregelin.com/archives/?page_id=2 ; seems to make the entire category “private” but that means its only accessible to the author. I don’t see that it supports (or plans to support) per-user access.

    UserExtra – http://log.squish.net/2005/09/20/usermeta-userextra/ which extends user profiles to include admin-defined attributes, and provides for category access controls with user-level granularity. [Released for 2.0 on 2/5/06,
    http://log.squish.net/2006/02/05/userextra-goes-wp20/
    with a correction on 2/12. This may be very close to what I’m looking for, though there are a few quibbles listed in the discussion of the version for WP 1.x.]

    On the other hand, I haven’t found any reference that talks about restricting access to pages, and restricting access to uploaded files seems entirely outside the scope of this discussion (and I can’t see how WordPress could control that). So I may end up needing some combination of WordPress and .htaccess files after all.

    Apologies for rambling in public.

    Okay, I’m not quite sure what all the features that v2 and the new authentication scheme provide. But the site I’m converting does have a (smallish) member-only section that in the current version is protected by a user name/password scheme managed with .htaccess/.htpasswd files — and a good way to “password protect an entire category” (as was the question in this post) would be exactly the behavior the users are accustomed to.

    However, I’m wondering if since this question was originally asked, the available solutions have changed.

    Is there any advice on what path to take as I move that section, in particular, to WordPress? Specifically, is there a “show this category only if user level is subscriber” functionality already in the system somewhere? Should I wait for additional user-level plugins to be released? Or is there something else that I’m missing entirely. All suggestions are welcome.

    Thanks.

Viewing 5 replies - 346 through 350 (of 350 total)