From dave.wells at foreshore.net Tue Apr 2 03:10:28 2013
From: dave.wells at foreshore.net (Dave Wells)
Date: Tue, 2 Apr 2013 08:10:28 +0100
Subject: [rt-devel] Make Starts field in Ticket Display updatedable like
Last Content(Told)
Message-ID: <32DD3FF116BE9D458E828DA941CF32BB07CBDF1B@exchange01.is.foreshore.net>
RT Version: 3.6.5
Hi,
I am trying to make the Starts date field updatable using a hyperlink
like the Last Content field to set the time value to now, this is in the
default Ticket Display screen Display.html.
I have updated the rt3/share/html/Ticket/Elements/ShowDates file to
include the hyperlink
<&|/l&>Starts&>: |
<% $Ticket->StartsObj->AsString
%> |
I have also updated the rt3/share/html/Ticket/Display.html file to
allow the action to pass
if (defined $ARGS{'Action'}) {
if ($ARGS{'Action'} =~ /^(Steal|Kill|Take|SetTold|SetStarts)$/)
{
my $action = $1;
my ($res, $msg)=$TicketObj->$action();
push(@Actions, $msg);
}
}
The link is now a hyperlink and I can click it however the output is
"Starts changed from Not set to Not set", I have done the same for the
Started field and it works fine as you would expect I'm not sure why the
SetStarts is not working as the SetTold and SetStarted are.
Any help would be greatly appreciated.
Regards
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From davide at nabla2.it Wed Apr 3 04:31:58 2013
From: davide at nabla2.it (Davide Imbeni)
Date: Wed, 3 Apr 2013 10:31:58 +0200
Subject: [rt-devel] Incorrect setting of Time Resolved with multiple
inactive states?
Message-ID:
Hello list,
I have a question / request regarding the setting of Resolved Time for a Ticket that changes status.
I read in the docs that:
RT will automatically set the Resolved date when a ticket's status is changed from an Initial or Active status to an Inactive status.
What I observed is instead that RT automatically set the Resolved date when a ticket's status is changed to an Inactive status, regardless of the original status.
This might seem a small distinction, but with my Lifecycle it makes an important difference.
We have implemented two different "final" states, the usual "resolved" and a following "closed", to keep track of the customer acknowledgement of the provided solution.
Both states are (and should be) inactive.
In our effort/time reports, we need to keep track of the time it took to resolve the ticket, i.e. we want to know when the status changed to "resolved".
When the ticket's status changes to "closed" is relatively irrelevant.
With the current code, unfortunately, the resolved time is changed at this last status change also.
I have implemented a tiny correction that solves the issue for us, but it's directly in the code (Ticket.pm), see below the diff:
--- Ticket.pm.orig 2013-04-02 17:14:45.000000000 +0200
+++ Ticket.pm 2013-04-02 17:44:38.000000000 +0200
@@ -3149,7 +3149,7 @@
#When we close a ticket, set the 'Resolved' attribute to now.
# It's misnamed, but that's just historical.
- if ( $lifecycle->IsInactive($new) ) {
+ if ( $lifecycle->IsInactive($new) && !($lifecycle->IsInactive($old)) ) {
$self->_Set(
Field => 'Resolved',
Value => $now->ISO,
Now my questions:
- Could this patch be incorporated in new releases of RT as a bugfix, or there are actual reasons for the current behavior I did not think about?
- IF the latter is the case, are there better ways for us to patch the code than editing the actual file (and keep track of the patch at every update)?
Thanks for your help
Davide
--- Davide Imbeni, Nabla2 s.r.l.
--- Viale Monchio 116, 41124 Modena (MO) - Italy
--- Email: davide at nabla2.it
From tjrc at sanger.ac.uk Wed Apr 3 04:47:51 2013
From: tjrc at sanger.ac.uk (Tim Cutts)
Date: Wed, 3 Apr 2013 09:47:51 +0100
Subject: [rt-devel] Incorrect setting of Time Resolved with multiple
inactive states?
In-Reply-To:
References:
Message-ID: <6F98CC01-B305-4C93-BD2B-127B016AFD64@sanger.ac.uk>
> --- Ticket.pm.orig 2013-04-02 17:14:45.000000000 +0200
> +++ Ticket.pm 2013-04-02 17:44:38.000000000 +0200
> @@ -3149,7 +3149,7 @@
>
> #When we close a ticket, set the 'Resolved' attribute to now.
> # It's misnamed, but that's just historical.
> - if ( $lifecycle->IsInactive($new) ) {
> + if ( $lifecycle->IsInactive($new) && !($lifecycle->IsInactive($old)) ) {
> $self->_Set(
> Field => 'Resolved',
> Value => $now->ISO,
>
> Now my questions:
> - Could this patch be incorporated in new releases of RT as a bugfix, or there are actual reasons for the current behavior I did not think about?
It's not my place to say, since I'm not a BestPractical developer, but it seems sensible logic to me.
> - IF the latter is the case, are there better ways for us to patch the code than editing the actual file (and keep track of the patch at every update)?
Yes, you can create a Ticket_Overlay.pm overlay module in your local area (for example, /opt/rt4/local/lib/RT/Ticket_Overlay.pm, in a default RT installation - the debian/Ubuntu packaged version has these in a different place), and just override the particular function you want to change (SetQueue). There's documentation on this in the Wiki.
Regards,
Tim
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
From davide at nabla2.it Wed Apr 3 05:30:35 2013
From: davide at nabla2.it (Davide Imbeni)
Date: Wed, 3 Apr 2013 11:30:35 +0200
Subject: [rt-devel] Incorrect setting of Time Resolved with multiple
inactive states?
In-Reply-To: <6F98CC01-B305-4C93-BD2B-127B016AFD64@sanger.ac.uk>
References:
<6F98CC01-B305-4C93-BD2B-127B016AFD64@sanger.ac.uk>
Message-ID: <8B52B47D-E611-42AA-9165-4A1498561463@nabla2.it>
Thanks Tim.
I missed the Overlay method, very useful.
I think the actual function to overlay should be SetStatus (for now I'll disregard status changes that are set together with Queue changes or at creation), but I think I get it.
Thanks again
Davide
--- Davide Imbeni, Nabla2 s.r.l.
--- Viale Monchio 116, 41124 Modena (MO) - Italy
--- Email: davide at nabla2.it
On 03/apr/2013, at 10:47, Tim Cutts wrote:
>> --- Ticket.pm.orig 2013-04-02 17:14:45.000000000 +0200
>> +++ Ticket.pm 2013-04-02 17:44:38.000000000 +0200
>> @@ -3149,7 +3149,7 @@
>>
>> #When we close a ticket, set the 'Resolved' attribute to now.
>> # It's misnamed, but that's just historical.
>> - if ( $lifecycle->IsInactive($new) ) {
>> + if ( $lifecycle->IsInactive($new) && !($lifecycle->IsInactive($old)) ) {
>> $self->_Set(
>> Field => 'Resolved',
>> Value => $now->ISO,
>>
>> Now my questions:
>> - Could this patch be incorporated in new releases of RT as a bugfix, or there are actual reasons for the current behavior I did not think about?
>
> It's not my place to say, since I'm not a BestPractical developer, but it seems sensible logic to me.
>
>> - IF the latter is the case, are there better ways for us to patch the code than editing the actual file (and keep track of the patch at every update)?
>
> Yes, you can create a Ticket_Overlay.pm overlay module in your local area (for example, /opt/rt4/local/lib/RT/Ticket_Overlay.pm, in a default RT installation - the debian/Ubuntu packaged version has these in a different place), and just override the particular function you want to change (SetQueue). There's documentation on this in the Wiki.
>
> Regards,
>
> Tim
>
> --
> The Wellcome Trust Sanger Institute is operated by Genome Research
> Limited, a charity registered in England with number 1021457 and a
> company registered in England with number 2742969, whose registered
> office is 215 Euston Road, London, NW1 2BE.
>
From falcone at bestpractical.com Wed Apr 3 09:32:34 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Wed, 3 Apr 2013 09:32:34 -0400
Subject: [rt-devel] RT 4.0.11rc2 available
Message-ID: <20130403133234.GB1548@jibsheet.com>
RT 4.0.11rc2 is now available for testing.
http://download.bestpractical.com/pub/rt/devel/rt-4.0.11rc2.tar.gz
http://download.bestpractical.com/pub/rt/devel/rt-4.0.11rc2.tar.gz.sig
SHA1 sums
bd69a926963695586d02d19593e9a04f37835c4a rt-4.0.11rc2-third-party-source.tar.gz
834a15e94d25814d7897eaa0a3ac20f403cdbd6c rt-4.0.11rc2-third-party-source.tar.gz.sig
This release of RT contains an update to the WYSIWYG editor (CKEditor) used on
ticket creation and reply pages. The update addresses numerous reports of
editor breakages when using IE 10. It also includes fixes for many other
browsers. You can read more about the included changes at
. We are shipping 3.6.6.1, upgraded from 3.4.1.
We expect a number of bugfixes as a result of the CKEditor upgrade, but there
may be small regressions as well. We would appreciate reports from folks who
have experienced problems with the richtext editor on earlier 4.0 releases of
RT or who have recently upgraded to a newer version of IE.
A complete changelog is available from git by running:
git log rt-4.0.11rc1..rt-4.0.11rc2
or visiting
https://github.com/bestpractical/rt/compare/rt-4.0.11rc1...rt-4.0.11rc2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From kai at xs4all.nl Wed Apr 3 09:50:10 2013
From: kai at xs4all.nl (kai)
Date: Wed, 03 Apr 2013 15:50:10 +0200
Subject: [rt-devel] rt-dump-metadata improvements
Message-ID:
Dear Best Practical,
I needed to create a working copy of our main RT instance, so I had to
patch a few things on rt-dump-metadata to make it useful. Bear with me
for 5 branches, of which a few are quite dependent on each other.
a) Fix the dumping of non-local groups
https://github.com/giganteous/rt/compare/4.0-trunk...4.0/fix-dump-nonlocal-groups
I might've missed a reason why this code was inside the $Local_Only if,
but it seemed implausible to ever dump non-user defined groups. I'm
curious why it's not been noticed before.
b) An option to limit the Users to only dump the privileged ones
https://github.com/giganteous/rt/compare/4.0/fix-dump-nonlocal-groups...4.0/feature-limit-dump-to-privileged-users
Since we have 680k unprivileged users this feature really shines for
us.
c) The previous patch will introduce a bug, the current ACL dumping
code doesn't work when principal IDs get renumbered. This is probably a
bug in itself, because we could've used the rt-shredder to remove users,
so the ACL code is bugged anyway. I've fixed the ACL dumping, sadly
leading to a large diff:
https://github.com/giganteous/rt/compare/4.0/feature-limit-dump-to-privileged-users...4.0/feature-dump-working-acls
Running git diff by hand with -w will show you the diff without the
whitespace. Dunno how to massage github's web compare :).
This is basically a reverse engineered version of the documentation of
Initialdata you guys made available on the website. That was a great
help.
d) Then, as I thought this would be handy, but again, the patch might
be a bit on the ugly side as it creates tests on several key points in
the code:
https://github.com/giganteous/rt/compare/4.0/feature-dump-working-acls%E2%80%A64.0/feature-skip-disabled
This partly fixes a few bugs in the 4.0/feature-dump-working-acls, as I
used a bare 'return' where that obviously wouldn't work.
e) A week later I needed to move a few CustomFields from a testing
environment back to production, and the Categories were missing. I
crafted another patch.
https://github.com/giganteous/rt/compare/4.0-trunk...4.0/fix-dump-metadata-customfieldvalues-attributes
This last one (e) is not dependent on the other work.
Anyway, is it worth to create pull requests for these units of work? Or
is the 4.2 work too much in the way? Are there any tests to be taken
into account?
Regards,
Kai
From MarkRoedel at letu.edu Wed Apr 3 11:59:50 2013
From: MarkRoedel at letu.edu (Roedel, Mark)
Date: Wed, 3 Apr 2013 15:59:50 +0000
Subject: [rt-devel] RT 4.0.11rc2 available
In-Reply-To: <20130403133234.GB1548@jibsheet.com>
References: <20130403133234.GB1548@jibsheet.com>
Message-ID: <2B3D699B434F1F49B73F97861B5FD5440115BE2038@Mail-DB-1.letnet.net>
-----Original Message-----
From: rt-devel-bounces at lists.bestpractical.com [mailto:rt-devel-bounces at lists.bestpractical.com] On Behalf Of Kevin Falcone
Sent: Wednesday, April 03, 2013 8:33 AM
To: rt-devel at lists.bestpractical.com
Subject: [rt-devel] RT 4.0.11rc2 available
> RT 4.0.11rc2 is now available for testing.
>
> This release of RT contains an update to the WYSIWYG editor
> (CKEditor) used on ticket creation and reply pages. The
> update addresses numerous reports of editor breakages when
> using IE 10.
This makes our helpdesk guys happy! Looking good here so far...
From falcone at bestpractical.com Wed Apr 3 15:20:32 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Wed, 3 Apr 2013 15:20:32 -0400
Subject: [rt-devel] Incorrect setting of Time Resolved with multiple
inactive states?
In-Reply-To:
References:
Message-ID: <20130403192032.GC1548@jibsheet.com>
On Wed, Apr 03, 2013 at 10:31:58AM +0200, Davide Imbeni wrote:
> I have a question / request regarding the setting of Resolved Time for a Ticket that changes status.
> I read in the docs that:
>
> RT will automatically set the Resolved date when a ticket's status is changed from an Initial or Active status to an Inactive status.
>
> What I observed is instead that RT automatically set the Resolved date when a ticket's status is changed to an Inactive status, regardless of the original status.
>
> This might seem a small distinction, but with my Lifecycle it makes an important difference.
This dates from the time when for most RTs, you really only had 2
inactive statuses (yes you could add more, but most people didn't).
You were rejecting or resolving a ticket and rarely cared about
toggling between them.
>
> --- Ticket.pm.orig 2013-04-02 17:14:45.000000000 +0200
> +++ Ticket.pm 2013-04-02 17:44:38.000000000 +0200
> @@ -3149,7 +3149,7 @@
>
> #When we close a ticket, set the 'Resolved' attribute to now.
> # It's misnamed, but that's just historical.
> - if ( $lifecycle->IsInactive($new) ) {
> + if ( $lifecycle->IsInactive($new) && !($lifecycle->IsInactive($old)) ) {
> $self->_Set(
> Field => 'Resolved',
> Value => $now->ISO,
This sort of change is something that we could never do in 4.0 but
could be a consideration for 4.2. A change that would be even better
for 4.2 is killing this code and adding a Scrip "On Status Change from
Active to Inactive Set Resolved". It's not terribly complicated and
would allow admins a *lot* more flexibility to control when Resolved
is set.
-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From ruz at bestpractical.com Wed Apr 3 16:48:06 2013
From: ruz at bestpractical.com (Ruslan Zakirov)
Date: Thu, 4 Apr 2013 00:48:06 +0400
Subject: [rt-devel] Incorrect setting of Time Resolved with multiple
inactive states?
In-Reply-To: <20130403192032.GC1548@jibsheet.com>
References:
<20130403192032.GC1548@jibsheet.com>
Message-ID:
On Wed, Apr 3, 2013 at 11:20 PM, Kevin Falcone wrote:
> On Wed, Apr 03, 2013 at 10:31:58AM +0200, Davide Imbeni wrote:
> > I have a question / request regarding the setting of Resolved Time for a
> Ticket that changes status.
> > I read in the docs that:
> >
> > RT will automatically set the Resolved date when a ticket's status is
> changed from an Initial or Active status to an Inactive status.
> >
> > What I observed is instead that RT automatically set the Resolved date
> when a ticket's status is changed to an Inactive status, regardless of the
> original status.
> >
> > This might seem a small distinction, but with my Lifecycle it makes an
> important difference.
>
> This dates from the time when for most RTs, you really only had 2
> inactive statuses (yes you could add more, but most people didn't).
> You were rejecting or resolving a ticket and rarely cared about
> toggling between them.
>
Don't know if I introduced regression or just followed old behaviour when
was imlementing lifecycles, but in any case I think this change should be
in RT 4.2.
--
Best regards, Ruslan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From falcone at bestpractical.com Wed Apr 3 17:27:42 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Wed, 3 Apr 2013 17:27:42 -0400
Subject: [rt-devel] Incorrect setting of Time Resolved with multiple
inactive states?
In-Reply-To:
References:
<20130403192032.GC1548@jibsheet.com>
Message-ID: <20130403212742.GD1548@jibsheet.com>
On Thu, Apr 04, 2013 at 12:48:06AM +0400, Ruslan Zakirov wrote:
> On Wed, Apr 3, 2013 at 11:20 PM, Kevin Falcone <[1]falcone at bestpractical.com> wrote:
>
> On Wed, Apr 03, 2013 at 10:31:58AM +0200, Davide Imbeni wrote:
> > I have a question / request regarding the setting of Resolved Time for a Ticket that
> changes status.
> > I read in the docs that:
> >
> > RT will automatically set the Resolved date when a ticket's status is changed from an
> Initial or Active status to an Inactive status.
> >
> > What I observed is instead that RT automatically set the Resolved date when a ticket's
> status is changed to an Inactive status, regardless of the original status.
> >
> > This might seem a small distinction, but with my Lifecycle it makes an important
> difference.
>
> This dates from the time when for most RTs, you really only had 2
> inactive statuses (yes you could add more, but most people didn't).
> You were rejecting or resolving a ticket and rarely cared about
> toggling between them.
>
> Don't know if I introduced regression or just followed old behaviour when was imlementing
> lifecycles, but in any case I think this change should be in RT 4.2.
Absolutely not a regression - I went back to 3.6 to check and didn't
bother going further. It's just a behavior change that makes sense
now that we have lifecycles (vs the more limited set of statuses).
-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From cloos at netsandbox.de Mon Apr 8 11:40:35 2013
From: cloos at netsandbox.de (Christian Loos)
Date: Mon, 08 Apr 2013 17:40:35 +0200
Subject: [rt-devel] JQuery Date and Time picker translations
Message-ID: <5162E4F3.7010107@netsandbox.de>
Hi RT Developer,
I already opened an bug for this which is linked to RT 4.2.0 release:
http://issues.bestpractical.com/Ticket/Display.html?id=22133
I currently try to implement this for our RT 4.0.10 installation and I'm
not sure what would be the best way for this:
1. find out the user language and load only the language specific JavaScript
2. load all localization JavaScript (add them to @JSFiles in config) and
set the datepicker and timepicker regional attribute to the user language
3. concatenate all localization JavaScript in one file, add it to
@JSFiles in config and set the datepicker and timepicker regional
attribute to the user language
I started with 1. using RT->AddJavaScript but ended up with the same
localization file load multiple times as AddJavaScript don't check if
@JSFile already contains this file.
So I load the localization file with a script element in
/Elements/HeaderJavascript. The pro is that only the used localization
JavaScript is transmitted to the client. The con is that this file isn't
squished.
With 2. the pro is we simply can add the files to @JSFiles in config and
the files will be squished. The con is that we have to modify the files
as the original files set the datepicker and timepicker regional attribute.
With 3. the pro is we only have to add one file to @JSFiles in config
and this one will be squished. The con is that we have to concatenate
the files and also have to remove the datepicker and timepicker regional
attribute setting as with 2.
Chris
From cloos at netcologne.de Tue Apr 9 09:33:55 2013
From: cloos at netcologne.de (Christian Loos)
Date: Tue, 09 Apr 2013 15:33:55 +0200
Subject: [rt-devel] RT 4.0.11rc2 available
In-Reply-To: <20130403133234.GB1548@jibsheet.com>
References: <20130403133234.GB1548@jibsheet.com>
Message-ID: <516418C3.5060206@netcologne.de>
Hi,
just noticed that devel/third-party/README still contains the link to
the old version of the ckeditor.
Chris
From falcone at bestpractical.com Tue Apr 9 11:18:07 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Tue, 9 Apr 2013 11:18:07 -0400
Subject: [rt-devel] RT 4.0.11rc2 available
In-Reply-To: <516418C3.5060206@netcologne.de>
References: <20130403133234.GB1548@jibsheet.com>
<516418C3.5060206@netcologne.de>
Message-ID: <20130409151807.GE1548@jibsheet.com>
On Tue, Apr 09, 2013 at 03:33:55PM +0200, Christian Loos wrote:
> just noticed that devel/third-party/README still contains the link to
> the old version of the ckeditor.
Thanks for the catch, I was in the middle of rolling tarballs so I was
able to fix it before it ships.
-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From falcone at bestpractical.com Tue Apr 9 16:30:32 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Tue, 9 Apr 2013 16:30:32 -0400
Subject: [rt-devel] [rt-announce] RT 4.0.11 Released
Message-ID: <20130409203032.GY1427@jibsheet.com>
RT 4.0.11 is now available for download.
http://download.bestpractical.com/pub/rt/release/rt-4.0.11.tar.gz
http://download.bestpractical.com/pub/rt/release/rt-4.0.11.tar.gz.sig
SHA1 sums
fc59a03b87be5cb02c763c55a2f5f3cafa67d087 rt-4.0.11.tar.gz
828ee5226748485d4de3c228622a5feed8d42ea1 rt-4.0.11.tar.gz.sig
This release of RT contains two large updates.
The WYSIWYG editor (CKEditor) used on ticket creation and reply pages
has been updated to address numerous reports of breakages when using IE
10. It also includes fixes for many other browsers. You can read more
about the included changes at . We are
shipping 3.6.6.1, upgraded from 3.4.1.
If you use RT with mod_perl and have not updated from SetHandler
perl-script to SetHandler modperl, RT will now refuse to start. You can
read more about mod_perl configuration here
http://bestpractical.com/rt/docs/latest/web_deployment.html#mod_perl-2.xx
Bugfixes
* Fix description of the ModifyACL right on Classes.
* Allow sorting by a Queue's SubjectTag (in the admin UI).
* Reminders attached to tickets in the deleted status now no longer
throw errors.
* Custom Fields containing & were not being displayed properly in search
results.
* Validate usernames properly on rename as well as during creation.
* Remove user preference for 'Number of search results' since it was
unused and conflicted with the option on the My RT at a Glance
configuration page.
* Clean up temp files left behind by the REST interface.
* Recipients and Scrips box on Ticket reply/comment pages retain
checkbox state when uploading attachments or including articles or
otherwise reloading the page.
* Charts are no longer hidden by the print css.
* Date Custom Fields should ignore time zones.
* rt-crontool no longer throws an error on --help or other error
conditions.
* When choosing the Shredder link from search results, correctly select
the Tickets plugin.
* Bring back an Article quick search missing since before 4.0.0.
* The default $ExtractSubjectTagMatch no longer removes [comment] from
mail with subjects like [comment] [rtname #1].
* In the Class PageMenus, load a Class not a CustomField to validate the id.
* Date Custom Fields now parse strings like 'today' in the user's
timezone.
* Username and Password are now the same length on IE8/9.
* External Custom Fields can now be changed back to internal
Custom Fields in the CF Admin UI.
* Inline text attachments now obey PlainTextPre or PlainTextMono if
they are set.
* Once a Group contained more than one User or Group, current members of
the Group were not being excluded from the autocomplete results.
* Reloading pages with results= will no longer trigger the CSRF warning.
Features
* Update translations from Launchpad, including a new Catalan
translation by Ton Orga Ventura.
* Watcher searches now pre-load the user when possible to reduce joins
to the Users table and boost query speed.
* When using RT::Record->Update new values are truncated before being
compared to the existing values. This removes a large number of
repeated update transactions that don't change anything.
* Search result formats may contain mailto: links.
* Refuse to start with an error message if RT is configured to use
mod_perl with SetHandler perl-script.
* Improve the display of numbers in the German translation.
Documentation
* Further updates to the code used to generate docs.bestpractical.com
and minor updates to the pod to improve formatting.
* New documentation for the ExtractSubjectTag extension by Kai Storbeck.
Developer
* Allow extensions to add new one-time-to types and headers.
* Expose version sorting code so Module::Install::RTx can use it.
* More consistent returns from RT::Link->LoadByParams.
* Added callbacks for changing the links from Quick search.
* A callback for changing the Queues displayed on the Quick search.
* Test setting and updating private/public GPG keys.
* More escaping of URLs, targets and IDs in the menus.
* Don't create testing databases or set them up when checking syntax.
* Add callbacks to the mobile login form.
A complete changelog is available from git by running:
git log rt-4.0.10..rt-4.0.11
or visiting
https://github.com/bestpractical/rt/compare/rt-4.0.10...rt-4.0.11
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
-------------- next part --------------
_______________________________________________
rt-announce mailing list
rt-announce at lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-announce
From cloos at netcologne.de Thu Apr 11 09:17:26 2013
From: cloos at netcologne.de (Christian Loos)
Date: Thu, 11 Apr 2013 15:17:26 +0200
Subject: [rt-devel] [rt-announce] RT 4.0.11 Released
In-Reply-To: <20130409203032.GY1427__32716.1248228096$1365539535$gmane$org@jibsheet.com>
References: <20130409203032.GY1427__32716.1248228096$1365539535$gmane$org@jibsheet.com>
Message-ID: <5166B7E6.6040205@netcologne.de>
Hi,
just noticed a little regression.
If you reply on an ticket the message box background color isn't red
anymore. This seems to be a side effect from the update of the ckeditor.
Tested with Firefox 20.0 on Ubuntu and IE7 an Windows XP.
Chris
From falcone at bestpractical.com Fri Apr 12 10:08:23 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Fri, 12 Apr 2013 10:08:23 -0400
Subject: [rt-devel] [rt-announce] RT 4.0.11 Released
In-Reply-To: <5166B7E6.6040205@netcologne.de>
References: <20130409203032.GY1427__32716.1248228096$1365539535$gmane$org@jibsheet.com>
<5166B7E6.6040205@netcologne.de>
Message-ID: <20130412140823.GF1548@jibsheet.com>
On Thu, Apr 11, 2013 at 03:17:26PM +0200, Christian Loos wrote:
> just noticed a little regression.
>
> If you reply on an ticket the message box background color isn't red
> anymore. This seems to be a side effect from the update of the ckeditor.
>
> Tested with Firefox 20.0 on Ubuntu and IE7 an Windows XP.
Looks like there was a report at about the same time here:
http://issues.bestpractical.com/Ticket/Display.html?id=23539
The 4.0/fix-ckeditor-bg-color branch is available, but hasn't been
reviewed yet.
-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From ruz at bestpractical.com Fri Apr 12 16:12:07 2013
From: ruz at bestpractical.com (Ruslan Zakirov)
Date: Sat, 13 Apr 2013 00:12:07 +0400
Subject: [rt-devel] looking for testers
Message-ID:
Hi,
We plan to change indexes in 4.2. We would like people to test new indexes
in busy production environments to make sure new set will work better or at
least on the same level.
If you would like to participate then you need to know how to enable log of
slow queries in your DB, list existing indexes, create new indexes and have
time to do this, collect results and write down report.
--
Best regards, Ruslan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From cloos at netcologne.de Wed Apr 17 03:03:20 2013
From: cloos at netcologne.de (Christian Loos)
Date: Wed, 17 Apr 2013 09:03:20 +0200
Subject: [rt-devel] RT create empty MIME entity for empty reply or comment
messages since 4.0.8
Message-ID: <516E4938.5030006@netcologne.de>
Hi,
if you reply or comment on an ticket in the webui and only upload an
attachment and don't put anything in the message box RT creates 3
attachments for this transaction. I would expect only 2 attachments.
Our user use this to add an attachment to the ticket but it can also be
used to just send the requestors the attachment without an message.
This behavior started after we upgraded in March from 4.0.8 to 4.0.10:
mysql> SELECT SUBSTRING(Created, 1, 7) AS Created, COUNT(*) AS COUNT
-> FROM Attachments
-> WHERE ContentType = 'application/octet-stream'
-> AND Filename IS NULL
-> AND ContentEncoding IS NULL
-> GROUP BY 1;
+---------+-------+
| Created | COUNT |
+---------+-------+
| 2013-03 | 131 |
| 2013-04 | 205 |
+---------+-------+
Is this the desired behavior or is this an bug?
Chris
-------------- next part --------------
mysql> select id, Parent, ContentType, Filename, ContentEncoding, Headers FROM Attachments WHERE TransactionId = 2331609\G
*************************** 1. row ***************************
id: 618
Parent: 0
ContentType: multipart/mixed
Filename: NULL
ContentEncoding: NULL
Headers: MIME-Version: 1.0
In-Reply-To:
X-RT-Original-Content-Type: text/plain
X-Mailer: MIME-tools 5.503 (Entity 5.503)
X-RT-Interface: Web
References:
Content-Type: multipart/mixed; boundary="----------=_1366180329-4291-10"
Message-ID:
RT-Send-CC:
RT-Send-BCC:
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 0
*************************** 2. row ***************************
id: 619
Parent: 618
ContentType: application/octet-stream
Filename: NULL
ContentEncoding: NULL
Headers: Content-Type: application/octet-stream
Content-Length: 0
*************************** 3. row ***************************
id: 620
Parent: 618
ContentType: application/pdf
Filename: Android intro.pdf
ContentEncoding: none
Headers: MIME-Version: 1.0
Subject: Android intro.pdf
X-Mailer: MIME-tools 5.503 (Entity 5.503)
Content-Type: application/pdf; name="Android intro.pdf"
Content-Disposition: inline; filename="Android intro.pdf"
Content-Transfer-Encoding: base64
Content-Length: 176607
3 rows in set (0.00 sec)
From ruz at bestpractical.com Wed Apr 17 03:43:23 2013
From: ruz at bestpractical.com (Ruslan Zakirov)
Date: Wed, 17 Apr 2013 11:43:23 +0400
Subject: [rt-devel] RT create empty MIME entity for empty reply or
comment messages since 4.0.8
In-Reply-To: <516E4938.5030006@netcologne.de>
References: <516E4938.5030006@netcologne.de>
Message-ID:
On Wed, Apr 17, 2013 at 11:03 AM, Christian Loos wrote:
> Hi,
>
> if you reply or comment on an ticket in the webui and only upload an
> attachment and don't put anything in the message box RT creates 3
> attachments for this transaction. I would expect only 2 attachments.
>
> Our user use this to add an attachment to the ticket but it can also be
> used to just send the requestors the attachment without an message.
>
> This behavior started after we upgraded in March from 4.0.8 to 4.0.10:
>
> mysql> SELECT SUBSTRING(Created, 1, 7) AS Created, COUNT(*) AS COUNT
> -> FROM Attachments
> -> WHERE ContentType = 'application/octet-stream'
> -> AND Filename IS NULL
> -> AND ContentEncoding IS NULL
> -> GROUP BY 1;
> +---------+-------+
> | Created | COUNT |
> +---------+-------+
> | 2013-03 | 131 |
> | 2013-04 | 205 |
> +---------+-------+
>
> Is this the desired behavior or is this an bug?
>
No. This is a bug.
>
> Chris
>
--
Best regards, Ruslan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From cloos at netcologne.de Wed Apr 17 04:02:11 2013
From: cloos at netcologne.de (Christian Loos)
Date: Wed, 17 Apr 2013 10:02:11 +0200
Subject: [rt-devel] RT create empty MIME entity for empty reply or
comment messages since 4.0.8
In-Reply-To:
References: <516E4938.5030006@netcologne.de>
Message-ID: <516E5703.50407@netcologne.de>
Thanks for the quick response.
I created an ticket for this:
http://issues.bestpractical.com/Ticket/Display.html?id=23665
Chris
Am 17.04.2013 09:43, schrieb Ruslan Zakirov:
> No. This is a bug.
From cloos at netcologne.de Wed Apr 17 06:19:50 2013
From: cloos at netcologne.de (Christian Loos)
Date: Wed, 17 Apr 2013 12:19:50 +0200
Subject: [rt-devel] [rt-announce] RT 4.0.11 Released
In-Reply-To: <20130409203032.GY1427__32716.1248228096$1365539535$gmane$org@jibsheet.com>
References: <20130409203032.GY1427__32716.1248228096$1365539535$gmane$org@jibsheet.com>
Message-ID: <516E7746.3090003@netcologne.de>
Am 09.04.2013 22:30, schrieb Kevin Falcone:
> Features
> * Update translations from Launchpad, including a new Catalan
> translation by Ton Orga Ventura.
I would assume here that missing translations are also added to the po
files from launchpad.
Is this right?
If yes, I can't see any updates to the missing German translations
between 4.0.10 and 4.0.11:
grep 'msgstr ""' ../rt-4.0.10/share/po/de.po |wc -l
352
grep 'msgstr ""' ../rt-4.0.11/share/po/de.po |wc -l
358
Launchpad currently reporting 77 missing German translations.
Chris
From falcone at bestpractical.com Wed Apr 17 08:12:39 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Wed, 17 Apr 2013 08:12:39 -0400
Subject: [rt-devel] [rt-announce] RT 4.0.11 Released
In-Reply-To: <516E7746.3090003@netcologne.de>
References: <20130409203032.GY1427__32716.1248228096$1365539535$gmane$org@jibsheet.com>
<516E7746.3090003@netcologne.de>
Message-ID: <20130417121239.GG1548@jibsheet.com>
On Wed, Apr 17, 2013 at 12:19:50PM +0200, Christian Loos wrote:
> Am 09.04.2013 22:30, schrieb Kevin Falcone:
> > Features
> > * Update translations from Launchpad, including a new Catalan
> > translation by Ton Orga Ventura.
>
> I would assume here that missing translations are also added to the po
> files from launchpad.
> Is this right?
>
> If yes, I can't see any updates to the missing German translations
> between 4.0.10 and 4.0.11:
> grep 'msgstr ""' ../rt-4.0.10/share/po/de.po |wc -l
> 352
> grep 'msgstr ""' ../rt-4.0.11/share/po/de.po |wc -l
> 358
>
> Launchpad currently reporting 77 missing German translations.
Launchpad updates from trunk - we've committed more po updates on
trunk than were included in 4.0.11.
git log share/po
will get you recent changes
git show SHA -- share/po/de.po | grep '+msgid'
will find you new strings
If you can find a string on launchpad but not in 4.0-trunk, let me
know and we can file a bug and triage.
I expect we'll suck in more updates in the next few days.
-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From ruz at bestpractical.com Wed Apr 17 10:58:11 2013
From: ruz at bestpractical.com (Ruslan Zakirov)
Date: Wed, 17 Apr 2013 18:58:11 +0400
Subject: [rt-devel] Devel release of DBIx::SearchBuilder
Message-ID:
Hi,
Recently there were a lot of changes in DBIx::SearchBuilder. Mostly new
features to support code in master branch, but some changes touch existing
code.
We would love to see new DBIx::SB tested with existing RT 3.8 and RT 4.0
installations. DBIx-SearchBuilder-1.63_02 is on its way to the CPAN.
In a few hours you would be able to download it from
http://search.cpan.org/dist/DBIx-SearchBuilder/ page.
Please give a try. I'm going to release production version in a week.
--
Best regards, Ruslan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From geert.wl.claes at gmail.com Fri Apr 19 06:18:17 2013
From: geert.wl.claes at gmail.com (Geert Claes)
Date: Fri, 19 Apr 2013 03:18:17 -0700 (PDT)
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
Message-ID: <1366366696842-53550.post@n7.nabble.com>
Has anyone tried to style the RT Tracker using the popular Twitter Bootstrap
and/or Zurb Foundation type of frameworks to make the tool look a bit
better?
--
View this message in context: http://requesttracker.8502.n7.nabble.com/rt-devel-RT-Tracker-styling-look-n-feel-tp53550.html
Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
From ruz at bestpractical.com Fri Apr 19 08:45:02 2013
From: ruz at bestpractical.com (Ruslan Zakirov)
Date: Fri, 19 Apr 2013 16:45:02 +0400
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
In-Reply-To: <1366366696842-53550.post@n7.nabble.com>
References: <1366366696842-53550.post@n7.nabble.com>
Message-ID:
On Fri, Apr 19, 2013 at 2:18 PM, Geert Claes wrote:
> Has anyone tried to style the RT Tracker using the popular Twitter
> Bootstrap
> and/or Zurb Foundation type of frameworks to make the tool look a bit
> better?
>
Adopting RT to bootstrap will be hard as it dictates markup, so you'll have
to change most mason templates and adjust half of html in there.
--
> View this message in context:
> http://requesttracker.8502.n7.nabble.com/rt-devel-RT-Tracker-styling-look-n-feel-tp53550.html
> Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
>
--
Best regards, Ruslan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From geert.wl.claes at gmail.com Fri Apr 19 09:02:29 2013
From: geert.wl.claes at gmail.com (Geert Claes)
Date: Fri, 19 Apr 2013 06:02:29 -0700 (PDT)
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
In-Reply-To:
References: <1366366696842-53550.post@n7.nabble.com>
Message-ID: <1366376549731-53552.post@n7.nabble.com>
I just found out the the "theme editor" is a recent addition. Were
frameworks such as Twitter Bootstrap or Zurb Foundation considered rather
than the "theme editor"? The look-n-feel is very important and an area
where RT could have scored a big win by building on the back of one of the
popular frameworks. Maybe something for a 4.1 release?
--
View this message in context: http://requesttracker.8502.n7.nabble.com/rt-devel-RT-Tracker-styling-look-n-feel-tp53550p53552.html
Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
From ruz at bestpractical.com Fri Apr 19 10:22:09 2013
From: ruz at bestpractical.com (Ruslan Zakirov)
Date: Fri, 19 Apr 2013 18:22:09 +0400
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
In-Reply-To: <1366376549731-53552.post@n7.nabble.com>
References: <1366366696842-53550.post@n7.nabble.com>
<1366376549731-53552.post@n7.nabble.com>
Message-ID:
On Fri, Apr 19, 2013 at 5:02 PM, Geert Claes wrote:
> I just found out the the "theme editor" is a recent addition. Were
> frameworks such as Twitter Bootstrap or Zurb Foundation considered rather
> than the "theme editor"? The look-n-feel is very important and an area
> where RT could have scored a big win by building on the back of one of the
> popular frameworks. Maybe something for a 4.1 release?
>
We bring a new theme in RT 4.2 without switching to a CSS framework.
I don't think we have time to do such huge ammount of work for 4.2.
> --
> View this message in context:
> http://requesttracker.8502.n7.nabble.com/rt-devel-RT-Tracker-styling-look-n-feel-tp53550p53552.html
> Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
>
--
Best regards, Ruslan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From geert.wl.claes at gmail.com Fri Apr 19 10:32:00 2013
From: geert.wl.claes at gmail.com (Geert Claes)
Date: Fri, 19 Apr 2013 07:32:00 -0700 (PDT)
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
In-Reply-To:
References: <1366366696842-53550.post@n7.nabble.com>
<1366376549731-53552.post@n7.nabble.com>
Message-ID: <1366381920790-53555.post@n7.nabble.com>
Ruslan Zakirov-2 wrote
> We bring a new theme in RT 4.2 without switching to a CSS framework.
While a new theme will very likely be a big improvement, I still reckon that
the work to incorporate a CSS framework (big it may be) will quickly pay
off, because there are a lot of themes available for these frameworks
created by professional designers which have a much better eye for what
looks great as aposed to developers.
--
View this message in context: http://requesttracker.8502.n7.nabble.com/rt-devel-RT-Tracker-styling-look-n-feel-tp53550p53555.html
Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
From falcone at bestpractical.com Fri Apr 19 10:35:11 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Fri, 19 Apr 2013 10:35:11 -0400
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
In-Reply-To: <1366376549731-53552.post@n7.nabble.com>
References: <1366366696842-53550.post@n7.nabble.com>
<1366376549731-53552.post@n7.nabble.com>
Message-ID: <20130419143511.GH1548@jibsheet.com>
On Fri, Apr 19, 2013 at 06:02:29AM -0700, Geert Claes wrote:
> I just found out the the "theme editor" is a recent addition. Were
> frameworks such as Twitter Bootstrap or Zurb Foundation considered rather
> than the "theme editor"? The look-n-feel is very important and an area
> where RT could have scored a big win by building on the back of one of the
> popular frameworks. Maybe something for a 4.1 release?
Since the theme editor was first released in RT 4.0.0 on 2011-04-28
and Twitter's blog post about Bootstrap dates from August of 2011, it
would have been difficult to make use of it when the Theme Editor was
under development.
As my colleague Ruslan said - the churn required for Bootstrap support
will not be happening for 4.2 but is under consideration for 4.4.
-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From trs at bestpractical.com Fri Apr 19 13:45:35 2013
From: trs at bestpractical.com (Thomas Sibley)
Date: Fri, 19 Apr 2013 10:45:35 -0700
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
In-Reply-To: <1366381920790-53555.post@n7.nabble.com>
References: <1366366696842-53550.post@n7.nabble.com>
<1366376549731-53552.post@n7.nabble.com>
<1366381920790-53555.post@n7.nabble.com>
Message-ID: <517182BF.6070408@bestpractical.com>
On 04/19/2013 07:32 AM, Geert Claes wrote:
> Ruslan Zakirov-2 wrote
>> We bring a new theme in RT 4.2 without switching to a CSS framework.
>
> While a new theme will very likely be a big improvement, I still reckon that
> the work to incorporate a CSS framework (big it may be) will quickly pay
> off, because there are a lot of themes available for these frameworks
> created by professional designers which have a much better eye for what
> looks great as aposed to developers.
It is not just looks and appearance that matter for an application, but
also how people interact with it (UX). Switching to a CSS framework
certainly helps, but doesn't actually solve most of the layout and
design problems.
Bootstrap and the ilk are just frameworks, in the end you still need
someone to decide the layout and interaction flow. None of it is easy
or quick work.
We certainly want to improve RT's interface, but _just_ retooling it
onto Bootstrap isn't going to solve any problems by itself.
From geert.wl.claes at gmail.com Fri Apr 19 15:55:34 2013
From: geert.wl.claes at gmail.com (Geert Claes)
Date: Fri, 19 Apr 2013 12:55:34 -0700 (PDT)
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
In-Reply-To: <517182BF.6070408@bestpractical.com>
References: <1366366696842-53550.post@n7.nabble.com>
<1366376549731-53552.post@n7.nabble.com>
<1366381920790-53555.post@n7.nabble.com>
<517182BF.6070408@bestpractical.com>
Message-ID: <1366401334565-53563.post@n7.nabble.com>
Hi Thomas, I completely agree what you said about UX ... I have some UX
design experience myself. Just to clarify, I am only providing constructive
feedback. We may be using RT at work and my first impression without even
trying to accomplish any task was that it looks like an ugly web app from
the 90's which is unfortunate because feature wise RT is up there. The
reason I was asking about ui frameworks was because it'll be one less thing
the developers need to worry about while it will make the job to improve the
UX later easier as well.
--
View this message in context: http://requesttracker.8502.n7.nabble.com/rt-devel-RT-Tracker-styling-look-n-feel-tp53550p53563.html
Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
From martin.wheldon at greenhills-it.co.uk Tue Apr 23 04:14:13 2013
From: martin.wheldon at greenhills-it.co.uk (Martin Wheldon)
Date: Tue, 23 Apr 2013 08:14:13 +0000
Subject: [rt-devel] =?utf-8?q?RTx=3A=3ACalendar_bug_and_accompanying_patch?=
=?utf-8?q?=3F?=
Message-ID:
Hi,
I've just installed RTx::Calendar on a Debian Wheezy box using the
Debian packeged Digest::SHA perl module.
When I select the preferences link the module complains it is unable to
find the Digest::SHA1 module.
The following patch fixes the issue:
--- a/html/Prefs/Calendar.html
+++ b/html/Prefs/Calendar.html
@@ -99,7 +99,13 @@ href="<%$RT::WebPath . '/Search/Build.html'%>">the
Query Builder
&>
<%INIT>
-use Digest::SHA1;
+# Patch for Debian Wheezy modules
+# Attempt to load module SHA1 else try SHA
+if (eval {require Digest::SHA1;1;} ne 1) {
+} else {
+Digest::SHA->import();
+}
+
use RT::SavedSearches;
my $title = loc("Calendar Prefs");
Best Regards
--
Martin Wheldon
Greenhills IT Ltd.
Greenhills IT Ltd. is a limited company registered in England and
Wales.
Company Registration No: 06387214
Registered Offices: 2 Greenhills, Claxton, YORK, North Yorkshire, YO60
7SA
From trs at bestpractical.com Tue Apr 23 14:04:38 2013
From: trs at bestpractical.com (Thomas Sibley)
Date: Tue, 23 Apr 2013 11:04:38 -0700
Subject: [rt-devel] RTx::Calendar bug and accompanying patch?
In-Reply-To:
References:
Message-ID: <5176CD36.1010409@bestpractical.com>
On 04/23/2013 01:14 AM, Martin Wheldon wrote:
> Hi,
>
> I've just installed RTx::Calendar on a Debian Wheezy box using the
> Debian packeged Digest::SHA perl module.
> When I select the preferences link the module complains it is unable to
> find the Digest::SHA1 module.
The Makefile.PL for RTx::Calendar specifies a dependency on
Digest::SHA1. Trying to satisfy it with Digest::SHA and getting a
failure is not a bug.
Debian decided to aggressively drop Digest::SHA1 from their packages.
You'll need to install it from CPAN or continue to use a local patch to
switch RTx::Calendar to Digest::SHA. Many Perl packages Debian provides
are modified by them at install time to s/Digest::SHA1/Digest::SHA/g.
Since Debian is forcing folks' hands on this, the RTx::Calendar dep
should just get changed to Digest::SHA instead of attempting to load it
completely undeclared after ::SHA1 fails.
From martin.wheldon at greenhills-it.co.uk Tue Apr 23 15:18:29 2013
From: martin.wheldon at greenhills-it.co.uk (Martin Wheldon)
Date: Tue, 23 Apr 2013 20:18:29 +0100
Subject: [rt-devel]
=?utf-8?q?RTx=3A=3ACalendar_bug_and_accompanying_patch?=
=?utf-8?q?=3F?=
Message-ID: <7a8f8ffe840937db6bc4ca40f1292bb6@mail.greenhills-it.co.uk>
Hi Thomas,
On 2013-04-23 19:04, Thomas Sibley wrote:
> On 04/23/2013 01:14 AM, Martin Wheldon wrote:
>> Hi,
>>
>> I've just installed RTx::Calendar on a Debian Wheezy box using the
>> Debian packeged Digest::SHA perl module.
>> When I select the preferences link the module complains it is unable
>> to
>> find the Digest::SHA1 module.
>
> The Makefile.PL for RTx::Calendar specifies a dependency on
> Digest::SHA1. Trying to satisfy it with Digest::SHA and getting a
> failure is not a bug.
Sorry, I haven't made myself clear, applying the patch works around the
bug from what I can see
and the RTx::Calendar plugin works.
>
> Debian decided to aggressively drop Digest::SHA1 from their packages.
> You'll need to install it from CPAN or continue to use a local patch
> to
> switch RTx::Calendar to Digest::SHA. Many Perl packages Debian
> provides
> are modified by them at install time to s/Digest::SHA1/Digest::SHA/g.
>
> Since Debian is forcing folks' hands on this, the RTx::Calendar dep
> should just get changed to Digest::SHA instead of attempting to load
> it
> completely undeclared after ::SHA1 fails.
Completely agree. I've just removed the RTx::Calendars dependency on
Digest::SHA1 please see below.
diff --git a/Makefile.PL b/Makefile.PL
index e2d9432..003724d 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -10,6 +10,7 @@ requires 'DateTime' => 0;
requires 'DateTime::Set' => 0;
requires 'Data::ICal' => 0;
requires 'Date::ICal' => 0;
+requires 'Digest::SHA' => 0;
no_index(package => 'RT::Interface::Web::Menu');
diff --git a/html/Prefs/Calendar.html b/html/Prefs/Calendar.html
index 2cf5d92..76ca3b6 100644
--- a/html/Prefs/Calendar.html
+++ b/html/Prefs/Calendar.html
@@ -99,7 +99,7 @@ href="<%$RT::WebPath . '/Search/Build.html'%>">the
Query Builder
&>
<%INIT>
-use Digest::SHA1;
+use Digest::SHA;
use RT::SavedSearches;
my $title = loc("Calendar Prefs");
@@ -118,7 +118,7 @@ if ($HiddenField && $HiddenField eq 'Private') {
}
if (defined $ChangeURL) {
- my @args = $object->SetAttribute(Name => 'ICalURL', Content =>
Digest::SHA1::sha1_base64(time));
+ my @args = $object->SetAttribute(Name => 'ICalURL', Content =>
Digest::SHA::sha1_base64(time));
} elsif (defined $ResetURL) {
my @args = $object->DeleteAttribute('ICalURL');
}
Best Regards
Martin
From trs at bestpractical.com Tue Apr 23 16:55:10 2013
From: trs at bestpractical.com (Thomas Sibley)
Date: Tue, 23 Apr 2013 13:55:10 -0700
Subject: [rt-devel] RTx::Calendar bug and accompanying patch?
In-Reply-To: <7a8f8ffe840937db6bc4ca40f1292bb6@mail.greenhills-it.co.uk>
References: <7a8f8ffe840937db6bc4ca40f1292bb6@mail.greenhills-it.co.uk>
Message-ID: <5176F52E.2060003@bestpractical.com>
On 04/23/2013 12:18 PM, Martin Wheldon wrote:
> Completely agree. I've just removed the RTx::Calendars dependency on
> Digest::SHA1 please see below.
Yep, that's pretty much what I just applied and pushed. It should be
getting indexed on CPAN shortly (missing perms myself), but you can grab
the 0.15 tarball here:
http://cpan.metacpan.org/authors/id/T/TS/TSIBLEY/RTx-Calendar-0.15.tar.gz
From martin.wheldon at greenhills-it.co.uk Wed Apr 24 05:16:16 2013
From: martin.wheldon at greenhills-it.co.uk (Martin Wheldon)
Date: Wed, 24 Apr 2013 09:16:16 +0000
Subject: [rt-devel]
=?utf-8?q?RTx=3A=3ACalendar_bug_and_accompanying_patch?=
=?utf-8?q?=3F?=
In-Reply-To: <5176F52E.2060003@bestpractical.com>
References: <7a8f8ffe840937db6bc4ca40f1292bb6@mail.greenhills-it.co.uk>
<5176F52E.2060003@bestpractical.com>
Message-ID:
Hi Thomas,
Many thanks.
Martin
On 2013-04-23 20:55, Thomas Sibley wrote:
> On 04/23/2013 12:18 PM, Martin Wheldon wrote:
>> Completely agree. I've just removed the RTx::Calendars dependency on
>> Digest::SHA1 please see below.
>
> Yep, that's pretty much what I just applied and pushed. It should be
> getting indexed on CPAN shortly (missing perms myself), but you can
> grab
> the 0.15 tarball here:
>
> http://cpan.metacpan.org/authors/id/T/TS/TSIBLEY/RTx-Calendar-0.15.tar.gz
>
>
> !DSPAM:9,5176e83533231294615937!
From geert.wl.claes at gmail.com Thu Apr 25 02:54:34 2013
From: geert.wl.claes at gmail.com (Geert Claes)
Date: Wed, 24 Apr 2013 23:54:34 -0700 (PDT)
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
In-Reply-To:
References: <1366366696842-53550.post@n7.nabble.com>
Message-ID: <1366872874275-53606.post@n7.nabble.com>
HI Ruslan, I found the css files in "rt/share/html/NoAuth/css/", quick -
maybe silly - question, where are all the "mason" templates?
--
View this message in context: http://requesttracker.8502.n7.nabble.com/rt-devel-RT-Tracker-styling-look-n-feel-tp53550p53606.html
Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
From tjrc at sanger.ac.uk Thu Apr 25 04:33:57 2013
From: tjrc at sanger.ac.uk (Tim Cutts)
Date: Thu, 25 Apr 2013 09:33:57 +0100
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
In-Reply-To: <1366872874275-53606.post@n7.nabble.com>
References: <1366366696842-53550.post@n7.nabble.com>
<1366872874275-53606.post@n7.nabble.com>
Message-ID: <5B230ACA-0081-4302-8F96-2D7D62EC6B17@sanger.ac.uk>
On 25 Apr 2013, at 07:54, Geert Claes wrote:
> HI Ruslan, I found the css files in "rt/share/html/NoAuth/css/", quick -
> maybe silly - question, where are all the "mason" templates?
Almost everything under share/html that isn't in NoAuth is Mason. They basically consist of the mason templates themselves (the .html files) and these then reference lots of mason components, which are in the Elements directories.
Tim
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
From jbrandt at bestpractical.com Thu Apr 25 09:45:16 2013
From: jbrandt at bestpractical.com (Jim Brandt)
Date: Thu, 25 Apr 2013 09:45:16 -0400
Subject: [rt-devel] RT Tracker: styling, look-n-feel ...
In-Reply-To: <1366872874275-53606.post@n7.nabble.com>
References: <1366366696842-53550.post@n7.nabble.com>
<1366872874275-53606.post@n7.nabble.com>
Message-ID: <5179336C.2000202@bestpractical.com>
On 4/25/13 2:54 AM, Geert Claes wrote:
> HI Ruslan, I found the css files in "rt/share/html/NoAuth/css/", quick -
> maybe silly - question, where are all the "mason" templates?
If you're taking a shot at some custom styling, this might be helpful:
http://bestpractical.com/rt/docs/latest/customizing/styling_rt.html
From geert.wl.claes at gmail.com Thu Apr 25 10:50:57 2013
From: geert.wl.claes at gmail.com (Geert Claes)
Date: Thu, 25 Apr 2013 07:50:57 -0700 (PDT)
Subject: [rt-devel] RT on AWS EC2 Micro as a Community AMI?
Message-ID: <1366901457238-53615.post@n7.nabble.com>
Has anyone successfully been able to install and configure RT Request Tracker
on a AWS EC2 Micro instance?
A "Jeevan" seems to have succeeded but on a "Small" rather than a "Micro"
(read free) EC2 instance:
http://geekospace.com/installing-and-configuring-request-tracker-4-on-ubuntu-aws-ec2-instance
I also found these:
http://serverfault.com/questions/435458/apache-taking-up-a-lot-of-cpu-while-running-request-tracker4
(bhowmik)
http://superuser.com/questions/518776/request-tracker-on-ubuntu-12-04-lts-ec2-instance-with-rds
(again Jeevan?)
Maybe one of the seasoned RT admins here could share a free Community
Contributed AMI (Amazon Machine Image) so that people can have a play around
with RT quickly?
Anyhow, just a thought
--
View this message in context: http://requesttracker.8502.n7.nabble.com/RT-on-AWS-EC2-Micro-as-a-Community-AMI-tp53615.html
Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
From cloos at netsandbox.de Fri Apr 26 08:30:46 2013
From: cloos at netsandbox.de (Christian Loos)
Date: Fri, 26 Apr 2013 14:30:46 +0200
Subject: [rt-devel] RT on AWS EC2 Micro as a Community AMI?
In-Reply-To: <1366901457238-53615.post@n7.nabble.com>
References: <1366901457238-53615.post@n7.nabble.com>
Message-ID: <517A7376.5090108@netsandbox.de>
Hi Geert,
I have tried this (Apache and MySQL) a few weeks ago and hat to switch
from a Micro to a Small instance because the 613 MiB RAM of the Micro
instance isn't enough.
Chris
Am 25.04.2013 16:50, schrieb Geert Claes:
> Has anyone successfully been able to install and configure RT Request Tracker
> on a AWS EC2 Micro instance?
>
> A "Jeevan" seems to have succeeded but on a "Small" rather than a "Micro"
> (read free) EC2 instance:
> http://geekospace.com/installing-and-configuring-request-tracker-4-on-ubuntu-aws-ec2-instance
>
> I also found these:
> http://serverfault.com/questions/435458/apache-taking-up-a-lot-of-cpu-while-running-request-tracker4
> (bhowmik)
> http://superuser.com/questions/518776/request-tracker-on-ubuntu-12-04-lts-ec2-instance-with-rds
> (again Jeevan?)
>
> Maybe one of the seasoned RT admins here could share a free Community
> Contributed AMI (Amazon Machine Image) so that people can have a play around
> with RT quickly?
>
> Anyhow, just a thought
>
>
>
>
>
> --
> View this message in context: http://requesttracker.8502.n7.nabble.com/RT-on-AWS-EC2-Micro-as-a-Community-AMI-tp53615.html
> Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
>
From martin.wheldon at greenhills-it.co.uk Fri Apr 26 07:49:17 2013
From: martin.wheldon at greenhills-it.co.uk (Martin Wheldon)
Date: Fri, 26 Apr 2013 11:49:17 +0000
Subject: [rt-devel] =?utf-8?q?RT_on_AWS_EC2_Micro_as_a_Community_AMI=3F?=
In-Reply-To: <517A7376.5090108@netsandbox.de>
References: <1366901457238-53615.post@n7.nabble.com>
<517A7376.5090108@netsandbox.de>
Message-ID: <2cffd392cfbf6a777f5196e6c5b36f52@mail.greenhills-it.co.uk>
Hi,
You could try replacing Apache with Nginx, this would reduce your
memory requirements.
Don't know whether it would get it low enough to run reasonably though?
Best Regards
Martin
On 2013-04-26 12:30, Christian Loos wrote:
> Hi Geert,
>
> I have tried this (Apache and MySQL) a few weeks ago and hat to
> switch
> from a Micro to a Small instance because the 613 MiB RAM of the Micro
> instance isn't enough.
>
> Chris
>
> Am 25.04.2013 16:50, schrieb Geert Claes:
>> Has anyone successfully been able to install and configure RT
>> Request Tracker
>> on a AWS EC2 Micro instance?
>>
>> A "Jeevan" seems to have succeeded but on a "Small" rather than a
>> "Micro"
>> (read free) EC2 instance:
>>
>> http://geekospace.com/installing-and-configuring-request-tracker-4-on-ubuntu-aws-ec2-instance
>>
>> I also found these:
>>
>> http://serverfault.com/questions/435458/apache-taking-up-a-lot-of-cpu-while-running-request-tracker4
>> (bhowmik)
>>
>> http://superuser.com/questions/518776/request-tracker-on-ubuntu-12-04-lts-ec2-instance-with-rds
>> (again Jeevan?)
>>
>> Maybe one of the seasoned RT admins here could share a free
>> Community
>> Contributed AMI (Amazon Machine Image) so that people can have a
>> play around
>> with RT quickly?
>>
>> Anyhow, just a thought
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://requesttracker.8502.n7.nabble.com/RT-on-AWS-EC2-Micro-as-a-Community-AMI-tp53615.html
>> Sent from the Request Tracker - Dev mailing list archive at
>> Nabble.com.
>>
>
>
> !DSPAM:9,517a667833235787813377!
From falcone at bestpractical.com Fri Apr 26 11:45:40 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Fri, 26 Apr 2013 11:45:40 -0400
Subject: [rt-devel] RT 4.0.12rc1 ready for testing
Message-ID: <20130426154540.GA1726@jibsheet.com>
RT 4.0.12rc1 is now available for testing.
http://download.bestpractical.com/pub/rt/devel/rt-4.0.12rc1.tar.gz
http://download.bestpractical.com/pub/rt/devel/rt-4.0.12rc1.tar.gz.sig
SHA1 sums
e07c7e8a78f605b44ed6dce855cb472ae0f31c05 rt-4.0.12rc1.tar.gz
6d8acbe21e249171f7ab4aa5b7e277b40f98adae rt-4.0.12rc1.tar.gz.sig
This release of RT repairs a regression in 4.0.11. If you use the Rich
Text Editor, the red background on Reply was missing due to the update
of CKEditor to support IE10. It also includes a database upgrade, so
please make sure to run 'make upgrade-database'.
Features
* Date and DateTime Custom Fields now have the same 'smart' date parsing
that core RT date fields have.
* Improved logging when the sending of a Correspond or Comment fails.
* The Quick Search preferences page now has Select/Clear All buttons.
* Unprivileged users can now change Language and Time Zone.
* Warn MySQL users if their max_allowed_packet is dangerously low.
Bugfixes
* Repair 4.0.11 regression where red background on Reply with the
RichText Editor was lost.
* Quiet warnings in the verbose user format.
* Allow changing the case of a Group's name (prevented by earlier code
stopping you from having two groups with the same name).
* Allow changing the case of a Class's name.
* Avoid warnings when using empty Templates.
* Update our InnoDB checks for MySQL 5.6 compatibility.
* Clarification of when SetOutgoingMailFrom and OverrideOutgoingMailFrom
are available.
* Improve layout of collection lists in IE.
* Fix Attach more files button in Self Service.
* Set caching headers on autocomplete endpoints.
* Restore and improve prematurely deleted documentation for
DontSearchFileAttachments.
* Correct the encoding of Dashboard email Subject headers.
* Fix the default roles on User->WatchedQueues.
* Document the need to grant SeeCustomField in UPGRADING-3.4.
* Nudge menus below the shadows in aileron.
* Fix missing headers and a syntax error in the
/REST/1.0/attachment/NN endpoint.
Localization
* Improve the display of numbers when using the French localization.
* Built in components and searches (such as Bookmarked Tickets) are now
localizable.
* Use PostgreSQL error codes in the full-text-indexer instead of
matching on error messages that may be in a non-english language.
* Localize 'Dashboard' during creation.
* Mark 'Modify this user' as localizable.
Developer
* Test can now be run against a remote DB server.
* Install etc/upgrade to make some rt-setup-database actions easier
without requiring access to the install directory.
* RT_TEST_PARALLEL_NUM controls the -j param in make parallel-test
* Work around a git bug in git archive when packaging releases.
This caused the third party sources to bloat the 4.0.11 tarball.
* Fix examples in the CreateTickets documentation.
* RT Ticket types (ticket, approval, reminder) are now always forced to
lower case.
* Allow the use of 'NOT IN' in Limits (assuming a new enough
DBIx::SearchBuilder).
A complete changelog is available from git by running:
git log rt-4.0.11..rt-4.0.12rc1
or visiting
https://github.com/bestpractical/rt/compare/rt-4.0.11...rt-4.0.12rc1
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From odhiambo at gmail.com Fri Apr 26 11:59:04 2013
From: odhiambo at gmail.com (Odhiambo Washington)
Date: Fri, 26 Apr 2013 18:59:04 +0300
Subject: [rt-devel] RT 4.0.12rc1 ready for testing
In-Reply-To: <20130426154540.GA1726@jibsheet.com>
References: <20130426154540.GA1726@jibsheet.com>
Message-ID:
I have installed this over my 4.0.11 and when restarting apache, I get
this warning:
[root at jaribu] ~/Tools/RT/rt-4.0.12rc1# /usr/local/etc/rc.d/apache22 stop
Stopping apache22.
Waiting for PIDS: 83534.
[root at jaribu] ~/Tools/RT/rt-4.0.12rc1# /usr/local/etc/rc.d/apache22 start
Performing sanity check on apache22 configuration:
[Fri Apr 26 15:57:47 2013] [warning]: max_allowed_packet is set to
1.0M, which limits the maximum attachment or email size that RT can
process. Consider adjusting MySQL's max_allowed_packet setting.
(/opt/rt4/sbin/../lib/RT/Handle.pm:296)
Syntax OK
Starting apache22.
[Fri Apr 26 15:57:48 2013] [warning]: max_allowed_packet is set to
1.0M, which limits the maximum attachment or email size that RT can
process. Consider adjusting MySQL's max_allowed_packet setting.
(/opt/rt4/sbin/../lib/RT/Handle.pm:296)
[root at jaribu] ~/Tools/RT/rt-4.0.12rc1#
However,
[root at jaribu] ~/Tools/RT/rt-4.0.12rc1# grep max_allowe /etc/my.cnf
max_allowed_packet = 5M
max_allowed_packet = 16M
On 26 April 2013 18:45, Kevin Falcone wrote:
> RT 4.0.12rc1 is now available for testing.
>
> http://download.bestpractical.com/pub/rt/devel/rt-4.0.12rc1.tar.gz
> http://download.bestpractical.com/pub/rt/devel/rt-4.0.12rc1.tar.gz.sig
>
> SHA1 sums
> e07c7e8a78f605b44ed6dce855cb472ae0f31c05 rt-4.0.12rc1.tar.gz
> 6d8acbe21e249171f7ab4aa5b7e277b40f98adae rt-4.0.12rc1.tar.gz.sig
>
> This release of RT repairs a regression in 4.0.11. If you use the Rich
> Text Editor, the red background on Reply was missing due to the update
> of CKEditor to support IE10. It also includes a database upgrade, so
> please make sure to run 'make upgrade-database'.
>
> Features
> * Date and DateTime Custom Fields now have the same 'smart' date parsing
> that core RT date fields have.
> * Improved logging when the sending of a Correspond or Comment fails.
> * The Quick Search preferences page now has Select/Clear All buttons.
> * Unprivileged users can now change Language and Time Zone.
> * Warn MySQL users if their max_allowed_packet is dangerously low.
>
> Bugfixes
> * Repair 4.0.11 regression where red background on Reply with the
> RichText Editor was lost.
> * Quiet warnings in the verbose user format.
> * Allow changing the case of a Group's name (prevented by earlier code
> stopping you from having two groups with the same name).
> * Allow changing the case of a Class's name.
> * Avoid warnings when using empty Templates.
> * Update our InnoDB checks for MySQL 5.6 compatibility.
> * Clarification of when SetOutgoingMailFrom and OverrideOutgoingMailFrom
> are available.
> * Improve layout of collection lists in IE.
> * Fix Attach more files button in Self Service.
> * Set caching headers on autocomplete endpoints.
> * Restore and improve prematurely deleted documentation for
> DontSearchFileAttachments.
> * Correct the encoding of Dashboard email Subject headers.
> * Fix the default roles on User->WatchedQueues.
> * Document the need to grant SeeCustomField in UPGRADING-3.4.
> * Nudge menus below the shadows in aileron.
> * Fix missing headers and a syntax error in the
> /REST/1.0/attachment/NN endpoint.
>
> Localization
> * Improve the display of numbers when using the French localization.
> * Built in components and searches (such as Bookmarked Tickets) are now
> localizable.
> * Use PostgreSQL error codes in the full-text-indexer instead of
> matching on error messages that may be in a non-english language.
> * Localize 'Dashboard' during creation.
> * Mark 'Modify this user' as localizable.
>
> Developer
> * Test can now be run against a remote DB server.
> * Install etc/upgrade to make some rt-setup-database actions easier
> without requiring access to the install directory.
> * RT_TEST_PARALLEL_NUM controls the -j param in make parallel-test
> * Work around a git bug in git archive when packaging releases.
> This caused the third party sources to bloat the 4.0.11 tarball.
> * Fix examples in the CreateTickets documentation.
> * RT Ticket types (ticket, approval, reminder) are now always forced to
> lower case.
> * Allow the use of 'NOT IN' in Limits (assuming a new enough
> DBIx::SearchBuilder).
>
> A complete changelog is available from git by running:
> git log rt-4.0.11..rt-4.0.12rc1
> or visiting
> https://github.com/bestpractical/rt/compare/rt-4.0.11...rt-4.0.12rc1
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
"I can't hear you -- I'm using the scrambler."
From falcone at bestpractical.com Fri Apr 26 12:33:12 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Fri, 26 Apr 2013 12:33:12 -0400
Subject: [rt-devel] RT 4.0.12rc1 ready for testing
In-Reply-To:
References: <20130426154540.GA1726@jibsheet.com>
Message-ID: <20130426163312.GB1726@jibsheet.com>
On Fri, Apr 26, 2013 at 06:59:04PM +0300, Odhiambo Washington wrote:
> [Fri Apr 26 15:57:47 2013] [warning]: max_allowed_packet is set to
> 1.0M, which limits the maximum attachment or email size that RT can
> process. Consider adjusting MySQL's max_allowed_packet setting.
> (/opt/rt4/sbin/../lib/RT/Handle.pm:296)
> [root at jaribu] ~/Tools/RT/rt-4.0.12rc1# grep max_allowe /etc/my.cnf
> max_allowed_packet = 5M
> max_allowed_packet = 16M
Connect to the mysql rt database as your rt_user and show what
show variables like 'max_allowed_packet';
returns?
Thanks
-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From odhiambo at gmail.com Fri Apr 26 12:36:06 2013
From: odhiambo at gmail.com (Odhiambo Washington)
Date: Fri, 26 Apr 2013 19:36:06 +0300
Subject: [rt-devel] RT 4.0.12rc1 ready for testing
In-Reply-To: <20130426163312.GB1726@jibsheet.com>
References: <20130426154540.GA1726@jibsheet.com>
<20130426163312.GB1726@jibsheet.com>
Message-ID:
[root at jaribu] ~/Tools/RT/rt-4.0.12rc1# grep max_allo vars.txt
max_allowed_packet 1048576
slave_max_allowed_packet 1073741824
On 26 April 2013 19:33, Kevin Falcone wrote:
> On Fri, Apr 26, 2013 at 06:59:04PM +0300, Odhiambo Washington wrote:
>> [Fri Apr 26 15:57:47 2013] [warning]: max_allowed_packet is set to
>> 1.0M, which limits the maximum attachment or email size that RT can
>> process. Consider adjusting MySQL's max_allowed_packet setting.
>> (/opt/rt4/sbin/../lib/RT/Handle.pm:296)
>> [root at jaribu] ~/Tools/RT/rt-4.0.12rc1# grep max_allowe /etc/my.cnf
>> max_allowed_packet = 5M
>> max_allowed_packet = 16M
>
> Connect to the mysql rt database as your rt_user and show what
> show variables like 'max_allowed_packet';
> returns?
>
> Thanks
>
> -kevin
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
"I can't hear you -- I'm using the scrambler."
From falcone at bestpractical.com Fri Apr 26 12:41:24 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Fri, 26 Apr 2013 12:41:24 -0400
Subject: [rt-devel] RT 4.0.12rc1 ready for testing
In-Reply-To:
References: <20130426154540.GA1726@jibsheet.com>
<20130426163312.GB1726@jibsheet.com>
Message-ID: <20130426164124.GC1726@jibsheet.com>
On Fri, Apr 26, 2013 at 07:36:06PM +0300, Odhiambo Washington wrote:
> [root at jaribu] ~/Tools/RT/rt-4.0.12rc1# grep max_allo vars.txt
> max_allowed_packet 1048576
> slave_max_allowed_packet 1073741824
So - mysqld is still running with a 1MB max_allowed_packet according
to that.
> >> [root at jaribu] ~/Tools/RT/rt-4.0.12rc1# grep max_allowe /etc/my.cnf
> >> max_allowed_packet = 5M
> >> max_allowed_packet = 16M
What sections are these max_allowed_packet's defined in?
I'd guess that one is in the [mysqldump] section, not so sure about
the 5M one, possibly [safe_mysqld] rather than [mysqld] or vice-versa.
-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From odhiambo at gmail.com Fri Apr 26 12:47:16 2013
From: odhiambo at gmail.com (Odhiambo Washington)
Date: Fri, 26 Apr 2013 19:47:16 +0300
Subject: [rt-devel] RT 4.0.12rc1 ready for testing
In-Reply-To: <20130426164124.GC1726@jibsheet.com>
References: <20130426154540.GA1726@jibsheet.com>
<20130426163312.GB1726@jibsheet.com>
<20130426164124.GC1726@jibsheet.com>
Message-ID:
max_allowed_packet variables are in [mysqld] and [mysqldump] sections of my.cnf.
I've restarted mysqld but the values appear to be persistent, somehow...
On 26 April 2013 19:41, Kevin Falcone wrote:
> On Fri, Apr 26, 2013 at 07:36:06PM +0300, Odhiambo Washington wrote:
>> [root at jaribu] ~/Tools/RT/rt-4.0.12rc1# grep max_allo vars.txt
>> max_allowed_packet 1048576
>> slave_max_allowed_packet 1073741824
>
> So - mysqld is still running with a 1MB max_allowed_packet according
> to that.
>
>> >> [root at jaribu] ~/Tools/RT/rt-4.0.12rc1# grep max_allowe /etc/my.cnf
>> >> max_allowed_packet = 5M
>> >> max_allowed_packet = 16M
>
> What sections are these max_allowed_packet's defined in?
> I'd guess that one is in the [mysqldump] section, not so sure about
> the 5M one, possibly [safe_mysqld] rather than [mysqld] or vice-versa.
>
> -kevin
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
"I can't hear you -- I'm using the scrambler."
From falcone at bestpractical.com Fri Apr 26 13:34:30 2013
From: falcone at bestpractical.com (Kevin Falcone)
Date: Fri, 26 Apr 2013 13:34:30 -0400
Subject: [rt-devel] RT 4.0.12rc1 ready for testing
In-Reply-To:
References: <20130426154540.GA1726@jibsheet.com>
<20130426163312.GB1726@jibsheet.com>
<20130426164124.GC1726@jibsheet.com>
Message-ID: <20130426173430.GD1726@jibsheet.com>
On Fri, Apr 26, 2013 at 07:47:16PM +0300, Odhiambo Washington wrote:
> max_allowed_packet variables are in [mysqld] and [mysqldump] sections of my.cnf.
> I've restarted mysqld but the values appear to be persistent, somehow...
Depending on how mysql is started from the init script, you can
sometimes need to put things in safe_mysqld vs mysqld (although
generally I see it the other way around and [mysqld] is the safest
place to put things).
Check other customizations you've made to the [mysqld] section and see
if they're showing up in show variables?
-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL:
From trs at bestpractical.com Fri Apr 26 14:06:56 2013
From: trs at bestpractical.com (Thomas Sibley)
Date: Fri, 26 Apr 2013 11:06:56 -0700
Subject: [rt-devel] RT on AWS EC2 Micro as a Community AMI?
In-Reply-To: <2cffd392cfbf6a777f5196e6c5b36f52@mail.greenhills-it.co.uk>
References: <1366901457238-53615.post@n7.nabble.com>
<517A7376.5090108@netsandbox.de>
<2cffd392cfbf6a777f5196e6c5b36f52@mail.greenhills-it.co.uk>
Message-ID: <517AC240.4000007@bestpractical.com>
On 04/26/2013 04:49 AM, Martin Wheldon wrote:
> You could try replacing Apache with Nginx, this would reduce your memory
> requirements.
> Don't know whether it would get it low enough to run reasonably though?
Apache/Nginx will definitely need tuning. You'd probably do best to run
RT as an external process, either FastCGI or a pure-Perl backend
(Starman/Starlet) which the frontend proxies.
You'll need to tune all of the above down to a reasonable process limit
so that it all fits without swapping. Should be possible, but you'll be
restricted in how many clients you can serve at once. Keep in mind that
each incoming email is also an HTTP client.
From ruz at bestpractical.com Fri Apr 26 15:04:24 2013
From: ruz at bestpractical.com (Ruslan Zakirov)
Date: Fri, 26 Apr 2013 23:04:24 +0400
Subject: [rt-devel] RT on AWS EC2 Micro as a Community AMI?
In-Reply-To: <1366901457238-53615.post@n7.nabble.com>
References: <1366901457238-53615.post@n7.nabble.com>
Message-ID:
Hi,
Installed on micro with nginx and external forking fcgi (10 processes - ok
to serve 100 user with medium activity) and even a bit of memory left. It's
with default RT config, for example loading less translations helps a lot.
It was also 64 bit system, 32 bit in this case would give another memory
win.
With some tricks it took less then two hours to setup EC2 ubuntu instance,
RDS mysql instance, compile and install custom perl, all perl modules from
CPAN, install nginx and configure web server. The only thing I didn't do
today is registration to access AWS.
On Thu, Apr 25, 2013 at 6:50 PM, Geert Claes wrote:
> Has anyone successfully been able to install and configure RT Request
> Tracker
> on a AWS EC2 Micro instance?
>
> A "Jeevan" seems to have succeeded but on a "Small" rather than a "Micro"
> (read free) EC2 instance:
>
> http://geekospace.com/installing-and-configuring-request-tracker-4-on-ubuntu-aws-ec2-instance
>
> I also found these:
>
> http://serverfault.com/questions/435458/apache-taking-up-a-lot-of-cpu-while-running-request-tracker4
> (bhowmik)
>
> http://superuser.com/questions/518776/request-tracker-on-ubuntu-12-04-lts-ec2-instance-with-rds
> (again Jeevan?)
>
> Maybe one of the seasoned RT admins here could share a free Community
> Contributed AMI (Amazon Machine Image) so that people can have a play
> around
> with RT quickly?
>
> Anyhow, just a thought
>
>
>
>
>
> --
> View this message in context:
> http://requesttracker.8502.n7.nabble.com/RT-on-AWS-EC2-Micro-as-a-Community-AMI-tp53615.html
> Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
>
--
Best regards, Ruslan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From geert.wl.claes at gmail.com Mon Apr 29 03:49:44 2013
From: geert.wl.claes at gmail.com (Geert Claes)
Date: Mon, 29 Apr 2013 00:49:44 -0700 (PDT)
Subject: [rt-devel] RT on AWS EC2 Micro as a Community AMI?
In-Reply-To:
References: <1366901457238-53615.post@n7.nabble.com>
Message-ID: <1367221784835-53672.post@n7.nabble.com>
--
View this message in context: http://requesttracker.8502.n7.nabble.com/RT-on-AWS-EC2-Micro-as-a-Community-AMI-tp53615p53672.html
Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
From geert.wl.claes at gmail.com Mon Apr 29 03:52:00 2013
From: geert.wl.claes at gmail.com (Geert Claes)
Date: Mon, 29 Apr 2013 00:52:00 -0700 (PDT)
Subject: [rt-devel] RT on AWS EC2 Micro as a Community AMI?
In-Reply-To:
References: <1366901457238-53615.post@n7.nabble.com>
Message-ID: <1367221920556-53674.post@n7.nabble.com>
Ruslan Zakirov-2 wrote
> With some tricks it took less then two hours to setup EC2 ubuntu instance,
> RDS mysql instance, compile and install custom perl, all perl modules from
> CPAN, install nginx and configure web server. The only thing I didn't do
> today is registration to access AWS.
Excellent! Just let us know here when a Community Contributed AMI is
available.
Thanks heaps!
--
View this message in context: http://requesttracker.8502.n7.nabble.com/RT-on-AWS-EC2-Micro-as-a-Community-AMI-tp53615p53674.html
Sent from the Request Tracker - Dev mailing list archive at Nabble.com.
From geert.wl.claes at gmail.com Mon Apr 29 05:02:45 2013
From: geert.wl.claes at gmail.com (Geert Claes)
Date: Mon, 29 Apr 2013 02:02:45 -0700 (PDT)
Subject: [rt-devel] New RT-theme: "love at first sight" maker theme
In-Reply-To:
References:
Message-ID: <1367226165713-53675.post@n7.nabble.com>
Hi ?kos, I only joined the RT forum here recently and just noticed your post.
We actually are looking at doing the same thing, make the RT UI (and UX)
look-n-feel better.
How is your initiative going (we haven't started yet)? Are you using a
front-end framework at all?
http://requesttracker.8502.n7.nabble.com/rt-devel-RT-Tracker-styling-look-n-feel-td53550.html
akos.torok at docca.hu wrote
> Now we would like to make a new theme, something that makes non-tech users
> fall in love at first sight. ((And we will release some new plugins like:
> - drag-n-drop organizing tickets (among saved searches),
> - per queue customizable ticket look-and-feel.))
>
> Our goal is to make RT more desirable for everyday people.
--
View this message in context: http://requesttracker.8502.n7.nabble.com/rt-devel-New-RT-theme-love-at-first-sight-maker-theme-tp53190p53675.html
Sent from the Request Tracker - Dev mailing list archive at Nabble.com.