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
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
RTx::AssetTracker is no longer being maintained and only "work" due to
people hacking it just enough so it does. Assets for RT is maintained
and supported by Best Practical...enough said ;-)
--
Later,
Darin
On Tue, May 20, 2014 at 1:12 PM, Duncan Napier wrote:
> Hi,
>
> Can anyone summarize the
Hi,
Can anyone summarize the advantages of the new Assets for RT versus those of
RTx::AssetTracker? I have been using RT-AssetTracker version 2.0.0b4 on RT
4.0.8 and it seems adequate for most my needs. Can anyone suggest what benefits
I would be able to leverage from switching to the new Asset
Right. So as some point, as close to the place that tries to include that
Rule.pm file, I'd add something similar to::
$RT::Logger->info ( Data::Dumper->Dump([\@INC, \%INC], [qw/inc_path
inc_hash]));
As far as I know, we're still trying to figure out why the existing include
paths are not findin
Looks reasonable on its face.
If it really is 'rule.pm' instead of 'Rule.pm' that that's probably one of
your problems, as the file names are case sensitive on Unix.
Do you have a way to interject some logging code into the logic flow?
Because it's important to know the state of the interpreter...
On 5/20/14 8:21 AM, Kevin Falcone wrote:
On Tue, May 20, 2014 at 09:08:49AM +, Flynn, Peter wrote:
On 19/05/14 15:23, Dominic Hargreaves wrote:
You need to set up some pipe aliases using rt-mailgate:
http://www.bestpractical.com/docs/rt/4.2/rt-mailgate.html
Thanks...I had got that far, bu
On Tue, May 20, 2014 at 09:08:49AM +, Flynn, Peter wrote:
> On 19/05/14 15:23, Dominic Hargreaves wrote:
> > You need to set up some pipe aliases using rt-mailgate:
> > http://www.bestpractical.com/docs/rt/4.2/rt-mailgate.html
>
> Thanks...I had got that far, but it wasn't clear if the aliases
Ok –r—r—r—is the permission for the rule.pm file and root owns it and the
entire directory
drwxr-xr-x is the permission of the top level perl directory and owner by root.
Are these permissions correct?
Thanks,
Mark Sears – CISSP-M.S. IA
Principal Information Security Analyst
[cid:image001.png@01C
> Don't ugprade from version to version.
> Copy the database to a new system. Install RT 4.0.20 and follow all
> the upgrading steps. Then install RTIR 3.0.2 and follow those
> upgrading steps. You will need to have some downtime obviously, but
> you cannot know how much downtime without running
On 19/05/14 15:23, Dominic Hargreaves wrote:
> You need to set up some pipe aliases using rt-mailgate:
> http://www.bestpractical.com/docs/rt/4.2/rt-mailgate.html
Thanks...I had got that far, but it wasn't clear if the aliases you
create in /etc/aliases had to match usernames set up in RT.
///Pe
11 matches
Mail list logo
