On Nov 4, 11:25 am, Andy C <[EMAIL PROTECTED]> wrote:
> Hi Richard,
>
> Thanks for the detailed analysis.
>
> I think that Access Control Lists are on the roadmap for the next
> release (0.6) which probably explains why this is the case.
>
> The Habari development team would probably maintain that the latest
> SVN head is also 'fluid and under development' rather than 'broken'.
>

I like the way you put that. :) ACL is incomplete at the moment, which
has caused issues with the Habari silo, and I would think the Viddler
silo, though it isn't as commonly used as the Habari silo, partly
because both of them rely on permissions without adding the
permissions to the db or to any users or groups, partly because there
is still no interface for admins to manipulate which groups have
access rights to permissions.

For this reason, as a temporary measure the acl subsystem should be
returning true for permissions that aren't found in the database. It
wasn't doing so properly before, and so the create directory and
upload links weren't showing. r2751 did, however, fix the problem for
me and the links appear in my silo. I don't understand what the
problem is that it isn't working for others.

Rick

That aside, the issue people are still continuing to experience
regarding the upload and create directory link confuses me. They
didn't appear for me, either, but r2751 fixed the problem for me.
> However, like you, I strongly agree that the Habari Media Silo should
> work. Now.
>
> Hopefully, your analysis will enable a developer to add a dummy entry
> in the permissions table (or whatever) to fix this issue.
>
> Alternatively, patches welcome :-)
> --
> Andy
>
> On Nov 4, 4:08 pm, Richard Catto <[EMAIL PROTECTED]> wrote:
>
> > I checked the underlying MySQL databases and the
> > hbi__group_token_permissions table is empty. No permissions are being
> > added explicitly to the db and thus the function will always return
> > false.
>
> > Your system is broken.
>
> > On Nov 4, 5:54 pm, Richard Catto <[EMAIL PROTECTED]> wrote:
>
> > > Andy C wrote:
> > > > On Nov 4, 2:58 pm, Richard Catto <[EMAIL PROTECTED]> wrote:
> > > > > Matt Read wrote:
> > > > > > On Mon, Nov 3, 2008 at 7:13 AM, Richard Catto <[EMAIL PROTECTED]> 
> > > > > > wrote:
> > > > > > > All I get is Root and Browse
> > > > > > > I have no .deriv directory.
> > > > > > > I've followed all the instructions regarding permissions and 
> > > > > > > .htaccess
> > > > > > > and this plugin does not work for me.
> > > > > > > None of the fixes posted so far work a darn.
> > > > > > try r2751
> > > > > Try English.
> > > > Hi Richard
>
> > > > While I share your frustration about not being able to get the Habari
> > > > media silo working, it might be prudent to show a little more respect
> > > > to a developer who is trying to help you.
>
> > > I was indicating to him that his answer is unintelligible to me.
>
> > > > Matt was referring to the fact that he recently submitted a change to
> > > > the Habari code that may have fixed the issue.
> > > > Unfortunately, for me, using Google Chrome it didn't. Neither does the
> > > > media silo work in Firefox (when it used to).
> > > > r2751 refers to the version number in Subversion which is the version
> > > > control system used by Habari.
> > > > There is a Web based interface to subversion where you see changes
> > > > browse the source code.
> > > > For example, the change Matt referred to above
> > > >http://trac.habariproject.org/habari/changeset/2751
>
> > > That I can understand.
>
> > > > It is possible to install Subversion client software so you can pull
> > > > the latest changes.
>
> > > I used subversion to install habari and I'm at version 2756 of habari.
> > > I ran 'svn up' 5 seconds ago at the command line using ssh.
>
> > > > You can also register for an account and log bugs in trac.
>
> > > Done and done.
>
> > > I'm a PHP developer myself but new to habari. Currently I blog on
> > > WordPress and have done so since 2005. I am enthusiastic about the
> > > habari project because I believe a class based system is a huge step
> > > forward and enables developers to much more easily understand code and
> > > locate bugs.
>
> > > I've isolated the code segment that is causing the failure to display
> > > the 'Upload' and 'Create Directory' links in the HabariSilo class in
> > > the file habarisilo.plugin.php:
>
> > >         public function filter_media_controls( $controls, $silo, $path,
> > > $panelname )
> > >         {
> > >                 $class = __CLASS__;
> > >                 if( $silo instanceof $class ) {
> > >                         $controls[]= $this->link_path( self::SILO_NAME . 
> > > '/' . $path,
> > > 'Browse' );
> > >                         if( User::identify()->can( 'upload_media' ) ) {
> > >                                 $controls[]= 
> > > $this->link_panel(self::SILO_NAME . '/' . $path,
> > > 'upload', 'Upload');
> > >                         }
> > >                         if( User::identify()->can( 'create_directories' ) 
> > > ) {
> > >                                 $controls[]= 
> > > $this->link_panel(self::SILO_NAME . '/' . $path,
> > > 'mkdir', 'Create Directory');
> > >                         }
> > >                 }
> > >                 return $controls;
> > >         }
>
> > > The 'User::identify()->can' is returning false in both instances,
> > > which indicates to me, by following the code through user.php and
> > > acl.php that Habari thinks that the logged in user does not have
> > > sufficient rights to manage MediaSilos.
>
> > > However, I have exactly one user defined in my Habari installation
> > > which is the admin user created by the Habari installation.
>
> > > Something is going wrong where that user is not being given the
> > > permissions needed to manage MediaSilos.
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/habari-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to