Yes, the Post Levels is a bit faster and ensures that posts aren't shown if the plugin is disabled; however, it doesn't work in WP 1.2
Fortes
· 4 years ago
Yes, the Post Levels is a bit faster and ensures that posts aren't shown if the plugin is disabled; however, it doesn't work in WP 1.2
Sine
· 4 years ago
I have tried to install this several times, each time I activate it all it does is show at the top of every page all the coding. It there somthing else that has to be done?
Sine
· 4 years ago
I have tried to install this several times, each time I activate it all it does is show at the top of every page all the coding. It there somthing else that has to be done?
Fortes
· 4 years ago
I've never seen the error, but here's a guess: Have you made renamed the file to post-level.php? You have to make sure there isn't an "s" at the end of the file extension.
If that's not the case, which version of WordPress are you using? This plugin doesn't work with version 1.2, but it shouldn't show the source code.
Fortes
· 4 years ago
I've never seen the error, but here's a guess: Have you made renamed the file to post-level.php? You have to make sure there isn't an "s" at the end of the file extension.
If that's not the case, which version of WordPress are you using? This plugin doesn't work with version 1.2, but it shouldn't show the source code.
Fortes
· 4 years ago
Nevermind, I found the issue -- saving the phps file directly actually gives you an HTML document [php's automatic source color coding]. You can either copy-paste the file contents, or re-download the plugin (I've removed the color coding).
Fortes
· 4 years ago
Nevermind, I found the issue -- saving the phps file directly actually gives you an HTML document [php's automatic source color coding]. You can either copy-paste the file contents, or re-download the plugin (I've removed the color coding).
Shelby
· 4 years ago
Are you working on getting the Archive / Category listing to show the posts? Also anyways to make protected posts SHOW they are protected eg. with the little padlock like "View Levels plugin" .. other than that sweet plugin thanks and keep up the good work
Shelby
· 4 years ago
Are you working on getting the Archive / Category listing to show the posts? Also anyways to make protected posts SHOW they are protected eg. with the little padlock like "View Levels plugin" .. other than that sweet plugin thanks and keep up the good work
Fortes
· 4 years ago
Unfortunately, Wordpress doesn't provide the right hooks to fix the Archive / Category listing, which makes it difficult to incorporate that within a plugin.
I'll add support for displaying a "private" icon in the next version of the plugin.
Fortes
· 4 years ago
Unfortunately, Wordpress doesn't provide the right hooks to fix the Archive / Category listing, which makes it difficult to incorporate that within a plugin.
I'll add support for displaying a "private" icon in the next version of the plugin.
Shelby
· 4 years ago
Man that sucks with Wordpress. And I will be looking forward to the next version, thanks again and keep up the good work.
Shelby
· 4 years ago
Man that sucks with Wordpress. And I will be looking forward to the next version, thanks again and keep up the good work.
Shelby
· 4 years ago
Man that sucks with Wordpress. And I will be looking forward to the next version, thanks again and keep up the good work.
Shelby
· 4 years ago
Man that sucks with Wordpress. And I will be looking forward to the next version, thanks again and keep up the good work.
iðunn
· 4 years ago
hello and thanks for releasing this into the wild ... however I've noticed that the entries that I've marked private and also set a post_level, these entries still appear on RSS-feed lists.. any idea how to fix that? :-)
iðunn
· 4 years ago
hello and thanks for releasing this into the wild ... however I've noticed that the entries that I've marked private and also set a post_level, these entries still appear on RSS-feed lists.. any idea how to fix that? :-)
Fortes
· 4 years ago
Actually, they only appear in the RSS feed if the feedreader you're using is either an in-browser one, or somehow uses your cookies. Try logging out of your browser (or using a different one) and visiting the feed URL, and you'll notice that the private posts are not shown.
Fortes
· 4 years ago
Actually, they only appear in the RSS feed if the feedreader you're using is either an in-browser one, or somehow uses your cookies. Try logging out of your browser (or using a different one) and visiting the feed URL, and you'll notice that the private posts are not shown.
iðunn
· 4 years ago
oops, I spoke to soon. the posts don't show up in the RSS feed if I do what I'm supposed to. I published my posts, instead of saving them as private.
Thanks again :-)
iðunn
· 4 years ago
oops, I spoke to soon. the posts don't show up in the RSS feed if I do what I'm supposed to. I published my posts, instead of saving them as private.
Thanks again :-)
Riff
· 4 years ago
Batch Categories 0.91 are not compatible when both installed and activated in WordPress v1.5 (final). I installed, activated and tested Post Levels first, and everything was fine. I installed Batch Categories next, and upon activation I got several PHP errors at the top of the Manage Plugins page itself, as well as every other page (have removed full path info from errors):
--- Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 6
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 7
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 8
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 9 ---
Errors stopped as soon as I deactivated Batch Categories and refreshed the page.
Would be extremely nice if you and the Batch Categories author could collaborate on a fix so both plugins will co-exist on one WP installation. Thanks!
Riff
· 4 years ago
Batch Categories 0.91 are not compatible when both installed and activated in WordPress v1.5 (final). I installed, activated and tested Post Levels first, and everything was fine. I installed Batch Categories next, and upon activation I got several PHP errors at the top of the Manage Plugins page itself, as well as every other page (have removed full path info from errors):
--- Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 6
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 7
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 8
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 9 ---
Errors stopped as soon as I deactivated Batch Categories and refreshed the page.
Would be extremely nice if you and the Batch Categories author could collaborate on a fix so both plugins will co-exist on one WP installation. Thanks!
Fortes
· 4 years ago
What you're describing is an issue with the Batch Categories plugin. You need to contact the author, there's nothing I can do about the error you're seeing (try using Batch Categories without Post Levels, and you'll see the same error).
Fortes
· 4 years ago
What you're describing is an issue with the Batch Categories plugin. You need to contact the author, there's nothing I can do about the error you're seeing (try using Batch Categories without Post Levels, and you'll see the same error).
Sine
· 4 years ago
Back again :) Ok I did what you suggested and it now longer shows the php code however now it bring this error up :(
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 6
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 7
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 8
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 9
Sine
· 4 years ago
Back again :) Ok I did what you suggested and it now longer shows the php code however now it bring this error up :(
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 6
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 7
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 8
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 9
Sine
· 4 years ago
aha worked it out !! Just had to remove spaces from the end of the php code
Sine
· 4 years ago
aha worked it out !! Just had to remove spaces from the end of the php code
Sine
· 4 years ago
Ok now its all installed but it shows the post even when I havethe level set high :( Wsa there another step I missed?
Sine
· 4 years ago
Ok now its all installed but it shows the post even when I havethe level set high :( Wsa there another step I missed?
Fortes
· 4 years ago
You have to make sure you've set the post status to Private (not Published).
Fortes
· 4 years ago
You have to make sure you've set the post status to Private (not Published).
Carla
· 4 years ago
Is there any way to make the user level option a little more friendly? I used a hack that had a drop down menu to establish the user level. Thanks. :)
Carla
· 4 years ago
Is there any way to make the user level option a little more friendly? I used a hack that had a drop down menu to establish the user level. Thanks. :)
is it possible that even though the post is private it pops up a comment post saying .. [normal post layout] this post is private please log in to view it ? [end]
giles
· 4 years ago
is it possible that even though the post is private it pops up a comment post saying .. [normal post layout] this post is private please log in to view it ? [end]
Lyanna
· 4 years ago
The sample PHP code for (private) works like a charm. What I would really like though, is to be able to display who can read what according to a certain level. What I mean is, that when I set a post to for instance post-level 2, it displays (Only Josh and Cindy can read this) and when I set a level 3, it displays (Only Josh can read this)
I've tried this with the is_post_level ($level) function, but it doesn't work. What I did is this:
if (function_exists('is_post_level($level)') && is_post_level('2')) : ?> (Only x and y can read this)
Where's the catch?
Lyanna
· 4 years ago
The sample PHP code for (private) works like a charm. What I would really like though, is to be able to display who can read what according to a certain level. What I mean is, that when I set a post to for instance post-level 2, it displays (Only Josh and Cindy can read this) and when I set a level 3, it displays (Only Josh can read this)
I've tried this with the is_post_level ($level) function, but it doesn't work. What I did is this:
if (function_exists('is_post_level($level)') && is_post_level('2')) : ?> (Only x and y can read this)
Where's the catch?
Fortes
· 4 years ago
Lyanna: The plug-in isn't set up to do what I think you're looking to do, because the plug-in works in such a way that private posts are never retrieved if the user doesn't have access to the post. This means you can't currently let the user know that there's a post they cannot see.
I'll add this type of functionality as a request for future versions.
Fortes
· 4 years ago
Lyanna: The plug-in isn't set up to do what I think you're looking to do, because the plug-in works in such a way that private posts are never retrieved if the user doesn't have access to the post. This means you can't currently let the user know that there's a post they cannot see.
I'll add this type of functionality as a request for future versions.
crash
· 4 years ago
hi fil. i'm glad someone is working on the "private-posts" front.
quick question: from a glance, it seems that the minimum "private" level for a post is 1. is there a way to make it 0, without breaking everything?
i want the least private of the private posts to be readable by registered users (user_level 0), without having to give them posting access (user_level 1+).
crash
· 4 years ago
hi fil. i'm glad someone is working on the "private-posts" front.
quick question: from a glance, it seems that the minimum "private" level for a post is 1. is there a way to make it 0, without breaking everything?
i want the least private of the private posts to be readable by registered users (user_level 0), without having to give them posting access (user_level 1+).
Daniel Drucker
· 4 years ago
In response to #25, the php function "function_exists" takes the NAME of a function only. So, your code should read:
if (function_exists('is_post_level') && is_post_level('2'))
Daniel Drucker
· 4 years ago
In response to #25, the php function "function_exists" takes the NAME of a function only. So, your code should read:
if (function_exists('is_post_level') && is_post_level('2'))
Ed Hidden
· 4 years ago
I have the plugin working fine. I love it. Thanks for putting forth the effort on this.
Do you know if there is a way to use a post_level of "2" by default? I'm building a wordpress site that I want the entire thing protected and would love to not have to remember to add a level of 2 to each post. (this will be used for a team that might not be diligent with the details of making sure all the posts are protected.)
(I have one post not protected that says, "You need to be logged in to see this stuff...")
Ed Hidden
· 4 years ago
I have the plugin working fine. I love it. Thanks for putting forth the effort on this.
Do you know if there is a way to use a post_level of "2" by default? I'm building a wordpress site that I want the entire thing protected and would love to not have to remember to add a level of 2 to each post. (this will be used for a team that might not be diligent with the details of making sure all the posts are protected.)
(I have one post not protected that says, "You need to be logged in to see this stuff...")
musyoka
· 4 years ago
perfect for my needs. Thank-you
musyoka
· 4 years ago
perfect for my needs. Thank-you
reagan
· 4 years ago
This is a great plugin! it seems that if the Post Status defaulted to Private & the Publish button was eliminated this would be foolproof. anyone have a hack for that? thanks!
reagan
· 4 years ago
This is a great plugin! it seems that if the Post Status defaulted to Private & the Publish button was eliminated this would be foolproof. anyone have a hack for that? thanks!
Love It! Just one thing...
· 4 years ago
I noticed that if a post is marked as Private, even when someone is logged in with the sufficient level to see the post, it is excluded from the Counts for the given category. Is this a bug in functionality, or inteded functionality as part of Private posts.
Additonally, is it possible to display (in red?) PRIVATE POST so those who have permissions to see it know that they are seeing someting special?
Love It! Just one thing...
· 4 years ago
I noticed that if a post is marked as Private, even when someone is logged in with the sufficient level to see the post, it is excluded from the Counts for the given category. Is this a bug in functionality, or inteded functionality as part of Private posts.
Additonally, is it possible to display (in red?) PRIVATE POST so those who have permissions to see it know that they are seeing someting special?
Ludwig
· 4 years ago
Hey, how can one make the post not private once it's private - Like publish it
Ludwig
· 4 years ago
Hey, how can one make the post not private once it's private - Like publish it
Hmmm. Perhaps I am one of the dim ones, but i have some questions: 1) How do I "Add a custom field"? and 2) how do I set the value of post_level to between 1 and 10? Also, after enabling the plug-in, I don't see a place to set post status to private. So 3) how do I set post status? (Should this be a menu option on the "Write" page, or is this also something that I need to change in the code?)
Thanks for any help.
washburn
· 4 years ago
Hmmm. Perhaps I am one of the dim ones, but i have some questions: 1) How do I "Add a custom field"? and 2) how do I set the value of post_level to between 1 and 10? Also, after enabling the plug-in, I don't see a place to set post status to private. So 3) how do I set post status? (Should this be a menu option on the "Write" page, or is this also something that I need to change in the code?)
Thanks for any help.
washburn
· 4 years ago
ok--figured it out. A drop down menu, like Skippy's User-Level Post plug-in had would be nice.
washburn
· 4 years ago
ok--figured it out. A drop down menu, like Skippy's User-Level Post plug-in had would be nice.
Sevenupcan
· 4 years ago
Thanks for your hard work on creating this plugin. I'm sure issues like the user interface will easily be solved in the next release. However I have one concerne.
Because posts on my site use the "custom fields" (metadata) for other information, for example I list key words related to that post using the custom fields. As you can probably figure out when you view the post the "post_view: 1" gets shown inside the meta data. And is shown on the post. Which is ugly and slightly confusing to those that don't know what it does.
Is there a quick way of solving this? I did think perhaps you could hide it using CSS, but there is no way of seperating it from the other metadata elements.
Thanks again.
Drew
· 4 years ago
I love this plugin! However I was wondering is there any way for a registered user with sufficient level to view my posts on my website to subscribe to my rss feed in a way that those posts are available? Thanks.
All Comments
http://www.furbona.org/viewlevel.html
http://www.furbona.org/viewlevel.html
If that's not the case, which version of WordPress are you using? This plugin doesn't work with version 1.2, but it shouldn't show the source code.
If that's not the case, which version of WordPress are you using? This plugin doesn't work with version 1.2, but it shouldn't show the source code.
I'll add support for displaying a "private" icon in the next version of the plugin.
I'll add support for displaying a "private" icon in the next version of the plugin.
Thanks again :-)
Thanks again :-)
---
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 6
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 7
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 8
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 9
---
Errors stopped as soon as I deactivated Batch Categories and refreshed the page.
Would be extremely nice if you and the Batch Categories author could collaborate on a fix so both plugins will co-exist on one WP installation. Thanks!
---
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 6
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 7
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 8
Warning: Cannot modify header information - headers already sent by (output started at /home/.[...]/wp-content/plugins/batch-access.php:11) in /home/.[...]/wp-admin/admin.php on line 9
---
Errors stopped as soon as I deactivated Batch Categories and refreshed the page.
Would be extremely nice if you and the Batch Categories author could collaborate on a fix so both plugins will co-exist on one WP installation. Thanks!
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 6
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 7
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 8
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 9
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 6
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 7
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 8
Warning: Cannot modify header information - headers already sent by (output started at /home/omiogazz/public_html/wp-content/plugins/post-levels.php:77) in /home/omiogazz/public_html/wp-admin/admin.php on line 9
(private)
...
(private)
...
[normal post layout]
this post is private please log in to view it ?
[end]
[normal post layout]
this post is private please log in to view it ?
[end]
I've tried this with the is_post_level ($level) function, but it doesn't work. What I did is this:
if (function_exists('is_post_level($level)') && is_post_level('2')) : ?>
(Only x and y can read this)
Where's the catch?
I've tried this with the is_post_level ($level) function, but it doesn't work. What I did is this:
if (function_exists('is_post_level($level)') && is_post_level('2')) : ?>
(Only x and y can read this)
Where's the catch?
I'll add this type of functionality as a request for future versions.
I'll add this type of functionality as a request for future versions.
quick question: from a glance, it seems that the minimum "private" level for a post is 1. is there a way to make it 0, without breaking everything?
i want the least private of the private posts to be readable by registered users (user_level 0), without having to give them posting access (user_level 1+).
quick question: from a glance, it seems that the minimum "private" level for a post is 1. is there a way to make it 0, without breaking everything?
i want the least private of the private posts to be readable by registered users (user_level 0), without having to give them posting access (user_level 1+).
if (function_exists('is_post_level') && is_post_level('2'))
if (function_exists('is_post_level') && is_post_level('2'))
Do you know if there is a way to use a post_level of "2" by default? I'm building a wordpress site that I want the entire thing protected and would love to not have to remember to add a level of 2 to each post. (this will be used for a team that might not be diligent with the details of making sure all the posts are protected.)
(I have one post not protected that says, "You need to be logged in to see this stuff...")
Do you know if there is a way to use a post_level of "2" by default? I'm building a wordpress site that I want the entire thing protected and would love to not have to remember to add a level of 2 to each post. (this will be used for a team that might not be diligent with the details of making sure all the posts are protected.)
(I have one post not protected that says, "You need to be logged in to see this stuff...")
Additonally, is it possible to display (in red?) PRIVATE POST so those who have permissions to see it know that they are seeing someting special?
Additonally, is it possible to display (in red?) PRIVATE POST so those who have permissions to see it know that they are seeing someting special?
Thanks for any help.
Thanks for any help.
Because posts on my site use the "custom fields" (metadata) for other information, for example I list key words related to that post using the custom fields. As you can probably figure out when you view the post the "post_view: 1" gets shown inside the meta data. And is shown on the post. Which is ugly and slightly confusing to those that don't know what it does.
Is there a quick way of solving this? I did think perhaps you could hide it using CSS, but there is no way of seperating it from the other metadata elements.
Thanks again.