[rt-users] Update to RT 4.2.1 - JSON error after login

2013-11-22 Thread Dr. Dirk Pape
Hello, I updated my RT test server to 4.2.1 (from 4.2.0) and after - stopping apache - clearing caches - starting apache I see the login page, but when I login RT signals an internal error. In the Log: [13817] [Fri Nov 22 08:17:15 2013] [error]: encountered object '1', but neither

Re: [rt-users] Update to RT 4.2.1 - JSON error after login

2013-11-22 Thread Dr . Dirk Pape
Hello, with some testing I found a workaround for which I don't know, if it is a bug fix. I found, if I patch html/Elements/JavascriptConfig the following way, my server lets me in without error. strange enough my productive server has the same file which is working fine there. I would

Re: [rt-users] Update to RT 4.2.1 - JSON error after login

2013-11-22 Thread Alex Vandiver
On Fri, 2013-11-22 at 09:28 +0100, Dr. Dirk Pape wrote: In the Log: [13817] [Fri Nov 22 08:17:15 2013] [error]: encountered object '1', but neither allow_blessed, convert_blessed nor allow_tags settings are enabled (or TO_JSON/FREEZE method missing) at

Re: [rt-users] Update to RT 4.2.1 - JSON error after login

2013-11-22 Thread Dr . Dirk Pape
Hi Alex, $ perl -MJSON -MModule::Versions::Report -e1 Perl v5.10.1 under linux Modules in memory: attributes v0.09; base v2.18; Carp v1.32; common::sense v3.72; constant v1.27; Exporter v5.68; Exporter::Heavy v5.68; JSON v2.90; JSON::Backend::XS::Supportable; JSON::PP::Boolean;

Re: [rt-users] Update to RT 4.2.1 - JSON error after login

2013-11-22 Thread Alex Vandiver
On Fri, 2013-11-22 at 17:22 +0100, Dr. Dirk Pape wrote: Hi Alex, $ perl -MJSON -MModule::Versions::Report -e1 [snip] I can't replicate your failure with the same versions. Does the following error for you? perl -MJSON -wle 'print JSON::to_json({foo=JSON::true})' - Alex

Re: [rt-users] Update to RT 4.2.1 - JSON error after login

2013-11-22 Thread Dr. Dirk Pape
Hi Alex, it is fine: $ perl -MJSON -wle 'print JSON::to_json({foo=JSON::true})' {foo:true} This is very strange! I updated my productive RT to 4.2.1 now and it does not show the issue even with the JavascriptConfig unpatched. It uses the same perl and PERLLIB. So it must have to do