Thanks Manual, I guess I'll evaluate the way of copying the interfaces which I need to change and give them their own indicator character. Though it's seems to me a bit stupid having the possibilities of inheritance at hand but being unable to use them in this case...
Is there any problem you could think of with this solution - except for having to manually syncing code changes in case of an update which I had to do anyway after changing the core files? Thanks Marc ORCA Services AG Herrenmattstrasse 26 CH-4132 Muttenz Office Basel: Aeschengraben 10, CH-4051 Basel [email protected]<mailto:[email protected]> T. +41 61 205 80 80 T. +41 61 205 80 73 (direkt) F. +41 61 205 80 81 www.orca.ch<http://www.orca.ch>, www.orca-services.ch<http://www.orca-services.ch> ________________________________ Von: [email protected] [mailto:[email protected]] Im Auftrag von Manuel Reiß Gesendet: Dienstag, 14. Juni 2011 15:37 An: [email protected] Betreff: Re: [oxid-dev-general] Extending the ERP interface Hi, if it's just about some new fields, you can easily add / remove the corresponding entries in your oxerptype-object's field-map protected $_aFieldListVersions (use the proper version index) I think there isn't an elegant way extending those classes (it's been a while since I was working on that interface), so you have to make your changes inside the original files and so you will lose your fire-and-forget update ability. Regards, Manuel [email protected]<mailto:[email protected]> | www.mediaopt.de<http://www.mediaopt.de/> derksen mediaopt gmbh | elbestrasse 28/29 | 12045 berlin | +49 (30) 34 09 42-77 | fax-66 | Amtsgericht Charlottenburg | HRB 120935 B | ust.-id DE265886017 | geschäftsführer dipl.-ing. philipp derksen Von: [email protected] [mailto:[email protected]] Im Auftrag von development Gesendet: Dienstag, 14. Juni 2011 15:23 An: [email protected] Betreff: [oxid-dev-general] Extending the ERP interface Hello list I posted a question to the German forum, which nobody seemed to able to answer me: http://www.oxid-esales.com/forum/showthread.php?t=9889 Here a translation of it: For a current project with a B2B customer I need to customize the ERP OXID CSV interface so that some additional fields more or a few existing fields less are imported. In a first step, it's only about the article import via CSV. How can I extend the interface (already own it) the easiest way without risking to limit the ability to update? I see in the documentary wonderfully, how I for example can create export functions as plugins and therefore don't limit the update ability. But the way described in the documentation for the extension of the CSV import interface requires several customizations in the existing code of the interface (and not only the cron file). Does anybody have me some hints how I can extend/change the existing interface without changing the core code (of the interface)? Many thanks and greetings from Basel Marc ORCA Services AG Herrenmattstrasse 26 CH-4132 Muttenz Office Basel: Aeschengraben 10, CH-4051 Basel [email protected]<mailto:[email protected]> T. +41 61 205 80 80 T. +41 61 205 80 73 (direkt) F. +41 61 205 80 81 www.orca.ch<http://www.orca.ch>, www.orca-services.ch<http://www.orca-services.ch>
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
