Private Entries

This is absolutely planned.

?? Glad to hear that it’s planned as it’s one of the few things that pMachine offers, that b2 doesn’t.

i would love to see a feature like this too. would save me a lot of (planned) work-arounds…

When I get some spare time tonight, I’m going to try implementing a hack that Michel suggested – see
https://www.tidakada.com/board/viewtopic.php?t=1560&postdays=0&postorde r=asc&highlight=password%20protect&start=0
I’ll let you know if I can get it working on my site or if I run into any probs. From the looks of it I can’t see why it wouldn’t work.
Cheers,
BC

Let us know how it goes.

The reason that won’t work is I run .RSS and there is a way to see not only the title but the entire blog entry in any .RSS form. I would love to have something secure like pMachine offers.

Yeah, I realised that afterwards… I don’t think it would be that hard to hack a function together to block RSS for certain posts, but since I’m still re-learning PHP someone else will have to do it… ??

A protected entry feature will possibly make the next version.

How about a protected category feature? Or category for registered users with rank higher than x?

I agree with “Anonymous” ?? . WordPress already has an excellent user system. If the user levels could be utilized so taht only users above level X can view these posts, it would give personal blogs much more control..
It’s # 1 on my “Please.. Please.. incorporate this into WP” list ??

ViewLevel v.1.1.2 Plugin for WordPress 1.2
https://www.furbona.org/viewlevel.html

@avtmx: I installed your viewlevel.php plugin. Nice work! But I couldn’t see the downloaded “padlock.gif” because the path was wrong.
It said “https://url.com/wp-images/padlock.gif” but should say “https://url.com/wordpress/wp-images/padlock.gif”
So I hacked a little and changed the following line in viewlevel.php:

$text='<img src=\''.$site_root.'/wp-images/'.$padlock_filename.'\' border=\'0\'/>'.$leveltext.$text;

to

$text='<img src=\'wp-images/'.$padlock_filename.'\' border=\'0\'/>'.$leveltext.$text;

Now it seems to work, although I’m not sure if it works also for installations with paths differently configured.