Hi again,
this is interesting because I wrote (some) modules that extend the menue without having extended classes setup in modules-array - the only file in modules-dir is menu.xml. Maybe this is a kind of bug - or simply new handling in 4.6. But I would like to see all module-dirs scanned for menue.xml without unnecessarily setting up files in the metadata.php. Regards, Kai Von: dev-general-boun...@lists.oxidforge.org [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Joachim Barthel Gesendet: Donnerstag, 28. Juni 2012 09:31 An: dev-general@lists.oxidforge.org Betreff: Re: [oxid-dev-general] Metadata: Problems on registering multiple entries for one class Hi Kai, yes the menu.xml (which adds the new menue entries to the admin menue in the left frame) wasn't loaded without having the "extend"-block. I think there is no alternative for the menue yet, the _only_ problem was that with the "files"-block alone the menue wont be loaded. Maybe the description for metadata <http://wiki.oxidforge.org/Features/Extension_metadata_file> can be extended by the OXID development, so that the behavior of the entries will be explained as well. Joachim 2012/6/27 Kai Gazmaga <kai.gazm...@vektordesign.de> Hi Joachim, i did not start to migrate my modules to 4.6. So I did not really play with the mechanics of the new module-system and can not give you profound help on that. Now I have a question: what do you mean with "the menu is missing / not loaded"? What menue. Isn't it described in a menue.xml any longer? How do I state, where to add new menu-entries etc.? If I understand it right, files-entry is for avoiding to copy files to core- and view-directories, but not for adding any menue or what-ever-additional-functionality. Regards, Kai Von: dev-general-boun...@lists.oxidforge.org [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Joachim Barthel Gesendet: Mittwoch, 27. Juni 2012 09:40 An: dev-general@lists.oxidforge.org Betreff: Re: [oxid-dev-general] Metadata: Problems on registering multiple entries for one class Hi Aurimas, Hi Kai, I see, I've misunderstood the mechanism. Now it is working, but I'm still a little bit wondering. Here my way to solve it: I've now added this section to the file metadata.php (as first _without_ any entries for extend) 'files' => array( 'oxprobs_articles' => 'oxprobs/oxprobs_articles.php', 'oxprobs_delivery' => 'oxprobs/oxprobs_delivery.php', 'oxprobs_groups' => 'oxprobs/oxprobs_groups.php', ), After that the modules will be loaded, but the menu is missing / not loaded. Therefore I added the following extend section (but with only one class) 'extend' => array( 'oxadmindetails' => 'oxprobs/oxprobs_articles' ), Now activate/deactivate works fine and the menu is shown as well Thanks to all for the help! Joachim 2012/6/27 Aurimas Urbonas <aurim...@gmail.com> Hi, Kai was right, you misunderstood the extension concept in oxid. You don't need to register "extension" in this case, because you are not changing oxid behaviour but adding new behaviour. You can use Kai's suggested solution, or if you want to keep everything under modules dir you can do the following: your controller classes should extend oxAdminDetails: class oxprobs_articles extends oxAdminDetails if you keep them in modules/oxprobs, then in you metadata.php you need to tell oxid autoloader where it should look for class oxprobs_articles $aModule = array( ... 'files' => array( 'oxprobs_articles' => 'oxprobs/oxprobs_articles.php' ) Best Regards, Aurimas On Wed, Jun 27, 2012 at 9:35 AM, Joachim Barthel <jobart...@googlemail.com> wrote: Hi Kai, thanks a lot for your support. The module is running for all versions from 4.3 to 4.5, you can see here some screenshots <http://code.google.com/p/oxprobs/wiki/Screenshots> . Menue.xml, .tpl's , own directory under modules etc. all of them is there, _only_ the registration in 4.6 with metadata.php makes trouble. Joachim 2012/6/26 Kai Gazmaga <kai.gazm...@vektordesign.de> I guess you missunderstood - if I understand you right. If you want to have NEW Items you should overload oxadmindetails, but you must put your new classes to the folder /admin where all the admin-view-classes are stored. Additionaly you must write a fitting template and place it in /out/admin/tpl and finaly you have to provide a menue.xml where you define the position / structure of your extension. By the way: did your extension show up in the backend inShops < 4.6? Without a menue.xml I can not really believe that. If you need further help have a look at my very small module vdService - you can download it here: http://www.vektordesign.de/downloads There you find all the necessary parts of a backend-extension. If you have further questions feel free to give me a call or go on writing here in the list. Gruß, Kai VektorDesign - Online-Shops und Programmierung Kai Gazmaga Katharinenstraße 57 73 728 Esslingen Tel.: +49 711 - 25516226 <tel:%2B49%20711%20-%2025516226> Fax: +49 711 - 25518078 <tel:%2B49%20711%20-%2025518078> Mail: i...@vektordesign.de Web: www.vektordesign.de <http://www.vektordesign.de/> _______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
