WordPress.org

Ready to get started?Download WordPress

Forums

Widget Logic
widget logic not working - topic not closed! (5 posts)

  1. dianabyron
    Member
    Posted 2 years ago #

    I just installed and activated Widget Logic, latest version, for WP 3.3.1. The Codex instructions show you what to put in the Widget Logic bar in the simplest case, eg. default setup, homepage left as the blog, want the sidebar to show on only the homepage. I put in what they suggest: is_page('home') and the widget disappears off ALL pages.
    So I put in other people's various suggestions for example ones that start with if_is(home), etc and all I get is Parse Errors on top of the webpages and on the widget area.
    Where is there a real, useful, newbie, English (not coder) explanation of what to fill in the Widget Logic box? (and please not the WP codex page on Widget Logic because I've already explored it all and it does not tell me what I need to know.)
    thanks

    http://wordpress.org/extend/plugins/widget-logic/

  2. alanft
    Member
    Plugin Author

    Posted 2 years ago #

  3. squidz
    Member
    Posted 2 years ago #

    @diannetrussell --

    the answer for home page only is:

    is_front_page()

    Simple as that.

    Alan, why not just answer the support question when it's clear the person is having trouble and doesn't quite understand? Then point them to the spot where they can learn more. Answering a question with a question creates frustration with your widget's users.

  4. James Revillini
    Member
    Posted 2 years ago #

    I'm not completely sure, but I think when this thing was rewritten, perhaps a simple bit of code global post; was left out somewhere and so we lose what the global $post variable is and it causes a lot of expressions to return false when they should return true. I'm having similar issues to @diannetrussel but with a different, custom added plugin function called is_page_or_ancestor. I'll get back to everyone after some testing.

  5. James Revillini
    Member
    Posted 2 years ago #

    Nope. I was totally off. My issue seems to be somewhere in the is_page_or_ancestor function.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic