1. Steve Taylor

    Thanks! I created my own hack for this (involving custom fields – not ideal). I thought I might shift to using your Members Role Levels plugin, as Members is baked into everything I do anyway.

    But now this! Have to say, you must be the first plugin author to post a free alternate solution to an issue so soon after releasing your first commercial plugin that solves the same issue 🙂

    Are there any differences here? I’m most interested in future-compatibility. Presumably sites using either Members Role Levels plugin or this code would be fine whatever is eventually used in core? I guess it’s all just interface stuff, with a single user ID stored in the data.

    • Justin Tadlock

      Members – Role Levels works with the current core WordPress method for handling this. The core method relies on a feature that core itself deprecated in version 2.1 (yes, 2.1), which is the user levels system.

      The one major difference is that the post author drop-down fix is more of a byproduct of the plugin. Really, it allows you to assign the old, deprecated user levels. It’s just that the only issue with user levels in core just so happens to be the post author drop-down. However, it could potentially solve issues with other plugins if they’re still relying user levels for whatever reason.

      The method in this tutorial is the direction I’d like to see core go into in the future. It’s an actual long-term fix for the post author drop-down. To me, this is the ideal method for handling things. This method, if it made it into the core code, would actually make Members – Role Levels and any user levels obsolete.

      Both methods would essentially accomplish the same goal. Both are forward-compatible. Like you said, it’s really just changing the interface as far as the average end user is concerned.

Comments are closed.