Hello,
I am getting error, when I access the survey URL from the frontend as customer.
Here is the error I get
Backend ERROR: OTRS-CGI-25 Perl: 5.10.1 OS: linux Time: Tue Oct 28 16:01:00 2014 Message: Module Kernel/Modules/PublicSurveyPublicSurveyKey558aea9eeed0a73e2c52299fda99f2ba.pm not found/could not be loaded! RemoteAddress: 123.63.153.97 RequestURI: /otrs/public.pl?Action=PublicSurvey%3bPublicSurveyKey=558aea9eeed0a73e2c52299fda99f2ba Traceback (2018): Module: Kernel::System::Web::InterfacePublic::Run (OTRS 3.3.9) Line: 188 Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_public_2epl::handler (unknown version) Line: 41 Module: (eval) (v1.99) Line: 204 Module: ModPerl::RegistryCooker::run (v1.99) Line: 204 Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 170 Module: ModPerl::Registry::handler (v1.99) Line: 31
Please let me know how I can fix this.
Thanks,
Raghu
Fatal Error accessing Survey URL in Frontend
Moderator: crythias
-
- Znuny newbie
- Posts: 22
- Joined: 27 Aug 2014, 19:25
- Znuny Version: 3.3.8
- Real Name: Raghuraman
Re: Fatal Error accessing Survey URL in Frontend
Hello,
I figured out where the problem is, it was with the URL
otrs/public.pl?Action=PublicSurvey%3bPublicSurveyKey=558aea9eeed0a73e2c52299fda99f2ba
I found that the URL got changed, meaning ";" was replaced with "%3b" and when I manually changed the URL it worked well.
So, now I need to figure out how this semicolon is changing. Any help here is much appreciated.
Thanks,
Raghu
I figured out where the problem is, it was with the URL
otrs/public.pl?Action=PublicSurvey%3bPublicSurveyKey=558aea9eeed0a73e2c52299fda99f2ba
I found that the URL got changed, meaning ";" was replaced with "%3b" and when I manually changed the URL it worked well.
So, now I need to figure out how this semicolon is changing. Any help here is much appreciated.
Thanks,
Raghu
Re: Fatal Error accessing Survey URL in Frontend
Just ran into this issue as well, replacing the semicolon with an ampersand in both the survey email template and by manually editing the URL in browser fixed the issue.
I think it may be webserver issue, because a little googlefu tells me that using ; instead of & should be supported but not all webservers do, it may be a setting.
Regards,
Elliott
I think it may be webserver issue, because a little googlefu tells me that using ; instead of & should be supported but not all webservers do, it may be a setting.
Regards,
Elliott