ACL changes from 2.06 to 2.07; auto-refresh

I did an upgrade last night, from 2.06 to 2.07 (finally), and broke a
couple of things in the process. Nothing serious – mostly just the
ability for users to take tickets.

Before the upgrade, I had given the group Support permission to Own Ticket
in the Support queue. This worked fine. Now, they need to have Modify
Ticket in order to take it. Otherwise, they get a Permission Denied
message (and nothing shows up in the logs). Was this a purposeful change,
or a result of some ACL modifications?

And on a not-so-similar note – we’re not getting the auto-refresh dropdown
menu. When I did a new installation, to a test directory on a test
database (fresh, no contents), I could see the option when logged in as
root. As soon as I change to the new database, the menu
disappears. Anyone know what could be causing that?

And on a not-so-similar note – we’re not getting the auto-refresh dropdown

menu. When I did a new installation, to a test directory on a test

database (fresh, no contents), I could see the option when logged in as

root. As soon as I change to the new database, the menu

disappears. Anyone know what could be causing that?

Did you restart Apache? Not just a kill -HUP, but really stop it and
start it again?

Martin

Martin Schapendonk, martin@schapendonk.org, Phone: +31 (0)6 55770237
Student Information Systems and Management at Tilburg University

And on a not-so-similar note – we’re not getting the auto-refresh dropdown

menu. When I did a new installation, to a test directory on a test

database (fresh, no contents), I could see the option when logged in as

root. As soon as I change to the new database, the menu

disappears. Anyone know what could be causing that?

Did you restart Apache? Not just a kill -HUP, but really stop it and
start it again?

Multiple times. The test installation was in a different DocumentRoot, so
there was a stop-start (apachectl stop ; apachectl start) whenever changing
from one to the other.

I have found that you sometimes need to repeat apachectl stop until it
reports no pid, then apachectl start.From: “Damian Gerow” damian@sentex.net
To: “Martin Schapendonk” martin@schapendonk.org
Cc: rt-users@lists.fsck.com
Sent: Friday, September 21, 2001 10:35 AM
Subject: Re: [rt-users] ACL changes from 2.06 to 2.07; auto-refresh

And on a not-so-similar note – we’re not getting the auto-refresh

dropdown

menu. When I did a new installation, to a test directory on a test

database (fresh, no contents), I could see the option when logged in as

root. As soon as I change to the new database, the menu

disappears. Anyone know what could be causing that?

Did you restart Apache? Not just a kill -HUP, but really stop it and
start it again?

Multiple times. The test installation was in a different DocumentRoot, so
there was a stop-start (apachectl stop ; apachectl start) whenever
changing
from one to the other.


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

I have found that you sometimes need to repeat apachectl stop until it
reports no pid, then apachectl start.

Just tried it, and still no go.

Neither of these things sound like things that got changed between
2.0.6 and 2.0.7. There’s something screwy going on with your install.On Fri, Sep 21, 2001 at 10:21:46AM -0400, Damian Gerow wrote:

I did an upgrade last night, from 2.06 to 2.07 (finally), and broke a
couple of things in the process. Nothing serious – mostly just the
ability for users to take tickets.

Before the upgrade, I had given the group Support permission to Own Ticket
in the Support queue. This worked fine. Now, they need to have Modify
Ticket in order to take it. Otherwise, they get a Permission Denied
message (and nothing shows up in the logs). Was this a purposeful change,
or a result of some ACL modifications?

And on a not-so-similar note – we’re not getting the auto-refresh dropdown
menu. When I did a new installation, to a test directory on a test
database (fresh, no contents), I could see the option when logged in as
root. As soon as I change to the new database, the menu
disappears. Anyone know what could be causing that?


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

Neither of these things sound like things that got changed between
2.0.6 and 2.0.7. There’s something screwy going on with your install.

Thought it would be that, and re-installed from scratch. The only thing
that’s the same is the database (and parts of config.pm).