Yep, like I commented it's easier to make a single line change to the
Defaults.pm file than to copy a whole array structure into Config.pm
and then risk losing "new" functionality when the array in Defaults.pm
is updated. I have a diff file which I use to reapply only the changes
I made.
In particular the option that I modified was to enable the Customer
Company functionality - adding UserCompanyID into the
$Self->{CustomerUser} => Map[] variable. Would be nice if this
functionality was just added into the code permanently, not sure why
it isn't in there with an option in SysConfig to simply enable/disable
it.
Steve
On 21 August 2012 12:12, Martin Gruner <[email protected]> wrote:
> Hi Steven and Israel,
>
> don't edit Defaults.pm. Just make the changes that cannot be done with
> AdminSysConfig in Kernel/Config.pm. This file will never be overwritten
> by a system update.
>
> Regards, mg
>
> Am 21.08.12 12:02, schrieb Steven Carr:
>> So in the /opt/otrs/Kernel/Config/Defaults.pm file you must have some
>> filesystem references from the Windows system. You will need to go
>> through the file and update them to the linux paths.
>>
>> For what it's worth, Kernel/Config/Defaults.pm should *never* be
>> edited (it does say so at the top of the file, though yes even I have
>> manually edited things in this as it's easier than trying to figure
>> out how to put part of an array into Kernel/Config.pm - just means you
>> have to watch out on upgrades incase your custom options get wiped
>> out).
>>
>> So I would probably grab a fresh copy of the Kernel/Config/Defaults.pm
>> from the OTRS source bundle, then do a diff and see what you have in
>> yours that is different to the source one.
>>
>> Steve
>>
>>
>>
>> On 21 August 2012 10:50, Israel Garcia <[email protected]> wrote:
>>> Hi Steve,
>>>
>>> I have done all steps talked in this thread but when run this two scripts
>>> see he error:
>>>
>>> [root@otrs2 var]# /opt/otrs/bin/otrs.RebuildConfig.pl
>>> ERROR: Can't read C:/ARCHIV~1/OTRS/OTRS/RELEASE: No such file or directory
>>> This file is needed by central system parts of OTRS, the system will not
>>> work without this file.
>>> Died at /opt/otrs/Kernel/Config/Defaults.pm line 2183.
>>>
>>> [root@otrs2 var]# /opt/otrs/bin/otrs.DeleteCache.pl
>>> ERROR: Can't read C:/ARCHIV~1/OTRS/OTRS/RELEASE: No such file or directory
>>> This file is needed by central system parts of OTRS, the system will not
>>> work without this file.
>>> Died at /opt/otrs/Kernel/Config/Defaults.pm line 2183.
>>>
>>> I think it's reading a file from the windows server... any idea on how to
>>> solve this...
>>>
>>> Thanks tons..
>>>
>> ---------------------------------------------------------------------
>> OTRS mailing list: otrs - Webpage: http://otrs.org/
>> Archive: http://lists.otrs.org/pipermail/otrs
>> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>>
>
> --
> Martin Gruner
> Senior Developer R&D
>
> OTRS AG
> Europaring 4
> 94315 Straubing
>
> T: +49 (0)6172 681988 0
> F: +49 (0)9421 56818 18
> I: www.otrs.com/
>
> Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.:
> DE256610065
> Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann
> (Vorsitzender), Christopher Kuhn, Sabine Riedel
>
> Verbinden wir uns! OTRS 3.1 schafft einfachere Integration mit
> Drittapplikationen – Für Frühbucher zum Vorzugspreis:
> http://www.otrs.com/index.php?id=2361&L=1
>
> ---------------------------------------------------------------------
> OTRS mailing list: otrs - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/otrs
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
