DISQUS

Thanks for the link. :)

I use a couple of plugins with my sideblog. Sideblog Wordpress Plugin 3.8 does the heavy lifting to separate those mini entries from my "regular" posts. I use Auto Tweet (a plugin of my own) to send those posts to Twitter as updates.

@Janus - I'm using Post Levels 1.1.1 with WP 2.1.3 and I'm having no problems.

See, this is my goal. One day I hope to make plugins so cool they elicit marriage proposals.

After further investigation, I've found that it's not Post Levels that's changed, but rather WordPress. In 2.0.x, a private post would be visible only to the post author (without any plugins, I mean). In 2.1, private posts are always visible to all Editors and Administrators.

They are visible under Manage - Posts (wp-admin/edit.php).

The post total under Users - Authors and Users (wp-admin/users.php) reveals only public posts. That is, if there are six posts, but only one of them is public the Actions column will list "View 1 post." However, if you click that link you're back to Manage - Posts (ex. wp-admin/edit.php?author=4) where all posts are again visible.

I've found a minor issue with this version. Users at a WordPress level of Administrator are able to see all posts, even if those posts belong to another user (even another Administrator user) and those posts have a higher Post Level than their user Post Level.

Example: Administrator #1 has a Post Levels user level of 5. Administrator #2 writes a post assigned Post Level 10. Administrator #1 can see that post.

Is this a bug, or is this by design?

I'm using WordPress 2.1.1 and Post Levels 1.1.1. This behavior did not occur with WP 2.0.x/PL 1.0.

So far, so good. At first glance all my problems have been resolved. Thank you!

I'm still having issues with this. :-/ Pages listed via wp_list_pages are duplicated for me on one blog, but not the other (not sure why that should be). And while the output of the loop doesn't have duplicate content, recent posts listed in the sidebar via either of two custom functions (one using a mini-loop that outputs only titles and permalinks, the other using a custom SELECT) will have duplicates. Also, there may be some kind of conflict with Ultimate Tag Warrior. Post Levels 1.1b2 causes a recent tag list called through UTW 3.14159265 to produce an SQL syntax error. I don't know if this should be "blamed" on the newest version of Post Levels or the newest version of UTW. This message went away on its own on one blog, but persists on the other. I won't paste the message here, as it's a little long, but I can send it to you if you wish.

Is there anything I can do to help out with development? I'm not much of a coder, but perhaps I can at least help you test builds?

Ah, cool. I'm glad I'm not getting left behind. I swapped stripos() for strpos() and the plugin works the way I would expect. Unfortunately, I can't use it right now. I'm having a few other issues I don't think are at all related to Post Levels.

Ah, ok.

I'll check back now and again to see if you've decided to release that code. :)

What's the deal with that standard/conversation view? I've been thinking about how to implement something exactly like that. Is that a plugin?