[Trac] fine-grained permissions (AuthzPolicy) and the old way (DefaultPermissionPolicy): any way to share groups?

Hi, I'm mostly trying to recreate the functionality that the old
RestrictedArea plugin provided, by using the new fine-grained
permissions functionality that the AuthzPolicy gives us. What I'd
*like* to be able to do would be to somehow refer to the existing
Permissions groups created via the admin interface, which the
DefaultPermissionPolicy makes use of. In my searching last night, I
found an updated authz_policy.py file (from a comment on this ticket:
http://trac.edgewall.org/ticket/7650) which supposedly offered just
this functionality. However, it's not working. So, before I try any
more tinkering, I thought I'd first ask if anyone has successfully
solved this problem, and if so, would you be willing to share how you
did it?

My plan right now is to just stop using the DefaultPermissionPolicy
and only rely on the AuthzPolicy. It will mean expressing the same
permissions which DefaultPermissionsPolicy enforces in the
authzpolicy.conf file, so that AuthzPolicy can take over that job. Has
anyone done something like this in the past?

The reason I'm going down this road is I'd like to avoid a situation
where I have to maintain group membership information in two places.

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@...
To unsubscribe from this group, send email to trac-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

[Trac] two levels of registered users

Hi all,
I'm almost a new trac user, so I apologize if this is a newbie question 
but I was not able to find an answer.

I have to setup a trac to have two different levels of registered users 
access.

To better explain what I need are "low-level" users able to create 
tickets and visualize only a subset of the tickets and "high-level" 
registered users able to create tickets and visualized/modify all of them.
My idea was to add a boolean field to the ticket, visible only by 
high-level users, used to enable/disable the "low-level" user visualization.

There is any plug-in enabling this possibility?
Can I do this in a different manner?

-Riccardo

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@...
To unsubscribe from this group, send email to trac-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

[Trac] Disable Autolinking?

Hi all,

I am new to using this so I am hopefully making a simple request. I am
creating an FAQ with involves path names, which Trac always tries to
link. I there a way to prevent this autolinking of anything that looks
potentially like a URL?

Thanks.

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@...
To unsubscribe from this group, send email to trac-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

[Trac] Autolink changesets in tickets

Hi all.

One thing I like a lot on github is that is automatically links a
changeset to all the isses that are referenced inside it.
Also very nice is that if one writes fixes #23 the isse 23 is
automatically closed.

I know that redmine chan do the same thing.

Here is my question: Is there a way to get the same funcitonality with
trac v0.10.6dev?
I know that this version is VERRRY old, but I am working as a student
in a big reseach facility and change is happening very slowly here :
( . Also we are still runnin CentOS 5.5 .

Any suggestions? Maybee a plugin?

Cheers
Waldemar

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@...
To unsubscribe from this group, send email to trac-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

[Trac] tracopt.ticket.commit_updater plugin, way to handle one svn repo for multiple trac instances?

Hello,

we currently have one single svn repository where we manage a lib and
projects. The layout for the repository "master" is something like
that:
/lib
/projects
--/project_1
--/project_2

etc.

We would like to use the commit updater plugin to auto close our
tickets. For that purpose we have added to the master repository's
post-commit hook the proposed "trac-admin changeset added" call.
That works perfectly as long as you have only one trac instance.

Due to the fact that we have to stick to the current "one repo"
solution we cannot split the repository but we require more trac
instances (namely for each project and for the lib)

So we have added three "trac-admin changeset added calls" to the
master repository's post-commit hook.
Unfortunately we cannot use the commit_update any more since writing
"closes #123" in the comments would close this ticket for every trac
instance.

Is there a known way to workaround that? The post commit hook of svn
provides the repository path but it is always the trunk (e.g /var/repo/
master for all commits in lib and in projects).

[Trac] format not defined

[Trac] unsub

[Trac]Trac Ticket Mover Plugin

I have a handful of open tickets (about 35) with history, and attachments that I would like to move from 
one instance of trac to another.

Both instances on Linux server
Trac 0.12.1
MySQL 5
Subversion Repository (plan to just bring over the latest baseline and not the history)

I was looking at the TicketMoverPlugin, but see this only went up to 0.11, so was wondering if there
was another plugin or would this work for 0.12 instance

or if there was a procedure I could use.  I didn't think trying to do the CSV export/import would bring over all
the history correctly and the attachments.

I will be leaving the original tickets in the instance of trac they are currently in for reference, but would
like these 35 tickets to now live in the newer Agilo instance.  

I am not versed in MySQL and currently our DBAs are all tied up and haven't had the time to look at this.

Thanks!
Margie

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@...
To unsubscribe from this group, send email to trac-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

[Trac] ANN: MultiRepoSearchPlugin, NewTicketLikeThisPlugin

[Trac] Reopening tickets

Is it acceptable to re-open a trac ticket because you wish the
developers to reconsider implementing the feature?

In particular, I would like to see http://trac.edgewall.org/ticket/3541
reconsidered.

We are a relatively new Trac user (4 months), but so far it looks
extremely good. For our usage, repository search is the only major
missing piece we have seen. It is a real weakness that I suspect we
can work around by using some other tool for that purpose (though, I
have found nothing that looks that good so far).

Neither of the search hacks seem to work very well. At least, I have
failed to make either work well, though I have made both work.

In any case, I believe if you added repository search you would
increase the value of Trac to many users.

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@...
To unsubscribe from this group, send email to trac-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

[Trac] Different behavior (issue ?) of trac.loader.load_components ... HELP

Hi all !

I have two local Trac installations for testing purpose :

1- Trac=0.11 installed from Ubuntu 10.04
    (<= is it enough to get the whole picture ?)
2- Trac=0.13dev installed in a virtual environment using
    setuptools develop command . site-packages dir
    is inherited from global installation

In the first case built-in Trac components (e.g. TicketSystem ) are
loaded , whereas in the later they are not .

The code looks like this (it is asumed that pkg should be the
top-level module in a package e.g. `trac` for Trac , `tracrpc` for
XmlRpcPlugin , ... ;)

{{{
#!py

   from trac.loader import load_components
   for pkg in ['trac'] :
      try :
        __import__(pkg)
      except ImportError :
        pass                        # Skip pkg. What a shame !
      else :
        mdl = sys.modules[pkg]
        load_components(self.env, dirname(dirname(mdl.__file__)))

}}}

Q:
  - Does anybody know why is this (i.e. built-in Trac components
    not loaded) happening in installation #2 ?
  - Is it some issue related to entry points ?

Thanks in advance !

--

Regards,

Olemis

Facebook => http://www.facebook.com/olemis
Twitter => http://www.twitter.com/olemislc (@olemislc)
Blog ES => http://simelo-es.blogspot.com
Blog EN => http://simelo-en.blogspot.com
Quora => http://www.quora.com/olemis
Youtube => http://youtube.com/user/greatsoftw

Get a signature like this. CLICK HERE.

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@...
To unsubscribe from this group, send email to trac-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.