1 morrighu Feb 09, 2008 18:12
3 morrighu Mar 18, 2008 22:09
That works for now, but now the entire b2evo is set to default to protected. I hate to do that because some of the authors don't mind publishing their stuff for the public and I'd like to see them be able to set their default to Publish instead of going to the extra step of publishing it.
I'd really like to see this become a per blog and not a per engine feature.
4 amoun Apr 15, 2008 10:45
Hi Morrighu and EdB.
Just an idea.
I thought or am thinking about how the skins work.
Doesn't it or shouldn't it work in such a way that any file in the skin will override any file in the main install. That way the above hack you suggested EbB would work if the file was out in a config folder in the skin(s) wanted.
Morrighu
A solution for a specific blog could be to protect it so that only members to it can view it. Then all the posts can stay public.
To do this in version 2.4.1
1. open inc/_main.inc.php
2. around line 360 find
if( !isset($login_required) )
{
$login_required = false;
}
3. replace with
if( $blog == "2")
{
$login_required = true;
}
else{$login_required = false;}
where the number is the number of the blog you wish to protect.
It will still show up on the public list and you can set permissions so that only registered members allocated permissions can view the blog and they will have to log in etc.
EdB I'm sure helped me with this some weeks ago when I first came across evo.
All the best
Amoun
Check out conf/_admin.php around line 101 (in v2.4.0) and set the default to 'protected'.