[opencms-dev] Publish on a specific site?

[Chirouze Olivier]

Hi Kai,
 
Thanks for your interesting reply. I went for the "project" solution and here's how I did:
 
Created groups:
GROUP_A
GROUP_B
 
Created directories:
/sites/APPLICATION_A => only allowed for group GROUP_A
/sites/APPLICATION_B => only allowed for group GROUP_B
 
Created projects:
PROJECT_A => resource = /sites/APPLICATION_A - manager & user group = GROUP_A
PROJECT_B => resource = /sites/APPLICATION_B - manager & user group = GROUP_B
 
That way, a user in GROUP_A will only see project "PROJECT_A" in the combo list and only APPLICATION_A directory. When he publishes, he only publishes on that directory, which is fine!
Also, another important thing is that if he is in GROUP_A and GROUP_B, he would still publish only in one directory at a time.
 
The only drawback I see now, is that in the later case (affected to multiple groups), the user will have to switch BOTH project AND directory to "activate" a different site. Since PROJECT_A has only directory /sites/APPLICATION_A as a resource, I would like /sites/APPLICATION_B to be invisible when you select PROJECT_A. Today, the directory is greyed and even though you cannot upload or modify a file (fortunately), it is still error-prone and users might get a bit confused. Not a major thing, though.
 
Any idea on how I could solve that *last* issue?
 
By the way, adding a project is much simpler than adding a site, which is great ;-)
 
Thanks
 
Olivier

Olivier CHIROUZE
I&0 Infrastructure 
Volvo Information Technology 

 


________________________________

	From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Schliemann, Kai
	Sent: 25 July 2008 11:43
	To: The OpenCms mailing list
	Subject: Re: [opencms-dev] Publish on a specific site?
	
	
	Hi Olivier,
	the publish button publishes resources which belong to the selected project / organizational unit. So what you need is either a project for each site or an OU (organizational unit) for each site.
	 
	HTH
	Regards
	Kai
	
	
	
	
	
	_________________________________________
	   
	Kai Schliemann
	Dipl.-Wirtschaftsingenieur (FH)
	Senior IT-Berater, Produktmanager OpenCms
	    
	comundus GmbH
	Schüttelgrabenring 3, D-71332 Waiblingen
	Telefon +49 7151-50028-20
	
	E-Mail k.schliemann at comundus.com
	Internet www.comundus.com
	 
	
	Geschäftsführer Klaus Hillemeier  
	Amtsgericht Stuttgart, HRB 264290
	         
	comundus ist ein Unternehmen der IT EXCELLENCE Group
	_________________________________________
	 

________________________________

	Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Chirouze Olivier
	Gesendet: Freitag, 25. Juli 2008 11:18
	An: The OpenCms mailing list
	Betreff: [opencms-dev] Publish on a specific site?
	
	

	Hi list, 

	There's something I just discovered on OpenCms (these things happen everyday, which is great ;-). That thing surprises me and annoys me!

	It seems if you click the nice "publish" button, that will publish resources for ** all sites your have permissions on **.

	I don't understand then what's the point to have multiple sites if you won't publish only the site you are working on. 

	If I'm not clear, let me give you a small scenario: 
	- I created sites A & B (added directory, added to opencms-system.xml, restarted) 
	- created groups G_A & G_B 
	- each directory is only allowed for its group (permissions) 
	=> so you need to be affected to group G_A to have rights on site A, same for B. 
	- if the user is in group A only, he selects site A, click publish => only site A is published (that's perfect) 
	- but if the user is in both groups, selects site A, click publish => resources from site A & B are published. 

	That's not the behaviour I would like to have. I think whenever you choose a specific site, that should become the scope you work on. A click on publish should publish resources for that scope only, even though you have the rigths to work on other projects.

	Am I missing a configuration parameter? Does it seem logical to you? 

	The goal is to have a list of "sites" with associated groups. Publisher work only on their sites. A publisher can be allowed on multiple sites but will work on one site at a time. I thought sites + groups was the perfect solution but I had this bad surprise. Am I choosing a wrong solution?

	Thanks! 

	Olivier 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20080728/5586b85e/attachment.htm>