Forum Replies Created

Viewing 15 replies - 286 through 300 (of 350 total)
  • You don’t say how you built the navigation …

    If you use wp_list_pages, it will wrap the current page’s list item like so:
    <li class="page_item current_page_item"><a ...>Page X</a></li>
    and you can use CSS to define the style associated with current_page_item.

    See wp_list_pages for additional information.

    The plugin Category Order (scroll to the bottom of the page) works for me.

    Found this while I was looking up something else. Just in case the question hits home with anyone …

    The way I do this is using the Category Access plugin – See http://www.coppit.org/code/

    — protects posts and categories according to individual permissions.

    I’m not quite sure what you mean by “it’s own single.php” – but customizing that should be straightforward.

    And if you do *want* the comments to be found by the search, check out the search everything plugin

    I’ve got a similar situation. Each month, I get a file with information about the organization’s current members. I upload that to WordPress giving each member a WordPress login and password based on their member id. These logins have limited permissions – they can be used to view “member only” content, but cannot post or comment. [If they want to contribute to the site, there’s a way they can apply for an account with more privileges.]

    We get a membership list each month. I’d like to delete all the members of this type and reload them from the new file. If they can access their profile page and change their passwords, their changes will be wiped out with the next upload.

    We can try to handle this through training, but with a relatively large population, this isn’t working well. Is there a way to create these users with a capability that would hide the profile page?

    The thread here has a suggestion on changing menu.php — but I don’t want to hide the page for everyone — just the folks who aren’t active contributors.

    I’m running role manager, but don’t know how I’d put the hooks in to check the capability to see the profile.

    Any suggestions? [My problem’s with WP 2.2, if that makes a difference.]

    converting2wp

    (@converting2wp)

    While looking for something else, I found a link to
    BDP RSS Aggregator listed on the 2.2 Compatible Plugins page.

    converting2wp

    (@converting2wp)

    You may no longer need this answer, but Category Access 0.8.0 is working for me on WordPress 2.1.3. I also installed RoleManager, but I don’t think it’s required.

    converting2wp

    (@converting2wp)

    What did you upgrade from?

    Is this the same issue as in “WYSIWYG editor losing HTML on 2.1“?

    converting2wp

    (@converting2wp)

    Interesting question.

    In the case of posts in a given category, it’s possible to use the previous_post_link() (and the corresponding next_post_link()) setting the in_same_cat parameter to TRUE to get behavior similar to what you’re describing.

    For a single “page” that has page breaks inserted with <!--nextpage-->, Styling Page-Links has some suggestions, but it sounds as if that’s not what you want, either.

    If I understand the question, what you’ve got is a page hierarchy set up using the Page Parent and Page Order drop downs on the Edit Page panel, and you want to navigate from one page to the next.

    Code I’ve used for a similar application (showing the child/sibling pages in the sidebar) is posted at pastebin. It’d need significant change to do what you want, but I’d think the building blocks would be the same.

    On the other hand, if someone’s got a good answer to your question, I’d expect I’d be able to use that to improve my strategy.

    Thread Starter converting2wp

    (@converting2wp)

    Okay, cancel all of that – apologies for taking the space.

    Of course, it’s the address in the post_content that needs to change — and so the Search and Replace plugin very well might be the right solution.

    My mass edit of the SQL file worked, but the change to the guid field was irrelevant. It was the change to the post_content that made the difference.

    The only problem I’ve found with leaving the guid unchanged comes when trying to reuse the old files in a new post. The uploader (in v 2.0.7) does use the guid field to find the file.

    converting2wp

    (@converting2wp)

    This should do what you’re asking —

    $parent_title = get_the_title($post->post_parent);
    echo $parent_title;

    To find out if a page is top-level check to see if $post->post_parent is 0.

    converting2wp

    (@converting2wp)

    What you probably want to investigate is how to “repost” an RSS feed from one blog as a set of headlines or posts on another.

    For instance if your MySpace blog has the RSS feed:

    http://blog.myspace.com/blog/rss.cfm?friendID=yourid

    then you can use the RSS widget or one of the RSS plugins (I use feedlist) configured with that address to put the MySpace headlines (+/- the excerpt) on your WordPress site.

    I’m not sure what it would take to go the other way — you may need to check for the help at MySpace — but the WordPress feeds are configurable. See WordPress Feeds and Customizing Feeds in the Codex to get started.

    Thread Starter converting2wp

    (@converting2wp)

    Moshu – thanks (as always!) – but your link above points to a search on all support topics referencing guid, and I’m not sure I’ve picked out the right ones.

    My case is similar to the discussion of “moving a site from test to production” (see this post on the hackers list) that’s from a hackers thread referenced by HandySolo this support discussion

    In addition, I’m specifically concerned about the address of uploaded files. In this support discussion, Kafakaesqui says

    With that said, there is the issue of file attachments (images or other files uploaded through the post editor), which *can* run into problems due to the guid. I have a plugin that relies on it, and have been thinking through a possible tool to update the field.

    I guess I understand that the guid is an ID, not an address, though I’ll still probably change it when moving from development to production. As for the issue of the path to uploaded files, I’ll look at that again.

    Thanks!

    Thread Starter converting2wp

    (@converting2wp)

    From the docs, the Search and Replace plugin doesn’t actually seem to help here — since the bits I want to change are in a database field that it doesn’t seem to reference. I suppose it wouldn’t be hard to hack the plugin to look at the guid field as well, but since this all came up because of a move of the WordPress files from one place to another in the directory tree, I solved the problem this way:

    0) Ensure no one’s accessing the system.
    1) Export the database to SQL before(checking the “Add Drop Table” option)
    2) Edit the SQL directly to change all the old path names to new
    3) Import the modified SQL.

    converting2wp

    (@converting2wp)

    Please add my vote for a fix — and see also the Ideas section — the first page of the Popular list has

    • Access to TinyMCE Plugins and Options
    • Choose a better WYSIWYG editor
    • and, Let us force a line break

    all marked “under consideration”.

    Thanks, all, for WordPress — but access to the HTML in the pages/posts does seem important to many.

    Forum: Fixing WordPress
    In reply to: Pages Links
    converting2wp

    (@converting2wp)

    Ref: WP 2.1.3

    If you’re talking about pages, not posts, and so the “category” discussion is irrelevant, here’s my suggestion.

    Arrange the pages in a hierarchy using the “page parent” selection on the “edit page” screen.

    Once the hierarchy is set, the template tag wp_list_pages
    will give you lists to the depth required. You’ll need some technology to show/hide the lists of child pages (probably CSS and JavaScript). I’ll let someone else comment on that.

    If you’re going to link from one page to another, and you’re using permalinks, remember to always refer to a page’s address with the trailing slash, e.g.
    htref=”/parent/child/detail/”, not “/parent/child/detail” and if you’re linking from one place in the hierarchy to another, I’ve found it easier to come up with the right link if you think of the address of the page as, for instance, /parent/child/detail/index.htm. So, for instance, on the page “child” a link to “detail” will be href=”detail/” and from “detail” to “child” will be href=”../” — not surprising. However, if you have
    parent/child/detail-one/
    parent/child/detail-two/

    the link on page “detail-one/” to “detail-two/” will need to be coded as “../detail-two/”, not “detail-two/”. To see this add the (invisible) “index.htm” to the end of each path — then it’s clear you need the “..” to get to “child” before descending to the “detail-two” directory.

    So there’s the reason for always adding the slash to the end of the address. If you don’t, while the page will come up fine, all the relative links will be off and so will fail.

    Again, WordPress functions like wp_list_pages will do this for you, but if you need to put links into the content of the page “by hand” (as you might if you’re using WordPress as a CMS), be sure to remember this.

    [Sorry to go on so long. Hope this helps someone from spinning as many wheels as I’ve done today.]

Viewing 15 replies - 286 through 300 (of 350 total)