|
Author
|
Message
|
|
Eirik Alfstad Johansen
|
Wednesday 10 December 2003 2:44:27 am
Hi, I've come to a point where I need to make changes in the kernel code (specifically in the shop module). So my question is this: Is there any way of modifying the kernel code and still ensuring that my installation remains upgradeable by new ezp distributions? Is it, for instance, possible to create a module extension with the same name and views as the kernel modules, and will these override the kernel modules and views? Thanks in advance ! Sincerely,
Eirik Johansen
Netmaking AS http://www.netmaking.no/
Sincerely,
Eirik Alfstad Johansen
http://www.netmaking.no/
|
|
Marco Zinn
|
Wednesday 10 December 2003 12:49:01 pm
I can't answer your question, because i don't know, if an extension is designed to override parts of the kernel. Maybe you could post your modification in the bug list as "enhancement", if this is the character of your modification. Or do you do some "personal" tweakings?
Marco
http://www.hyperroad-design.com
|
|
Eirik Alfstad Johansen
|
Thursday 11 December 2003 12:00:05 am
Hi Marco, Thanks for your reply. My modifications to the shop module are in essence an extension of the information collected when placing an order. However, regardless of whether ezp could use this as an extension or not, I'll be making several modifications in the future, and several of them will be usable just for us. So I really need to find out how this works. Anyone from ez around? Sincerely,
Eirik Johansen
Netmaking AS http://www.netmaking.no/
Sincerely,
Eirik Alfstad Johansen
http://www.netmaking.no/
|
|
Bård Farstad
|
Thursday 11 December 2003 12:05:36 am
If you need additional information on an order you should look into storing this using the shop account handler ( which serializes information to XML ). Another approach can be using workflows. You should try to make your additions in extensions as much as possible. If you change the kernel code you will definetly have problems with upgrades. --bård
Documentation: http://ez.no/doc
|
|
Eirik Alfstad Johansen
|
Thursday 11 December 2003 12:24:48 am
Hi Bård, I have made use of the shop account handler to the extend possible. However, this is (as you know) also a part of the kernel code, as well as the register view of the shop module which I've had to modify in order to validate the new data being collected. It surprised me that there was no other way of doing something as simple as modifying the collected order information without touching the kernel code, but when dived into it, I found out that the data used by ezp was hardcoded. Hopefully, I'm missing something that would make this easier. Maybe the answer is in the creation of a new shopaccounthandler? But that brings me back to the question of whether it would be accessible or not if I put it in a module extension with the same name as the shop module. Furthermore, that still doesn't solve the problem with the shop/register.php modifications. Sincerely,
Sincerely,
Eirik Alfstad Johansen
http://www.netmaking.no/
|
|
Paul Forsyth
|
Thursday 11 December 2003 1:01:29 am
You could create a small patch file that can be applied to future versions (provided the targeted file remains the same...) For our shop in www.planet-troy.com we had to add a small function to retreive needed information to: ezproductcollectionitem.php which we maintain as a patch. Its not as good as an extension because file checks need to be performed on new version but its a good compromise for us. paul
|
|
Georg Franz
|
Friday 12 December 2003 3:44:18 am
Hi Bard, I also made some minor changes in some files which are in /kernel/content and I've the same question: Is there another way to keep this modifications instead of doing the modifications in new versions of ez again? -> Suggestion for future versions: An "override" directory for kernel / lib files would be fine (the same way as with templates), this can be placed in "extension" or in an own main directory.
Kind regards,
Emil.
Best wishes,
Georg.
--
http://www.schicksal.com Horoskop website which uses eZ Publish since 2004
|
|
Graham Brookins
|
Wednesday 01 January 2025 11:04:58 am
Hello Eirik and Others Listening! In eZ Publish 6 We quickly addressed this problem by patching the core kernel that loads module views and made extensions detected take priority and load instead of the available kernel modules. This solves this problem cleanly within existing extension structures. Here is the related change on GitHub! For those interested but not running the latest eZ Publish 6 release 6.0.6 can use this ezpublish5 based kernel override extension, bckernelmoduleoverride. Enjoy! Cheers, Graham
|