In the past, when setting up RT 3.4, 3.6, and 3.8 I used the base domain
for our company when configuring RT and postfix. For instance, example.com.
We configured Exchange (2007) to relay email destined for
rt-comm...@example.com and r...@example.com to the RT server. This worked
fine.
I am now se
Why don’t use you want to use REST? You’re shooting yourself in the foot; when
you upgrade RT, your queries will no longer work and will have to be updated.
If you use the REST interface, you can upgrade with impunity and not have to
worry about your queries not working anymore.
—
Tom
On Dec
Just typing in a comment/reply and hitting enter in the message box, it
doesn't do anything. You need to use Ctrl-Enter.
On 3 December 2013 09:48, Alex Vandiver wrote:
> On Tue, 2013-12-03 at 09:34 +1100, Andrew Chung wrote:
> > I've got a couple of users who are having problems with using the
On Tue, 2013-12-03 at 09:34 +1100, Andrew Chung wrote:
> I've got a couple of users who are having problems with using the
> enter/return key when using RT 4.2.1 with Safari.
Using the return key in what context?
- Alex
I've got a couple of users who are having problems with using the
enter/return key when using RT 4.2.1 with Safari.
Ctrl-Enter works, but that is not a good work around for our users.
I've replicated this on Safari 6 and Safari 7 on both OS X 10.8/10.9.
Is this happening for others?
Regards,
An
On Sat, 2013-11-30 at 16:59 +0100, Payam Poursaied wrote:
> In the past weeks, we received considerable complaints from our staff
> that their comments and corresponds are not delivered to the
> requestors (i.e. on correspond notify requestors).
>[snip]
> Working more, I found that, when
> HTML::Fo
I'm getting ready to do an upgrade from 4.0.18 to 4.2.1 here on two servers.
When I try the upgrade in a test environment, I get a bunch of errors that fly
by (I don't have them, sorry :( ) but the site appears to be working. My
question is, is it safe to do a "fresh install" of 4.2.1 and then u
From: rt-users-boun...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Wendi M.
Sent: Monday, December 02, 2013 12:35 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Custom Status Setup Problems
I am running RT4 and trying to setup a new custom
I am running RT4 and trying to setup a new custom status for "pending" for
the developers. I have added the following to the RT_SiteConfig, did the
update, and restarted Apache.
#Set Custom Statuses
#Attemping to add a "Pending" status
Set( %Lifecycles, default_pending => {
initial
On Sun, 2013-12-01 at 23:38 -0800, andkulb wrote:
> Is it possible to make a RSS feed from articles like with the tickets?
Not currently; patches accepted.
- Alex
On Fri, 2013-11-29 at 13:37 +, Chris Davies wrote:
> I've finally got around to making some changes to
> RT::Authen::ExternalAuth that allows me to define the Windows domain.
> [snip]
> Are the patches something that would be useful to share here? I've tried
> emailing the contact in the RT:
On Mon, 2013-12-02 at 14:54 +0100, Matthias Peplow wrote:
> after upgrading from 4.016 to 4.2 I cannot select Scrips anymore via
> Admin->Scrips->Select.
Please try the following patch, which should be in 4.2.2:
https://github.com/bestpractical/rt/commit/d9c1d3a.patch
- Alex
On Fri, 2013-11-29 at 13:11 +, Jenny Martin wrote:
> I would like to change our Organization name to avoid confusion with
> another RT instance? Does anyone have a script to fixup the RT database
> so that I can change the Organization name without breaking the RT
> ticket links?
RT 4.2's sbi
On Thu, 2013-11-28 at 11:48 -0800, Chris Black wrote:
> I just upgraded from 4.0.8 to 4.2.1 this morning and when I log in
> with my username which was full admin. When I log in now, I am only
> seeing my list of "open tickets". I can't find any dashboard options,
> admin options, etc.
Please sho
On Mon, 2013-12-02 at 11:38 +0100, m...@fv-berlin.de wrote:
> Hi,
>
> I'm trying to upgrade a 3.6.1-4 (don't ask) RT to 4.0.4-2 and I ran into
> issues.
>
> First of all: I am doing this upgrade (test) on a duplicate of the
> actual production system, so no worries.
>
> As part of the preparatio
On Mon, 2013-12-02 at 15:01 +0100, Matthias Peplow wrote:
> after the Upgrade from 4.016 to 4.2 the history of tickets was not
> shown anymore. The label „loading“ was shown forever but the history
> never appeared.
>
>
> We solved this issue by restoring the RT 4.0 behavior with
>
> Set($ShowH
Hi,
after the Upgrade from 4.016 to 4.2 the history of tickets was not shown
anymore. The label „loading“ was shown forever but the history never appeared.
We solved this issue by restoring the RT 4.0 behavior with
Set($ShowHistory, 'always‘);
How can we get the delayed ticket history worki
Hi,
after upgrading from 4.016 to 4.2 I cannot select Scrips anymore via
Admin->Scrips->Select.
The UI says
An internal RT error has occurred. Your administrator can find more details in
RT's log files.
an in the logs I find
rt4 RT-4: [13778] RT::Scrip::Queue Unimplemented in HTML::Mason::Co
Hi,
I'm trying to upgrade a 3.6.1-4 (don't ask) RT to 4.0.4-2 and I ran into
issues.
First of all: I am doing this upgrade (test) on a duplicate of the
actual production system, so no worries.
As part of the preparation before running the actual database upgrade, I ran
rt-validator --check
Whi
19 matches
Mail list logo