Argh.. I have the code in place (actually, improved upon the code by
replicating some of the detection code from the original plugin), and I
can see it is working via some test code, but the commands still show up
in the content of the ticket.
So.. that leads to the question: where did you put you
On Thu, Aug 6, 2009 at 16:38, Rich West wrote:
> Being unfamiliar with how to drop things in the local/lib tree, is the
> process to simply create a file of the same name and the contents are
> added? or does the file entirely replace the original?
Local overrides original. Appending would raise a
Being unfamiliar with how to drop things in the local/lib tree, is the
process to simply create a file of the same name and the contents are
added? or does the file entirely replace the original?
-Rich
On 08/03/2009 10:20 AM, Andreas Ittgenshorst wrote:
> To remove the commands I added a few l
To remove the commands I added a few lines
to /opt/rt3/local/lib/RT/Transaction_Overlay.pm
# Remove quoted signature.
$content =~ s/\n-- \n(.*?)$//s;
+# Remove CommandByMail commands
+my @content = split ("\n",$content);
+my @new_content = ();
+
One item that should be documented is that this extension cannot handle
spaces in the custom field names. Spaces causes it to break. :(
-Rich
On 07/23/2009 10:56 AM, Rich West wrote:
The extension works rather well once you get past the caveats of the
formatting. With regard to the slimness
Another question, though.. is there a way to strip out the email
commands from the content of the ticket as it shows up in Request Tracker?
-Rich
On 07/23/2009 10:56 AM, Rich West wrote:
The extension works rather well once you get past the caveats of the
formatting. With regard to the slimne
The extension works rather well once you get past the caveats of the
formatting. With regard to the slimness of the documentation, it
doesn't mention those 'simple rules', which forced me to comb through
the code (which is rather clean) to determine the proper formatting
which led to the disco
2009 03:14:49 PM -0400
Subject: [rt-users] Commands by Email
Way back in the day, when I was heavily involved in the development of
RT, there was a way to send commands in to RT to set some of the
metadata (queue, owner, status, etc).
Now that the place I am at is heavily entrenched in to RT 3.8
What's so slim in the doc?
http://search.cpan.org/~falcone/RT-Extension-CommandByMail-0.07/lib/RT/Extension/CommandByMail.pm
http://search.cpan.org/~falcone/RT-Extension-CommandByMail-0.07/lib/RT/Interface/Email/Filter/TakeAction.pm#COMMANDS_commands_below
Simple rules: no html, no empty lines, c
Way back in the day, when I was heavily involved in the development of
RT, there was a way to send commands in to RT to set some of the
metadata (queue, owner, status, etc).
Now that the place I am at is heavily entrenched in to RT 3.8.4 and our
separate front-end form submission system is near
On Tue 14.Oct'08 at 13:00:10 +0200, Richard Hartmann wrote:
> Hi all,
>
> I thought RT 3.8.x had email commands incorporated and does not need
> CommandByMail, any more. Yet, I can't see anything in the docs/wiki
> about it. I don't want to enable the plugin without checking if that is
> the ri
Hi all,
I thought RT 3.8.x had email commands incorporated and does not need
CommandByMail, any more. Yet, I can't see anything in the docs/wiki
about it. I don't want to enable the plugin without checking if that is
the right way to go.
So, does RT 3.8.x come with CommandByMail or not?
Thanks,
12 matches
Mail list logo
