Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • This is a feature, but doesn’t seem to be working..

    Plugin Author OneWebsite

    (@onewebsite)

    Glad you’re enjoying it!

    Did this get solved?

    I am using this to get variable sidebar content:

    <?php
    global $post;

    if (is_page() && $post->post_parent ) {
    include(‘sub-page.php’);
    } else {
    include(‘not-sub-page.php’);
    }
    ?>

    But this only helps me if the page is a sub_page.

    I want something exactly the same that works if the page is a parent

    Hey,

    So I want to have a conditional that includes a file if the page has children – not to display those children as discussed above. If the page does not have children I want to include a different file.

    So plain spoken program:

    If page is parent {

    include(file-for-parent-pages.php);

    } else {

    include(file-for-non-parent-pages.php);

    }

    Could someone please provide this snippet.

    I have tried this:

    <?php
    global $wp_query;

    if ( empty($wp_query->post->post_parent) )

    { include(‘side-parent.php’); }

    else

    { include(‘side-no-children.php’); }

    ?>

    THANKS!!!

    Thread Starter OneWebsite

    (@onewebsite)

    Sweet, thanks.

    I read the first link doc.

    I understand that if and when the 2.5.1 is updated I will run the switch command to update the files – although I am not sure why it is different here than the bleeding version when you use svn up.

    What happens when 2.5.1 goes to 2.5.2. I am assuming that the switch command would no longer be relevant? Or would I use the following, even if my current tag is 2.5.1:

    $ svn sw https://svn.automattic.com/wordpress/tags/2.5.2/

    Thread Starter OneWebsite

    (@onewebsite)

    Thank you,

    I will upgrade my old versions.

    Is there an svn repo for 2.5.1 to pull revisions from or must updates be done manually?

    Thread Starter OneWebsite

    (@onewebsite)

    Moshu,

    I do get that very well thanks.

    Can you define safe?

    You see I have lots of software, and most of it is old. I don’t always upgrade to the latest version, as I am sure you do as well (unless you have deep pockets).

    Are you suggesting that every client I have installed wordpress 2.1 for must – absolutely must be upgraded?

    I understand that WordPress is not a desktop application and is susceptible to threats that Photoshop isn’t and therefore there isn’t a critical need to upgrade to CS3 except for feature and to make Adobe richer.

    Thread Starter OneWebsite

    (@onewebsite)

    Thanks Otto.

    I am installing WordPress for clients and clearly I need to decide which version to install. Each have features and limitations. Some plugins that have been developed for 2.1 only work on 2.1 and so if I begin to use 2.5 I will need to retool those plugins.

    Taking into consideration feature set, plugins available and security are 2.1 or 2.3 worthwhile or should the be permanently abandoned for 2.5.

    More than one person has expressed their devotion to legacy versions.

    I understand it is as much as anything preference, but that is what I am looking for, experienced opinions.

    Thanks again.

    Thread Starter OneWebsite

    (@onewebsite)

    What is confusing is that there is a line of product in between 2.0.11 and 2.5.1 and generally speaking most software lines do have massive gaps in stable production. One could assume that the latest in line of 2.1 would be better than 2.0

    And please spare me the righteous indignation. 3 more sentences in the description would clarify a very brief disclaimer that carries substantial weight. The semantics of safe is open to interpretation. Does that mean all hackers world wide will assemble to destroy your content if you dare install version 2.3. Will the server implode on installation?

    Please don’t bother helping people if you do it with contempt.

Viewing 9 replies - 1 through 9 (of 9 total)