[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bricolage-bugs
Subject:    [Bricolage-Bugs] [Bug 745] New: postgresql field "site.name" value seems irrelevant where site.id=10
From:       bugzilla-daemon () thepirtgroup ! com
Date:       2004-07-25 7:57:16
Message-ID: 200407250757.i6P7vGa43258 () bricolage-bugzilla ! about ! com
[Download RAW message or body]

           Summary: postgresql field "site.name" value seems irrelevant
                    where site.id=100
           Product: Bricolage
           Version: 1.8.x - Current Stable Release
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Database
        AssignedTo: david@kineticode.com
        ReportedBy: will@serensoft.com


We just installed 1.8.1; admin -> system -> sites; we renamed "DefaultSite" to
something else. Now we add some users who have access to the new site: admin ->
system -> users; when creating (or editing) a user, the "Default Site" still
shows up under gruop memberships with create/deny/edit/publish/read/recall
available.

Apparently regardless of what's in the site.name field (where id = 100) it shows
up as "DefaultSite". even better, it shows up even when field site.active = 0!

Short version: "DefaultSite" seems to be hardwired into the HTML::Mason
somewhere, instead of being pulled from the database.

http://bugzilla.bricolage.cc/show_bug.cgi?id=745


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bricolage-Bugs mailing list
Bricolage-Bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-bugs
[prev in list] [next in list] [prev in thread] [next in thread]