Hi, there
We have to patch some files of OTRS in Kernel/Modules, Kernel/Language and Kernel/System directories at our site. But this drives to making us patch/re-patch and fix our patchset as soon as we decide to upgrade.
For example:
We need to patch Kernel/Modules/AgentTicketForward.pm and as a result - change 'sub Form' definition by some additional lines
Or even more: Kernel/System/Ticket.pm have several 'sub's redefined.
Is there any possibility to hack-out system modules as an external module? Reading API docs didn't clarify that. Is there any tutorial on such a hack development?
Module-driven customizations
Re: Module-driven customizations
Hi,
what version of OTRS are you using. There is a custom feature now for overwriting Kernel/System and Kernel/Modules Features starting from 3.0...
Language Files should never be overwritten as there is the possibility to create files like en_Custom.pm which will will overwrite english words..
what version of OTRS are you using. There is a custom feature now for overwriting Kernel/System and Kernel/Modules Features starting from 3.0...
Language Files should never be overwritten as there is the possibility to create files like en_Custom.pm which will will overwrite english words..
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
Re: Module-driven customizations
We are on 2.4.7 now and planning to upgrade to version 3.
As of reading OTRS-Dev docs these customizations should and could be implemented as PackageNamespase::PackagenameCustom. Please, point me to the appropriate documentation section that describes customizations if I'm wrong.
As for Language we need to slightly customize Kernel::Language package as itself and will use ${langname}_Custom.pm files for i18n strings definition as this is possible. But can we enpack customizations we make to Kernel::Language into custom package?
As of reading OTRS-Dev docs these customizations should and could be implemented as PackageNamespase::PackagenameCustom. Please, point me to the appropriate documentation section that describes customizations if I'm wrong.
As for Language we need to slightly customize Kernel::Language package as itself and will use ${langname}_Custom.pm files for i18n strings definition as this is possible. But can we enpack customizations we make to Kernel::Language into custom package?