Can't write ConfigItem!

[happybrowndog]

After enabling "Manage Customer-Group Relations", and then submitting the form entitled "Edit Config Settings in Framework -> Frontend::Customer", I get a "Can't write ConfigItem" error.

Error Details:
Backend ERROR: OTRS-CGI-10 Perl: 5.8.8 OS: linux Time: Thu Jul 19 09:51:35 2012 Message: Can't write ConfigItem! Traceback (12277): Module: Kernel::Modules::AdminSysConfig::Run (v1.119.2.1) Line: 174 Module: Kernel::System::Web::InterfaceAgent::Run (v1.64) Line: 868 Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 46 Module: (eval) (v1.90) Line: 204 Module: ModPerl::RegistryCooker::run (v1.90) Line: 204 Module: ModPerl::RegistryCooker::default_handler (v1.90) Line: 170 Module: ModPerl::Registry::handler (v1.99) Line: 31

I googled for an answer, but only found something in German. I took basic German in college, so I could kind of understand what they were saying.... anyways, it was to run "otrs.SetPermissions.pl". But when I did, it asked for parameters I had no idea what to do with.

Is this the right way to solve this problem? If so, what should I plug in as parameters?

If not, what should I do instead?

And why does managing customer-group relations give me the interface to create the customer front-end?? I would think it would be an interface to tie the customer to the groups I've already defined.

[crythias]

anyways, it was to run "otrs.SetPermissions.pl". But when I did, it asked for parameters I had no idea what to do with.

Since I don't know your version of OTRS, I can only guess at the answer.

Read the INSTALL file. It's likely one of:

7) File Permissions:
-----------------
File permissions need to be adjusted to allow OTRS to read and write files:

shell> bin/otrs.SetPermissions.pl --otrs-user=<OTRS_USER> --web-user=<WEBSERVER_USER> [--otrs-group=<OTRS_GROUP>] [--web-group=<WEB_GROUP>] <OTRS_HOME>

For example:
Web server which runs as the OTRS user:

shell> bin/otrs.SetPermissions.pl --otrs-user=otrs --web-user=otrs /opt/otrs

Webserver with wwwrun user (e. g. SUSE):

shell> bin/otrs.SetPermissions.pl --otrs-user=otrs --web-user=wwwrun /opt/otrs

Webserver with apache user (e. g. Red Hat, CentOS):

shell> bin/otrs.SetPermissions.pl --otrs-user=otrs --web-user=apache --otrs-group=apache --web-group=apache /opt/otrs

Webserver with www-data user (e. g. Debian, Ubuntu):

shell> bin/otrs.SetPermissions.pl --otrs-user=otrs --web-user=www-data --otrs-group=www-data --web-group=www-data /opt/otrs

---
(You might want to make setPerm.sh file in /opt/otrs that holds the one that works for you to have it handy.)

And why does managing customer-group relations give me the interface to create the customer front-end?? I would think it would be an interface to tie the customer to the groups I've already defined.

It's the dev's choice. Basically, it's something that applies to a customer, in the framework of dealing with a customer, and applies to security in a Customer's front end.
viewtopic.php?f=60&t=7531 (Info on Customer Groups)
Also, don't use Customer Based Queues. viewtopic.php?f=53&t=16064

[happybrowndog]

Thanks for your reply. By the way I am on OTRS 3.1.6.
I'll try your suggestions shortly (on Debian).