for ex.,
rubrique-10.html :
[(#SESSION|oui)
<INCLUDE{fond=inc/my_private_content,env}>
][(#SESSION|non) #LOGIN_PUBLIC
]
(note that you can’t include loops inside the conditionnal part of the expression (#SESSION|oui). If you want to do this, use the plugin spip-bonux – http://www.spip-contrib.net/SPIP-Bounce – and <BOUCLE_test(CONDITION)>)
Imho I think « Acces Restreint » is usefull if you want to manage several user groups or non-standard ACL rules. For a simple restriction, #SESSION and #LOGIN_PUBLIC can do the job.
Regards,
.Gilles VINCENT
On Wed, Jun 16, 2010 at 12:25 AM, tom dissing <tom@mir2.dk> wrote:
Is there any plugs og clever « work arounds » on making part of a spip site « private ».
Im thinking about « closing » part of my archive, so that only visitors with acces can read.
I did try out Acces Restreint but would like to know if there is other options…
eventually including paypal options for spip 2.xx ?
kindly
Tom Dissing
All the above mentioned solutions mean that visitors with granted acces will also be able to enter the private area.
I would like to password-protect one page. About 30 people will have acces to read (one login, one pass, would be good enough). Normally I would say I could use a .htacces and .htpass, but those will then go in the squellettes folder, implying eveything is than protected (not an option). Acces Restreint could work, but as mentioned, you will also give acces to the private area as an editor (that is not an option either). Above all, I would also like the webpage to be part of the spip-cms; that is to be edited and controlled by the spip-cms.
Am I missing something? It looks so easy, but I can’t find a solution. Anyone an idea?
for ex.,
rubrique-10.html :
[(#SESSION|oui)
<INCLUDE{fond=inc/my_private_content,env}>
][(#SESSION|non) #LOGIN_PUBLIC
]
(note that you can't include loops inside the conditionnal part of the expression (#SESSION|oui). If you want to do this, use the plugin spip-bonux -- SPIP Bonux - SPIP-Contrib -- and <BOUCLE_test(CONDITION)>)
Imho I think "Acces Restreint" is usefull if you want to manage several user groups or non-standard ACL rules. For a simple restriction, #SESSION and #LOGIN_PUBLIC can do the job.
Regards,
.Gilles VINCENT
All the above mentioned solutions mean that visitors with granted acces will also be able to enter the private area.
George, thanks for answering, but know I feel stupid. I work with spip allready for a long time, but I only know of an author status as editor or administrator. Where is the option to create acces for a person/author with visitor status?
Regards,
Ewout
On 14 dec. 2010, at 18:00, george@middleeastwatch.net wrote:
Quoting Ewout Dorman <ewout@mac.com>:
Dear all,
referring to this spip-mail from last summer, I still haven't found a satisfying solution:
for ex.,
rubrique-10.html :
[(#SESSION|oui)
<INCLUDE{fond=inc/my_private_content,env}>
][(#SESSION|non) #LOGIN_PUBLIC
]
(note that you can't include loops inside the conditionnal part of the expression (#SESSION|oui). If you want to do this, use the plugin spip-bonux -- SPIP Bonux - SPIP-Contrib -- and <BOUCLE_test(CONDITION)>)
Imho I think "Acces Restreint" is usefull if you want to manage several user groups or non-standard ACL rules. For a simple restriction, #SESSION and #LOGIN_PUBLIC can do the job.
Regards,
.Gilles VINCENT
All the above mentioned solutions mean that visitors with granted acces will also be able to enter the private area.
George, thanks for answering, but know I feel stupid. I work with spip allready for a long time, but I only know of an author status as editor or administrator. Where is the option to create acces for a person/author with visitor status?
Regards,
Ewout
You have to allow the registration of visitors from Site configuration > Interactivity > Visitors paragraph (you can of course delete the registration form from your templates if you don't actually want them to register).
Having done that, you will have an extra item called visitor in the author's status when you create a new author or when you modify an existing author.