date:20140521

Re: [rt-users] Rich text editor disabled after update to 4.2.4

2014-05-21 Thread Martin Janíček

You can inspect that file with some web-developement tool in your browser,
look on the given line 2403 and then try to identify the .js file from where
that line originate (squished .js file contains all .js files that RT uses,
merged together). This should help you figure out to what is this property
attached.

 

btw

 

RT_SiteConfig.pm

Set($MessageBoxRichTextHeight, 400);

 

 

-mJ

 

From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf
Of Robert Shaker
Sent: Tuesday, May 20, 2014 8:01 PM
To: rt-us...@bestpractical.com
Subject: Re: [rt-users] Rich text editor disabled after update to 4.2.4

 

Also, the chrome console reveals this, which I did not notice before.

 

event.returnValue is deprecated. Please use the standard
event.preventDefault() instead.

Uncaught TypeError: Cannot read property 'MessageBoxRichTextHeight' of
undefined squished-884af658b44cdd5c585766ea0a0518ba.js:2403

 

 

From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf
Of Robert Shaker
Sent: Tuesday, May 20, 2014 1:51 PM
To: rt-us...@bestpractical.com
Subject: [rt-users] Rich text editor disabled after update to 4.2.4

 

Hello mailing list,

 

I have updated my RT installation to 4.2.4 just this Friday, and now we have
noticed that the rich text editor seems to no longer be working. When I
reply to a ticket it shows the quoted text like before, but now it is a
garbled mess of HTML as it is not translating properly. Does anyone have any
idea what's going on?

 

Thank you,

 

Bob Shaker | Co-op IT analyst

Arden Companies | Bombay Outdoors

30400 Telegraph Rd, Suite 200, Bingham Farms, MI 48025

 http://www.ardencompanies.com/ ArdenCompanies.com
http://bombayoutdoors.com/ BombayOutdoors.com 

 

cid:image001.jpg@01CF49DF.644DF900

 

 

  _  

ARDEN
A Global Company
Celebrating over 50 years of making your life more comfortable!

This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, or take any action based on this message or
any information herein. If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message.

This OUTBOUND E-mail and Document(s) has been scanned by an Antivirus
Server.

 

  _  

ARDEN
A Global Company
Celebrating over 50 years of making your life more comfortable!

This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, or take any action based on this message or
any information herein. If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message.

This OUTBOUND E-mail and Document(s) has been scanned by an Antivirus
Server.

-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] RTChecker released as open source

2014-05-21 Thread Guadagnino Cristiano

Hi all,
I have just sorted out the problem with installing ClickOnce application from 
Dropbox.

You can now install RTChecker v2.0.0.3 from my Dropbox, by connecting (with 
Internet Explorer) to this link:
http://goo.gl/qw6bpM

Hope you'll enjoy it!

Bye
Cris







Il giorno mar, 06/05/2014 alle 16.29 +, Guadagnino Cristiano ha scritto:
Hi all,
I just wanted to let you all know that I have released my RTChecker software as 
opensource.

RTChecker is a software that sits in the tray of your Windows desktop and 
notifies you when there are new tickets, or when a ticket that was assigned to 
you has been reopened.
RTChecker connects to your RT installation trough HTTP and works by issuing 
REST requests. You NEED RT 4.2.2+.

I have been developing and enhancing RTChecker since 2009 for our internal use.

Lately I decided to enhance it to make it sufficiently general that it could be 
used from others as well, and to opensource it under the GPL license.

Presently it is Windows only but I hope to make a Linux version soon thanks to 
mono (or to write a python port if mono proves not to be mature enough).

There are also other features that I would like to add soon, like reminders 
notification and quick delete.

You can access the source code at the following address 
https://www.assembla.com/code/rtcheckerv2/subversion/nodes.
Also, a binary release is available from my Dropbox public folder here: 
https://www.dropbox.com/sh/tnz21nfbcpwtijb/KN7beRGVoX/RTChecker.

RTChecker is distributed as a click-once application so you have to open the 
publish.htm file with Internet Explorer.
I am presently having some difficulties convincing IE to correctly open the 
file, so I may change the distribution method soon, although it has been 
working well internally for years. The good thing about clic-once is automatic 
updates, but let's see what I can do with it.

RTChecker took a lot of hours of development in my spare time, so if you find 
it useful please donate (see link in the About box).
I will also happily accept patches if you are so inclined.

A little web page with help and a tutorial will follow soon, but I hope it is 
easy enough to be used without help for now. Languages supported are english 
and italian presently.

Bye
Cris



--
RT Training - Dallas May 20-21
http://bestpractical.com/training

-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

[rt-users] Upgrade History shows Upgrade Incomplete

2014-05-21 Thread Nathan Baker

Hello everyone,

I just upgraded from 4.0.6 to 4.2.3 using the Debian packages.  During the
database upgrade, I received a few errors:

 Processing 4.1.1

Now populating database schema.

[12453] [Wed May 21 03:19:36 2014] [critical]: DBD::Pg::st execute failed:
ERROR:  cannot drop sequence objectscrips_id_seq because other objects
depend on it

DETAIL:  default for table objectscrips column id depends on sequence
objectscrips_id_seq

HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
/usr/share/request-tracker4/lib/RT/Handle.pm line 529.
(/usr/share/request-tracker4/lib/RT.pm:394)

DBD::Pg::st execute failed: ERROR:  cannot drop sequence
objectscrips_id_seq because other objects depend on it

DETAIL:  default for table objectscrips column id depends on sequence
objectscrips_id_seq

HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
/usr/share/request-tracker4/lib/RT/Handle.pm line 529.

error encountered processing
/usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3:

/usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3
exited with non-zero status


There could be an issue with the Debian packages (they are still in the
testing branch), but I'm trying to figure out what state the database is in
now.  The system is working fine, and shows version 4.2.3.  If I navigate
to Admin - Tools - System Configuration, then in the RT Upgrade History
section it looks like it might have tried to upgrade the database twice,
and the second time it failed (understandably).


Is there a way I can verify that the database schema is completely up to
date?


Here is what the RT Upgrade History section shows: (Sorry for the HTML,
wasn't sure how else to show it)
RT (Current version: 4.2.3) ActionDateElapsedRT VersionInsert from
/usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:17:45
20141 second4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:17:53
20141 second4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:17:55
20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade from
4.0.19 to 4.2.3Tue May 20 23:17:56 20142 minutes4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:19:29
20140 seconds4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:19:34
20140 seconds4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:19:35
20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade from
4.0.19 to 4.2.3 (Incomplete)Tue May 20 23:19:36 20144.2.3Upgrade from
4.0.19 to 4.1.0Tue May 20 23:19:36 20140 seconds4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.1.0/contentTue May 20 23:19:36
20140 seconds4.2.3Upgrade from 4.1.0 to 4.1.1 (Incomplete)Tue May 20
23:19:36 20144.2.3Schema updates from
/usr/share/request-tracker4/etc/upgrade/4.1.1 (Incomplete)Tue May 20
23:19:36 20144.2.3
Thanks,
Nate
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade History shows Upgrade Incomplete

2014-05-21 Thread Kevin Falcone

On Wed, May 21, 2014 at 11:33:20AM -0400, Nathan Baker wrote:
 Hello everyone,
 
 I just upgraded from 4.0.6 to 4.2.3 using the Debian packages.  During the
 database upgrade, I received a few errors:

I'm guessing you set up a new machine, installed request-tracker4 from
testing, restored your database and then did the upgrade?

You have an unclean database with 4.2 tables in it, and you're
tripping over some of the code we added to help RT handle that more
gracefully.

I've pushed
https://github.com/bestpractical/rt/commit/0ac64855f479b4133f4fe838af6b8b2dec8f5d18.patch
and it should be in 4.2.5.  You may be able to apply the patch
manually to /usr/share/request-tracker4/etc/upgrade/4.1.1/schema.Pg
or just clean out your DB by hand before letting the debian upgrade
scripts go.

-kevin

  Processing 4.1.1
 
 Now populating database schema.
 
 [12453] [Wed May 21 03:19:36 2014] [critical]: DBD::Pg::st execute failed:
 ERROR:  cannot drop sequence objectscrips_id_seq because other objects
 depend on it
 
 DETAIL:  default for table objectscrips column id depends on sequence
 objectscrips_id_seq
 
 HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
 /usr/share/request-tracker4/lib/RT/Handle.pm line 529.
 (/usr/share/request-tracker4/lib/RT.pm:394)
 
 DBD::Pg::st execute failed: ERROR:  cannot drop sequence
 objectscrips_id_seq because other objects depend on it
 
 DETAIL:  default for table objectscrips column id depends on sequence
 objectscrips_id_seq
 
 HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
 /usr/share/request-tracker4/lib/RT/Handle.pm line 529.
 
 error encountered processing
 /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3:
 
 /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3
 exited with non-zero status
 
 
 There could be an issue with the Debian packages (they are still in the
 testing branch), but I'm trying to figure out what state the database is in
 now.  The system is working fine, and shows version 4.2.3.  If I navigate
 to Admin - Tools - System Configuration, then in the RT Upgrade History
 section it looks like it might have tried to upgrade the database twice,
 and the second time it failed (understandably).
 
 
 Is there a way I can verify that the database schema is completely up to
 date?
 
 
 Here is what the RT Upgrade History section shows: (Sorry for the HTML,
 wasn't sure how else to show it)
 RT (Current version: 4.2.3) ActionDateElapsedRT VersionInsert from
 /usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:17:45
 20141 second4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:17:53
 20141 second4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:17:55
 20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade from
 4.0.19 to 4.2.3Tue May 20 23:17:56 20142 minutes4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:19:29
 20140 seconds4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:19:34
 20140 seconds4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:19:35
 20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade from
 4.0.19 to 4.2.3 (Incomplete)Tue May 20 23:19:36 20144.2.3Upgrade from
 4.0.19 to 4.1.0Tue May 20 23:19:36 20140 seconds4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.1.0/contentTue May 20 23:19:36
 20140 seconds4.2.3Upgrade from 4.1.0 to 4.1.1 (Incomplete)Tue May 20
 23:19:36 20144.2.3Schema updates from
 /usr/share/request-tracker4/etc/upgrade/4.1.1 (Incomplete)Tue May 20
 23:19:36 20144.2.3
 Thanks,
 Nate



pgpnoqdvz8sSz.pgp
Description: PGP signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Rich text editor disabled after update to 4.2.4

2014-05-21 Thread Robert Shaker

Resolved.

I managed to fix this by basically cleaning out my 
/opt/rt4/local/html/Elements/Header file.

As it turns out, the header in 4.2.4 is loading the JS for the rich text 
editor, and this was being overwritten by my old version of the file.

From: Martin Janíček [mailto:martin.jani...@riomedia.cz]
Sent: Wednesday, May 21, 2014 3:38 AM
To: Robert Shaker; rt-us...@bestpractical.com
Subject: RE: [rt-users] Rich text editor disabled after update to 4.2.4

You can inspect that file with some web-developement tool in your browser, 
look on the given line 2403 and then try to identify the .js file from where 
that line originate (squished .js file contains all .js files that RT uses, 
merged together). This should help you figure out to what is this property 
attached.

btw

RT_SiteConfig.pm
Set($MessageBoxRichTextHeight, 400);


-mJ

From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of 
Robert Shaker
Sent: Tuesday, May 20, 2014 8:01 PM
To: rt-us...@bestpractical.commailto:rt-us...@bestpractical.com
Subject: Re: [rt-users] Rich text editor disabled after update to 4.2.4

Also, the chrome console reveals this, which I did not notice before.

event.returnValue is deprecated. Please use the standard event.preventDefault() 
instead.
Uncaught TypeError: Cannot read property 'MessageBoxRichTextHeight' of 
undefined squished-884af658b44cdd5c585766ea0a0518ba.js:2403


From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of 
Robert Shaker
Sent: Tuesday, May 20, 2014 1:51 PM
To: rt-us...@bestpractical.commailto:rt-us...@bestpractical.com
Subject: [rt-users] Rich text editor disabled after update to 4.2.4

Hello mailing list,

I have updated my RT installation to 4.2.4 just this Friday, and now we have 
noticed that the rich text editor seems to no longer be working. When I reply 
to a ticket it shows the quoted text like before, but now it is a garbled mess 
of HTML as it is not translating properly. Does anyone have any idea what's 
going on?

Thank you,

Bob Shaker | Co-op IT analyst
Arden Companies | Bombay Outdoors
30400 Telegraph Rd, Suite 200, Bingham Farms, MI 48025
ArdenCompanieshttp://www.ardencompanies.com/.com   BombayOutdoors.com 
http://bombayoutdoors.com/

[cid:image001.jpg@01CF7502.5618E450]



ARDEN
A Global Company
Celebrating over 50 years of making your life more comfortable!

This message may contain confidential and/or privileged information. If you are 
not the addressee or authorized to receive this for the addressee, you must not 
use, copy, disclose, or take any action based on this message or any 
information herein. If you have received this message in error, please advise 
the sender immediately by reply e-mail and delete this message.

This OUTBOUND E-mail and Document(s) has been scanned by an Antivirus Server.


ARDEN
A Global Company
Celebrating over 50 years of making your life more comfortable!

This message may contain confidential and/or privileged information. If you are 
not the addressee or authorized to receive this for the addressee, you must not 
use, copy, disclose, or take any action based on this message or any 
information herein. If you have received this message in error, please advise 
the sender immediately by reply e-mail and delete this message.

This OUTBOUND E-mail and Document(s) has been scanned by an Antivirus Server.


ARDEN
A Global Company
Celebrating over 50 years of making your life more comfortable!

This message may contain confidential and/or privileged information. If you are 
not the addressee or authorized to receive this for the addressee, you must not 
use, copy, disclose, or take any action based on this message or any 
information herein. If you have received this message in error, please advise 
the sender immediately by reply e-mail and delete this message.

This OUTBOUND E-mail and Document(s) has been scanned by an Antivirus Server.
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

[rt-users] Need help with upgrade

2014-05-21 Thread Sears, Mark

I have recently taken on managing the RT system.  It is currently housed on 
(2) systems - a back end and a front end server.  I am not sure why the need 
for 2 systems to host the RT instance - can anyone explain?  So, I want to 
upgrade from 3.8.7 to the latest 4.2.4.  I get the instructions and understand 
the upgrade process but am kind of stumped where to do the upgrade (ie on front 
end or back end).  I believe the back end is the database for the RT system.

Any guidance would be appreciated

Thanks,
Mark Sears - CISSP-M.S. IA
Principal Information Security Analyst
 [cid:image001.png@01CE728F.61780B30]
12249 Science Drive Suite 160
Orlando, FL 32826
office: (407) 541-4062
fax: (407) 380-3823
mark.se...@gdit.commailto:mark.se...@gdit.com
www.gdit.comhttp://www.gdit.com/



-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade History shows Upgrade Incomplete

2014-05-21 Thread Nathan Baker

On Wed, May 21, 2014 at 1:22 PM, Kevin Falcone falc...@bestpractical.comwrote:

 On Wed, May 21, 2014 at 11:33:20AM -0400, Nathan Baker wrote:
  Hello everyone,
 
  I just upgraded from 4.0.6 to 4.2.3 using the Debian packages.  During
 the
  database upgrade, I received a few errors:

 I'm guessing you set up a new machine, installed request-tracker4 from
 testing, restored your database and then did the upgrade?


Actually this is on a system that was running 4.0.6 previously.  I just did
apt-get install request-tracker4 (using the testing repository) and it
upgraded all the packages.


 You have an unclean database with 4.2 tables in it, and you're
 tripping over some of the code we added to help RT handle that more
 gracefully.


What I'm wondering is how I can tell if the database is unclean or if
it's okay.  The upgrade history section in System Configuration shows
that it did Upgrade from 4.0.19 to 4.2.3 once without errors, and then it
did it again and it says (Incomplete).  Maybe that doesn't actually mean
it tried twice though, I'm not sure.



 I've pushed

 https://github.com/bestpractical/rt/commit/0ac64855f479b4133f4fe838af6b8b2dec8f5d18.patch
 and it should be in 4.2.5.  You may be able to apply the patch
 manually to /usr/share/request-tracker4/etc/upgrade/4.1.1/schema.Pg
 or just clean out your DB by hand before letting the debian upgrade
 scripts go.


Can I safely just drop  the table, drop the sequence, create the sequence,
and create the table?  I won't lose anything critical by doing that?

I'm guessing there's a bunch of stuff it was supposed to do after that, but
it probably stopped at that point.  I'm just thrown off by it being in the
upgrade history twice, the first time it looks like it did a whole bunch
of stuff successfully, including this step and lot after this step.

-kevin

   Processing 4.1.1
 
  Now populating database schema.
 
  [12453] [Wed May 21 03:19:36 2014] [critical]: DBD::Pg::st execute
 failed:
  ERROR:  cannot drop sequence objectscrips_id_seq because other objects
  depend on it
 
  DETAIL:  default for table objectscrips column id depends on sequence
  objectscrips_id_seq
 
  HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
  /usr/share/request-tracker4/lib/RT/Handle.pm line 529.
  (/usr/share/request-tracker4/lib/RT.pm:394)
 
  DBD::Pg::st execute failed: ERROR:  cannot drop sequence
  objectscrips_id_seq because other objects depend on it
 
  DETAIL:  default for table objectscrips column id depends on sequence
  objectscrips_id_seq
 
  HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
  /usr/share/request-tracker4/lib/RT/Handle.pm line 529.
 
  error encountered processing
  /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3:
 
  /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3
  exited with non-zero status
 
 
  There could be an issue with the Debian packages (they are still in the
  testing branch), but I'm trying to figure out what state the database is
 in
  now.  The system is working fine, and shows version 4.2.3.  If I navigate
  to Admin - Tools - System Configuration, then in the RT Upgrade
 History
  section it looks like it might have tried to upgrade the database twice,
  and the second time it failed (understandably).
 
 
  Is there a way I can verify that the database schema is completely up to
  date?
 
 
  Here is what the RT Upgrade History section shows: (Sorry for the HTML,
  wasn't sure how else to show it)
  RT (Current version: 4.2.3) ActionDateElapsedRT VersionInsert from
  /usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:17:45
  20141 second4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:17:53
  20141 second4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:17:55
  20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade
 from
  4.0.19 to 4.2.3Tue May 20 23:17:56 20142 minutes4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:19:29
  20140 seconds4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:19:34
  20140 seconds4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:19:35
  20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade
 from
  4.0.19 to 4.2.3 (Incomplete)Tue May 20 23:19:36 20144.2.3Upgrade from
  4.0.19 to 4.1.0Tue May 20 23:19:36 20140 seconds4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.1.0/contentTue May 20 23:19:36
  20140 seconds4.2.3Upgrade from 4.1.0 to 4.1.1 (Incomplete)Tue May 20
  23:19:36 20144.2.3Schema updates from
  /usr/share/request-tracker4/etc/upgrade/4.1.1 (Incomplete)Tue May 20
  23:19:36 20144.2.3
  Thanks,
  Nate


 --
 RT Training - Boston, September 9-10
 http://bestpractical.com/training


Thanks,
Nate
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade History shows Upgrade Incomplete

2014-05-21 Thread Nathan Baker

After looking at all of the schema.Pg files after 4.1.1, it looks like all
of the changes have already been applied. The subsequent changes in the
4.1.1 script have also been applied already (Disabled column was added,
Stage and Queue columns were removed), so I don't think it would work to
patch my 4.1.1 file and run the upgrade again.

From what I can tell, the upgrade was successful the first time and failed
the second time, which is probably for the best anyway. I'm not sure what
caused that, but I did notify Dominic about it. I guess unless I notice
any problems, I'm just going to leave it and consider it to be normal/clean.

Thanks,
Nate

On Wed, May 21, 2014 at 4:23 PM, Nathan Baker bak...@gmail.com wrote:

On Wed, May 21, 2014 at 1:22 PM, Kevin Falcone
falc...@bestpractical.comwrote:

On Wed, May 21, 2014 at 11:33:20AM -0400, Nathan Baker wrote:
Hello everyone,

I just upgraded from 4.0.6 to 4.2.3 using the Debian packages. During
the
database upgrade, I received a few errors:

I'm guessing you set up a new machine, installed request-tracker4 from
testing, restored your database and then did the upgrade?

Actually this is on a system that was running 4.0.6 previously. I just
did apt-get install request-tracker4 (using the testing repository) and it
upgraded all the packages.

You have an unclean database with 4.2 tables in it, and you're
tripping over some of the code we added to help RT handle that more
gracefully.

What I'm wondering is how I can tell if the database is unclean or if
it's okay. The upgrade history section in System Configuration shows
that it did Upgrade from 4.0.19 to 4.2.3 once without errors, and then it
did it again and it says (Incomplete). Maybe that doesn't actually mean
it tried twice though, I'm not sure.

I've pushed

https://github.com/bestpractical/rt/commit/0ac64855f479b4133f4fe838af6b8b2dec8f5d18.patch
and it should be in 4.2.5. You may be able to apply the patch
manually to /usr/share/request-tracker4/etc/upgrade/4.1.1/schema.Pg
or just clean out your DB by hand before letting the debian upgrade
scripts go.

Can I safely just drop the table, drop the sequence, create the sequence,
and create the table? I won't lose anything critical by doing that?

I'm guessing there's a bunch of stuff it was supposed to do after that,
but it probably stopped at that point. I'm just thrown off by it being in
the upgrade history twice, the first time it looks like it did a whole
bunch of stuff successfully, including this step and lot after this step.

-kevin

Processing 4.1.1

Now populating database schema.

[12453] [Wed May 21 03:19:36 2014] [critical]: DBD::Pg::st execute
failed:
ERROR: cannot drop sequence objectscrips_id_seq because other objects
depend on it

DETAIL: default for table objectscrips column id depends on sequence
objectscrips_id_seq

HINT: Use DROP ... CASCADE to drop the dependent objects too. at
/usr/share/request-tracker4/lib/RT/Handle.pm line 529.
(/usr/share/request-tracker4/lib/RT.pm:394)

DBD::Pg::st execute failed: ERROR: cannot drop sequence
objectscrips_id_seq because other objects depend on it

DETAIL: default for table objectscrips column id depends on sequence
objectscrips_id_seq

HINT: Use DROP ... CASCADE to drop the dependent objects too. at
/usr/share/request-tracker4/lib/RT/Handle.pm line 529.

error encountered processing
/usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3:

/usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3
exited with non-zero status

There could be an issue with the Debian packages (they are still in the
testing branch), but I'm trying to figure out what state the database
is in
now. The system is working fine, and shows version 4.2.3. If I
navigate
to Admin - Tools - System Configuration, then in the RT Upgrade
History
section it looks like it might have tried to upgrade the database twice,
and the second time it failed (understandably).

Is there a way I can verify that the database schema is completely up to
date?

Here is what the RT Upgrade History section shows: (Sorry for the
HTML,
wasn't sure how else to show it)
RT (Current version: 4.2.3) ActionDateElapsedRT VersionInsert from
/usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:17:45
20141 second4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20
23:17:53
20141 second4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20
23:17:55
20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade
from
4.0.19 to 4.2.3Tue May 20 23:17:56 20142 minutes4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:19:29
20140 seconds4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20
23:19:34
20140 seconds4.2.3Insert from

[rt-users] problem with custom condition in scrip

2014-05-21 Thread Hugo Escobar

Hello,

I've been attempting to instruct rt to send emails 'On Correspond' to
'Requestors' and 'Ccs',
only if the email address of the user generating the transaction matches a
predetermined list (@domain1 or @domain2)

Following, the code I wrote for the 'custom condition':

#--- begin code ---
if ( $self-TransactionObj-Type ne 'Create'

!grep { $self-CurrentUser-EmailAddress =~ /$_$/ }
   ('@domain1','@domain2')
) {
return 0;
}

return 1;
#-- end code --

This is the Basics section of the scrip:
Description: On Correspond Notify Requestors and Ccs
Condition: User Defined
Action: Notify Requestors and Ccs
Template: Correspondence
Global
Enabled

Additionally, for testing purposes I took care of setting user@domain1 as a
'requestor'

I've tested the code snippet on a regular perl script and it works 100% of
the time, however
RT is not doing what I need.

Any help will be highly appreciated

-- 
Hugo Escobar


[image: AFS_logo.png]

Follow us on Facebook and Linked-In

[image: 
facebook-24x24.png]http://www.facebook.com/pages/Miami-FL/ASSOCIATION-FINANCIAL/64952991864
 [image: linkedin-24x24.png] http://www.linkedin.com/companies/1006276
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Rich text editor disabled after update to 4.2.4

Re: [rt-users] RTChecker released as open source

[rt-users] Upgrade History shows Upgrade Incomplete

Re: [rt-users] Upgrade History shows Upgrade Incomplete

Re: [rt-users] Rich text editor disabled after update to 4.2.4

[rt-users] Need help with upgrade

Re: [rt-users] Upgrade History shows Upgrade Incomplete

Re: [rt-users] Upgrade History shows Upgrade Incomplete

[rt-users] problem with custom condition in scrip

9 matches

Site Navigation

Mail list logo

Footer information