emt036

I’m running WP 2.0.3 with PHP 5.0.2 on Apache 1.3.34 with no problems…

Hmm, odd. I’ve made a few changes to WP and Viewlevels, but I don’t think either would cause mine to work, and yours not. The only thing I added in page.php was:

<?php if(function_exists('vl_restricted'))vl_restricted(); ?>

to show the little lock icon on protected pages. And the only thing I added to viewlevels.php was some code to hide “Email to a Friend” and “Print” links on protected pages.

I currently use ViewLevel 2.1.0 from https://blog.firetree.net/2005/08/25/viewlevel-20/ and WP 2.0.2 (though I also did have it running on 1.5.2). I am not sure I 100% understand you, but if you want to prevent pages from being displayed to someone with a viewlevel less than you specify, it is possible.

Unfortunately, I don’t believe the vl=1 method works for pages. Instead, under the “Write Page” screen for the post that you want to protect/prevent unauthorized viewing:
1) Scroll down to “Custom Fields” (hit the + to expand it if need be).
2) Under “Add a New Custom Field,” type viewlevel in the key box, and your desired viewlevel (i.e. 1,2,3,etc.) into the value box.
3) Press “Add Custom Field” button.

That’s it. Hope that helps.

Upgraded from WP-Email 2.02 to 2.03, which seems to work with WP2.0.2. Thanks!

Yup, did that. I’ll try downloading/reinstalling now that the download is back up. Thanks.

Yup, regenerated permalink, as well as re-uploaded all the WP-Email files. The Email Manager in the Admin panel comes up fine, but it seems to be the wp-email.php that is having the problems.

Anyone get this working on 2.0.2? My WP-Print seems to be working fine, but WP-Email only generates a blank page (i.e. https://www.subaquasternalrubs.com/archives/2006/03/14/wordpress-upgraded-to-202/email/)

I did not change my .htaccess or anything else, other than the core WP files.

You could also edit /wp-admin/menu.php so you could change the user level required to do certain things, i.e. change the user level for plugins.php to 9 so that your friend could not access it.

Yeah, I have had no problems except for the switch from DST and I got 60 800k emails….

Thanks jalenack, I have just started to use this plugin/hack. I too was wondering about cookie authentication along with the time out, as the IP checking could allow users to edit comments other than their own on home/corporate/educational networks. I know my school only has two WAN IP’s for the hundreds of computers on the student LAN. Same with home networks — only one WAN IP for however many computers on the LAN.

Perhaps a there is a way to integrate it with the WordPress user cookie?

Thanks a lot.

Did you try and delete/re-upload the offending file from a fresh WP install?

No categories, but you can have parent pages be the “categories,” and then organize child pages under them.

(Assuming you are working with the default theme:)

Delete wp-comments-post.php and wp-trackback.php in your root directory, and then delete comments.php and comments-popup.php in your theme directory.

Then, in the index.php in your theme directory delete:

<?php comments_popup_link('No Comments »', '1 Comment »', '% Comments »'); ?>

In the single.php of your theme directory, delete:

<?php if (('open' == $post-> comment_status) && ('open' == $post->ping_status)) { // Both Comments and Pings are open ?>
You can <a href="#respond">leave a response</a>, or <a href="<?php trackback_url(display); ?>">trackback</a> from your own site.

<?php } elseif (!('open' == $post-> comment_status) && ('open' == $post->ping_status)) {
// Only Pings are Open ?>
Responses are currently closed, but you can <a href="<?php trackback_url(display); ?> ">trackback</a> from your own site.


<?php } elseif (('open' == $post-> comment_status) && !('open' == $post->ping_status)) {
// Comments are open, Pings are not ?>
You can skip to the end and leave a response. Pinging is currently not allowed.


<?php } elseif (!('open' == $post-> comment_status) && !('open' == $post->ping_status)) {
// Neither Comments, nor Pings are open ?>
Both comments and pings are currently closed.

Also delete:
<?php comments_template(); ?>

That should be it.

True… you could use .htaccess to redirect everything to index.html, but that would be a pain.

You could also put up an index.html in your blog root explaining that the site is down for maintainence.. On most servers this takes precendece over index.php, so your visitors would see the html page. (Though if they manually typed in index.php, it would still work.)