y a successful enabling of the user.
Is this normal for RT::Authen::ExternalAuth, or did I break something?
James Zuelow
Systems Operations Manager
City and Borough of Juneau MIS
(907) 586-0236
===
(1)
(probably get munged by word wrap)
RT::Authen::ExternalAuth version 0.9
Modified:
I started testing 4.0.1 I had mod_speling enabled to fix capitalization,
and that broke the RT menus.
James Zuelow
Systems Operations Manager
City and Borough of Juneau MIS
(907) 586-0236
2011 Training: http://bestpractical.com/services/training.html
at 10:46:48PM +, Roberto Hoyle wrote:
>> James Zuelow ci.juneau.ak.us> writes:
>>
>>> You don't, by chance, have mod_speling enabled do you?
>>>
>>> When I started testing 4.0.1 I had mod_speling enabled to fix
>>> capitalization, a
is undefined
Line: 128
Char: 113
Code: 0
URI:
http://rt.cbj.local/rt/NoAuth/js/squished-0d827a85fc350fae22bf999015a8d153.js
======
At that point, I am out of my depth.
James Zuelow
Systems Operations Manager
City and Borough of Juneau MIS
(907) 586-0236
RT
Original Message
From: rt-users-boun...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf
Of Kevin Falcone
Sent: Thursday, August 11, 2011 8:42 AM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Missing Menu on Left
>
> The path we request i
attribute (
> ExternalAuthId ) is
> null or incorrectly defined in the attr_map for this service (
> Active_Directory )
Your AD schema does not have an "ExternalAuthID" field in it.
You have ExternalAuthID mapped to sAMAccountName. What happens if you try:
'attr_match
I've got an RT 4.0.2 install that the tech staff has been working with.
However we've noticed that Internet Explorer 8 is extremely slow when browsing,
and can hang completely.
For example, when viewing a ticket with this URL:
/rt/Ticket/History.html?id=FOO
IE8 can take up to 90 seconds to ret
I'm having trouble setting up the fulltext index on a Debian installation.
Admittedly this is a Wheezy installation, not Jessie as we wanted to track a
newer version of rt4, so some things may be broken. Hopefully the freeze comes
soon though.
Package versions at the moment are MySQL 5.6.30
> -Original Message-
> From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of
> Jim Brandt
> Sent: Friday, October 14, 2016 4:37 AM
> To: rt-users@lists.bestpractical.com
> Subject: Re: [rt-users] rt-setup-fulltext-index dropped DB connections with
> MySQL
>
> We h
>
> I will experiment with Debian Snapshots and see if I can roll back MySQL to
> 5.6.28, and report what happens.
My Debian Snapshots foo is a little weak, so I ended up with MySQL 5.6.27-2
instead of 5.6.28.
However, the rt-setup-fulltext-index script ran perfectly at that point. I
will pin
ian packages for everything, which had JSON at 3.02 and
JSON::XS at 2.98 after the upgrade. Upgrading JSON::XS with CPAN worked and
now CPAN says that JSON and JSON::XS packages are both up to date (3.02)
The rest of the system works as advertised, just not the web UI.
James Zuelow
System
$s =~ s{/}{\\/}g;
> return $s;
> }
Now the question remains - am I silently breaking something else with that
little hack?
I know just enough Perl to be dangerous, so freely admit I'm not aware of all
of the possible ramifications of the edit.
James Zuelow
Systems Operation
I had success by using Debian’s snapshot server and downgrading MySQL 5.6.27-2
and then running rt-setup-fulltext-index. That worked perfectly.
You can safely “upgrade” back to your current version after the setup script
runs – the fulltext index maintenance script will run fine.
If downgradin
, November 14, 2016 1:33 PM
To: James Zuelow
Cc: martin.whel...@greenhills-it.co.uk; rt-users
Subject: Re: [rt-users] Enabling full text index, getting "MySQL server has
gone away"
For future readers, my own solution was--thankfully--much simpler. Nowhere that
I found in the docs I was read
14 matches
Mail list logo
