On 4/13/18 9:33 AM, Dominic Hargreaves wrote: > Control: forwarded -1 > https://issues.bestpractical.com/Ticket/Display.html?id=3301 > > On Fri, Apr 13, 2018 at 11:41:20AM +0200, Daniel Baumann wrote: >> When upgrading from 4.4.1-5 to 4.4.2-1 (and subsequently to 4.4.2-2), we >> noticed the follwowing regression: >> >> * Logging in as root, going to Admin / Tools / System Configuration, >> a page with the following message is shown instead of the >> configuration page: >> >> "An internal RT error has occurred. Your administrator can find more >> details in RT's log files." >> >> * The logfile shows: >> >> ---snip--- >>  [Fri Apr 13 09:21:20 2018] [error]: Can't store REGEXP items at >> /usr/share/request-tracker4/lib/RT/Config.pm line 1521. > > Hi, > > This means that some part of your configuration which is being obfuscated > for display uses regexps. There is an issue in the upstream bugtracker > about this and a candidate fix in upstream's repo. > > Shawn, can you say what the status of this is? Are there known > issues which have lead to it not yet being merged?
Hi Dom, We're looking at this branch as a potential fix since it covers both REGEXP and CODE in configuration. https://github.com/bestpractical/rt/tree/4.4/config-clone-error Right now it just needs some testing and code review. We should be able to merge it soon. Jim > > Cheers, > Dominic. > >  <https://issues.bestpractical.com/Ticket/Display.html?id=33019> >  <https://github.com/bestpractical/rt/tree/4.4/config-error> > -- Jim Brandt Director, Product and Engineering Best Practical Solutions