Re: what is the pourpose of "fake" projects?

On Tue, 2009-05-19 at 15:23 +0200, Renzo Vettori wrote:
> to clarify my previous post. Manual settings in db "project" table:
> is_fake=1, url='' ->project not listed; project permissions NOT working; 
> document permissions NOT working
> is_fake=1, url=skyrix://server/skyrix-id/ ->project not listed; project 
> permissions NOT working; document permissions NOT working
> is_fake=0, url='' -> project listed; project permissions working; 
> document permissions NOT working
> is_fake=0, url=skyrix://server/skyrix-id/ ->project listed; project 
> permissions working; document permissions working
> So, it seems that if is_fake=1, project permissions are not applied, 
> regardless from url setting.

Gotcha,  still on my list to track down what the &%^@^%$ isFake=1
disables.  

But a project with a NULL URL is, IMO, just wrong.  Document permissions
are managed by the storage backend. The storage backend object is
manifested using the URL - so a project with no URL has no storage
backend to manage permissions.  So that part make sense.

On the other hand a setting to just disable the automatic creation of
"fake" projects for enterprises would also probably make sense.  Would
reduce allot of clutter produced by a rarely used feature.

> Adam Tauno WIlliams ha scritto:
> > On Tue, 2009-05-19 at 11:54 +0200, Renzo Vettori wrote:
> >> As an experiment, I manually changed the flag "is_fake" to 0 in 
> >> "projects" db table. The result is: 1. project becomes listed in webui; 
> >> 2. permission became effective for the project itself, NOT for related 
> >> documents
> >> In a second attempt, I manually addedd the "url" property in "projects" 
> >> db table. The result is: 1. project is listed in webui; 2. permission 
> >> became effective for both project itself AND for related documents.
> >> Only adding the "url" property did not work (permission did not work 
> >> both for the project itself and for related documents).
> > Excellent, thanks for the feedback.  I think the 
> >> So, as a very temporary workaround, I think I can script the changes to 
> >> be made in database for enterprises added outside the webui (which is my 
> >> first aim), the only collateral damage being many more projects being 
> >> listed in the "project" section of the webui. Do you think this is ok?
> >> As a related thought, I think that the "permission" editor in the webui 
> >> for filesystem projects, which can't have any permission applied, is 
> >> really confusing.
> > I believe it is disabled for filesystem projects;  but the lack of a URL
> > breaks that.  I believe the LSNewEnterpriseCommand command needs to be
> > modified to set the url property of the "fake" project.
> > If you build from source you can try the attached path that will set a
> > database-backed style URL for new "fake" projects created for new
> > enterprises.
> >> I really like opengroupware and would like to see it receive all the 
> >> attention it deserves, as a basic component for "sound" intranet 
> >> projects, so I appreciate very much your committment to help users
> > Well, I use it too! :)
-- 
OpenGroupware developer: [email protected]
<http://whitemiceconsulting.blogspot.com/>
OpenGroupare & Cyrus IMAPd documenation @
<http://docs.opengroupware.org/Members/whitemice/wmogag/file_view>

-- 
OpenGroupware.org Users
[email protected]
http://mail.opengroupware.org/mailman/listinfo/users