Timeline for Call PHTML from another PHTML
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21, 2018 at 18:38 | history | edited | seanbreeden | CC BY-SA 4.0 |
Added closing php tag
|
| Jun 4, 2016 at 10:18 | comment | added | Fabian Blechschmidt | Not sure about implications. 1. But it looks ugly and logic should be avoided in templates. 2. Beside this your colleagues are happy if they find code where it is expected (block -> layout.xml). And third it might be important for (full page) caching. | |
| Jun 4, 2016 at 10:18 | comment | added | Raphael at Digital Pianism | @Toto it is more of a good practice in my opinion. This way developers see straight away which blocks are child of other blocks without having to look in every template to find out "magic code" like the second one | |
| Jun 4, 2016 at 10:04 | comment | added | Husanoo | Thanks Fabian. Is there a reason why second way is not recommended? First one looks more like Magento standard way. But just curious what implication second way may have. | |
| Jun 4, 2016 at 9:44 | history | answered | Fabian Blechschmidt | CC BY-SA 3.0 |