You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@roller.apache.org by Thinkboy <ma...@gmail.com> on 2007/11/21 11:47:44 UTC
can i set password to protect a particular blog entry ?
hi,
I am thinking how to set a certain blog as private , then whoever
trying to view this entry will be authenticated.
of course, i am not referring the servlet security spec.
how about a tag / or extra column for weblog entry. when we view a
page , set a pointcut to verify this special tag,
and protect this by acegi .
~thinkboy.
Re: can i set password to protect a particular blog entry ?
Posted by Dave <sn...@gmail.com>.
On Nov 28, 2007 10:24 AM, Thinkboy <ma...@gmail.com> wrote:
> On 2007-11-26 22:44:57 +0800, Dave <sn...@gmail.com> said:
>
> > On Nov 21, 2007 5:47 AM, Thinkboy <ma...@gmail.com> wrote:
> >> I am thinking how to set a certain blog as private , then whoever
> >> trying to view this entry will be authenticated.
> >
> > What if weblog posts had the following levels of privacy:
> >
> > - Private: only members of the blog can see the entry
> > - Protected: only logged in Roller users can see the entry
> > - Public: everybody (including anonymous visitors) can see the entry
> >
> > Would that be sufficient?
>
> yes, this is exactly what I am thinking too (private, protected,
> public) . i believe, it is a great feature!
>
> very appreciated that roller community does consider this in the near
> future release. COOL! . :-D
Despite the fact that I just spent a month or more reworking Roller's
user/permissions management system (http://tinyurl.com/28br55 is now
in trunk), I don't have an immediate requirement for private/protected
weblogs or weblog entries and I don't think any of the other
contributors do either. I *do* think these are important features,
but I just don't have a requirement for them right now.
So, if you really want protected/private blog posts, you might have to
push pretty hard for it, i.e. look at the source code, understand the
permission system, propose & discuss some solution(s) and if that goes
well develop a patch.
- Dave
Re: can i set password to protect a particular blog entry ?
Posted by Thinkboy <ma...@gmail.com>.
On 2007-11-26 22:44:57 +0800, Dave <sn...@gmail.com> said:
> On Nov 21, 2007 5:47 AM, Thinkboy <ma...@gmail.com> wrote:
>> I am thinking how to set a certain blog as private , then whoever
>> trying to view this entry will be authenticated.
>
> What if weblog posts had the following levels of privacy:
>
> - Private: only members of the blog can see the entry
> - Protected: only logged in Roller users can see the entry
> - Public: everybody (including anonymous visitors) can see the entry
>
> Would that be sufficient?
yes, this is exactly what I am thinking too (private, protected,
public) . i believe, it is a great feature!
very appreciated that roller community does consider this in the near
future release. COOL! . :-D
>
>
>> of course, i am not referring the servlet security spec.
>> how about a tag / or extra column for weblog entry. when we view a
>> page , set a pointcut to verify this special tag,
>> and protect this by acegi .
>
> We don't do any AOP in Roller, so point-cut is out. And we don't want
> to depend directly on Acegi because Roller should also be able to work
> with Container Manager Authentication (CMA) too.
>
> I think we could implement the levels of privacy above using the
> Roller 4.1 permission system, plus one additional field on each entry.
> However, the implications on caching and feeds could make things a
> little complex. We'd need to think through those issues very
> carefully.
>
> Discussions like this should probably happen on the dev list.
>
> - Dave
Re: Roller under JDK 1.5 and Tomcat 4.1.34
Posted by Matt Raible <ma...@raibledesigns.com>.
Have you looked in $CATALINA_HOME/logs/roller.log? If it fails to
start, you might look in $CATALINA_HOME/logs/localhost*.log.
I haven't run Roller on 4.1 for many years, so I don't know if it'll
work.
Matt
On Nov 27, 2007, at 10:49 AM, Prabhu Patil wrote:
> Matt,
> Sorry, I do not see any logs generated when I try running Roller under
> Tomcat 4.1.34. I'm curious how your trial went.
>
> Thanks
>
> -----Original Message-----
> From: Matt Raible [mailto:matt@raibledesigns.com]
> Sent: Monday, November 26, 2007 3:44 PM
> To: user@roller.apache.org
> Subject: Re: Roller under JDK 1.5 and Tomcat 4.1.34
>
> I would try it and see if it works - if it doesn't, send us the
> errors you're seeing in your logs.
>
> Matt
>
> On Nov 26, 2007, at 2:41 PM, Prabhu Patil wrote:
>
>> Hi Matt,
>>
>> We are integrating the blog functionality with a website which is
>> already running under Tomcat 4.1.x and jdk 1.5.x. It's not possible
>> for
>> us to upgrade this website now. That's the reason why I'm trying to
>> make
>> Roller 3.1 work in this environment.
>>
>> Or the other option I'm considering is to look for an older
>> version of
>> Roller that might work under this environment.
>>
>> Please let me know if you can throw some light on this.
>>
>> Thanks,
>>
>> -----Original Message-----
>> From: Matt Raible [mailto:mraible@mac.com]
>> Sent: Monday, November 26, 2007 3:14 PM
>> To: user@roller.apache.org
>> Subject: Re: Roller under JDK 1.5 and Tomcat 4.1.34
>>
>> Just curious - why do you want to use Tomcat 4.1 when 5.0, 5.5 and
>> 6.0 are out?
>>
>> Matt
>>
>> On Nov 26, 2007, at 1:41 PM, Prabhu Patil wrote:
>>
>>> All,
>>> Is it possible to run Roller 3.1 under JDK 1.5 & Tomcat 4.1.34? The
>>> installation guide mentions Tomcat 5.x as the recommended version
>>> of the
>>> server. However, it does also say any container complaint with
>>> servlet
>>> spec 2.3 will work.
>>>
>>> I'm trying to get Roller 3.1 working under JDK 1.5 & Tomcat 4.1.34
>>> with
>>> no results.
>>>
>>> -Thanks
RE: Roller under JDK 1.5 and Tomcat 4.1.34
Posted by Prabhu Patil <pp...@digitas.com>.
Matt,
Sorry, I do not see any logs generated when I try running Roller under
Tomcat 4.1.34. I'm curious how your trial went.
Thanks
-----Original Message-----
From: Matt Raible [mailto:matt@raibledesigns.com]
Sent: Monday, November 26, 2007 3:44 PM
To: user@roller.apache.org
Subject: Re: Roller under JDK 1.5 and Tomcat 4.1.34
I would try it and see if it works - if it doesn't, send us the
errors you're seeing in your logs.
Matt
On Nov 26, 2007, at 2:41 PM, Prabhu Patil wrote:
> Hi Matt,
>
> We are integrating the blog functionality with a website which is
> already running under Tomcat 4.1.x and jdk 1.5.x. It's not possible
> for
> us to upgrade this website now. That's the reason why I'm trying to
> make
> Roller 3.1 work in this environment.
>
> Or the other option I'm considering is to look for an older version of
> Roller that might work under this environment.
>
> Please let me know if you can throw some light on this.
>
> Thanks,
>
> -----Original Message-----
> From: Matt Raible [mailto:mraible@mac.com]
> Sent: Monday, November 26, 2007 3:14 PM
> To: user@roller.apache.org
> Subject: Re: Roller under JDK 1.5 and Tomcat 4.1.34
>
> Just curious - why do you want to use Tomcat 4.1 when 5.0, 5.5 and
> 6.0 are out?
>
> Matt
>
> On Nov 26, 2007, at 1:41 PM, Prabhu Patil wrote:
>
>> All,
>> Is it possible to run Roller 3.1 under JDK 1.5 & Tomcat 4.1.34? The
>> installation guide mentions Tomcat 5.x as the recommended version
>> of the
>> server. However, it does also say any container complaint with
>> servlet
>> spec 2.3 will work.
>>
>> I'm trying to get Roller 3.1 working under JDK 1.5 & Tomcat 4.1.34
>> with
>> no results.
>>
>> -Thanks
Re: Roller under JDK 1.5 and Tomcat 4.1.34
Posted by Matt Raible <ma...@raibledesigns.com>.
I would try it and see if it works - if it doesn't, send us the
errors you're seeing in your logs.
Matt
On Nov 26, 2007, at 2:41 PM, Prabhu Patil wrote:
> Hi Matt,
>
> We are integrating the blog functionality with a website which is
> already running under Tomcat 4.1.x and jdk 1.5.x. It's not possible
> for
> us to upgrade this website now. That's the reason why I'm trying to
> make
> Roller 3.1 work in this environment.
>
> Or the other option I'm considering is to look for an older version of
> Roller that might work under this environment.
>
> Please let me know if you can throw some light on this.
>
> Thanks,
>
> -----Original Message-----
> From: Matt Raible [mailto:mraible@mac.com]
> Sent: Monday, November 26, 2007 3:14 PM
> To: user@roller.apache.org
> Subject: Re: Roller under JDK 1.5 and Tomcat 4.1.34
>
> Just curious - why do you want to use Tomcat 4.1 when 5.0, 5.5 and
> 6.0 are out?
>
> Matt
>
> On Nov 26, 2007, at 1:41 PM, Prabhu Patil wrote:
>
>> All,
>> Is it possible to run Roller 3.1 under JDK 1.5 & Tomcat 4.1.34? The
>> installation guide mentions Tomcat 5.x as the recommended version
>> of the
>> server. However, it does also say any container complaint with
>> servlet
>> spec 2.3 will work.
>>
>> I'm trying to get Roller 3.1 working under JDK 1.5 & Tomcat 4.1.34
>> with
>> no results.
>>
>> -Thanks
RE: Roller under JDK 1.5 and Tomcat 4.1.34
Posted by Prabhu Patil <pp...@digitas.com>.
Hi Matt,
We are integrating the blog functionality with a website which is
already running under Tomcat 4.1.x and jdk 1.5.x. It's not possible for
us to upgrade this website now. That's the reason why I'm trying to make
Roller 3.1 work in this environment.
Or the other option I'm considering is to look for an older version of
Roller that might work under this environment.
Please let me know if you can throw some light on this.
Thanks,
-----Original Message-----
From: Matt Raible [mailto:mraible@mac.com]
Sent: Monday, November 26, 2007 3:14 PM
To: user@roller.apache.org
Subject: Re: Roller under JDK 1.5 and Tomcat 4.1.34
Just curious - why do you want to use Tomcat 4.1 when 5.0, 5.5 and
6.0 are out?
Matt
On Nov 26, 2007, at 1:41 PM, Prabhu Patil wrote:
> All,
> Is it possible to run Roller 3.1 under JDK 1.5 & Tomcat 4.1.34? The
> installation guide mentions Tomcat 5.x as the recommended version
> of the
> server. However, it does also say any container complaint with servlet
> spec 2.3 will work.
>
> I'm trying to get Roller 3.1 working under JDK 1.5 & Tomcat 4.1.34
> with
> no results.
>
> -Thanks
Re: Roller under JDK 1.5 and Tomcat 4.1.34
Posted by Matt Raible <mr...@mac.com>.
Just curious - why do you want to use Tomcat 4.1 when 5.0, 5.5 and
6.0 are out?
Matt
On Nov 26, 2007, at 1:41 PM, Prabhu Patil wrote:
> All,
> Is it possible to run Roller 3.1 under JDK 1.5 & Tomcat 4.1.34? The
> installation guide mentions Tomcat 5.x as the recommended version
> of the
> server. However, it does also say any container complaint with servlet
> spec 2.3 will work.
>
> I'm trying to get Roller 3.1 working under JDK 1.5 & Tomcat 4.1.34
> with
> no results.
>
> -Thanks
Roller under JDK 1.5 and Tomcat 4.1.34
Posted by Prabhu Patil <pp...@digitas.com>.
All,
Is it possible to run Roller 3.1 under JDK 1.5 & Tomcat 4.1.34? The
installation guide mentions Tomcat 5.x as the recommended version of the
server. However, it does also say any container complaint with servlet
spec 2.3 will work.
I'm trying to get Roller 3.1 working under JDK 1.5 & Tomcat 4.1.34 with
no results.
-Thanks
Re: can i set password to protect a particular blog entry ?
Posted by Dave <sn...@gmail.com>.
On Nov 21, 2007 5:47 AM, Thinkboy <ma...@gmail.com> wrote:
> I am thinking how to set a certain blog as private , then whoever
> trying to view this entry will be authenticated.
What if weblog posts had the following levels of privacy:
- Private: only members of the blog can see the entry
- Protected: only logged in Roller users can see the entry
- Public: everybody (including anonymous visitors) can see the entry
Would that be sufficient?
> of course, i am not referring the servlet security spec.
> how about a tag / or extra column for weblog entry. when we view a
> page , set a pointcut to verify this special tag,
> and protect this by acegi .
We don't do any AOP in Roller, so point-cut is out. And we don't want
to depend directly on Acegi because Roller should also be able to work
with Container Manager Authentication (CMA) too.
I think we could implement the levels of privacy above using the
Roller 4.1 permission system, plus one additional field on each entry.
However, the implications on caching and feeds could make things a
little complex. We'd need to think through those issues very
carefully.
Discussions like this should probably happen on the dev list.
- Dave