Widget Visibility – When Do We Get That?

WordPress.com users now have a feature available to them that should have been in the core of WordPress a long time ago. They call it, Widget Visibility. Users can either hide or show widgets based on category, author, tag, date, or page. This covers the most common use cases without having a need to use conditional tags.

Widget Visibility

The interface is surprisingly simple. In fact, I prefer what WordPress.com is using versus Widget Logic which requires me to know conditional tags. I’m wondering how did WordPress.com get this feature before stand-alone WordPress? When I asked this question on Twitter, Ian Stewart responded with:

@wptavern I’d look for it here http://jetpack.me/ :)

This makes sense and in fact would allow the Jetpack team to get valuable feedback before ever considering putting it into core. If you can’t wait that long, try out the Widget Context plugin. Widget Context provides a similar interface with a few more bells and whistles that the WordPress.com variety doesn’t have.

8 Comments


  1. The advantage of widget logic (for developers) is that you can write custom boolean functions and then call them from widget logic. I’ve accomplished some pretty nifty things with this approach.

    Report


  2. @Josh – the downside is that there’s no security consideration in Widget Logic–it simply runs eval() on whatever is entered in the conditional field for the widget. Widget Visibility may be more limited for advanced developers, but it doesn’t provide a ready opportunity for arbitrary code execution.

    Report



  3. which is better in terms of usage and performance widget logic or widget context? I don’t use jetpack so I’m choosing between the two.

    Report


    1. Widget logic is bare bones but you’ll need to know how WordPress conditional statements work in order to use it.

      Report

Comments are closed.