Sure, i faced same problem several times. feel free to make a pull request :)
If you need a quick workaround: https://github.com/vanilla-thunder/vt-cmsstructure/blob/master/copy_this/modules/vt-cmsstructure/out/blocks/admin_content_list_item.tpl -----Ursprüngliche Nachricht----- Von: dev-general-boun...@lists.oxidforge.org [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Maximilian Berghoff Gesendet: Dienstag, 17. März 2015 12:12 An: dev-general@lists.oxidforge.org Betreff: [oxid-dev-general] Better block definition in original templates Hi, i really like the idea of blocks in the templates. The upside is, that i don't need to copy the complete template for changes. Template changes in the original code arn't that hard to catch, when just extending some blocks. But i think there are some block definitions in the shop code that arn't very helpfull. Example [{bloc="block-name"}] <td> <div> <!-- Content --></div> <div> <!-- Content --></div> </td> [{/block}] (seen in basketcontents.tpl) It is impossible now to extend the <td></td> content except copying the complete content again. Better approach: <td> [{bloc="block-name"}] <div> <!-- Content --></div> <div> <!-- Content --></div> [{/block}] </td> Now i can just extend the block and add my content. What do you think? greets max -- -- Maximilian Berghoff Mayflower GmbH Gneisenaustraße 10/11 Tel.: +49 931 359 65 1180 D-97074 Würzburg Fax : +49 931 359 65 28 maximilian.bergh...@mayflower.de http://www.mayflower.de Mayflower GmbH: http://mayflower.de/impressum _______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
