View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006822||OXID eShop (all versions)||2.3. Extensions (modules, themes)||public||2018-04-27 16:18||2019-05-06 11:32|
|Target Version||Fixed in Version|
|Summary||0006822: Admin templates can't be changed in source if they are overwritten in pe/ee|
|Description||If a template is overwritten in PE or EE Version of OXID eShop 6, you can't do changes in the template stored in the source directory. The reason is the look up order of the shop framework:|
3) source (ce)
So for example if you need a new block in admin template article_main, you have to make changes in the vendor -> oxideshop-ee -> article_main template, because the shop framework will take this one to render the webpage. Unfortunately it should be strictly avoided to make changes in the vendors directory.
|Steps To Reproduce||1) search for an admin template in pe/ee that's also available in source (ce)|
2) make changes in the template in source
3) empty /tmp
4) reload the webpage
5) you will see no changes
6) delete/rename the corresponding template in pe/ee
7) changes will be visible
|Additional Information||Changing the look up order wouldn't be a solution, but it's appreciated to have a option to change admin templates, especially for adding own blocks.|
|Tags||Admin Template, Template Blocks, Theme Handling|
|PHP Version||Not defined|
|MySQL Version||Not defined|
That was exactly the problem we tried to describe in 0006821 - you can't add new blocks to EE admin templates right now, which is a major bug to me, because we need some extra blocks for quite some modules, so I am not sure about the "low" priority ...
And why are all the CE admin templates copied to the EE source directory anyways, but not the EE specific ones?
Issue was classified minor, because you can extend admin templates with the included blocks and even not all admin templates are affected. Possible priority changes will be discusssed intern at the next development meeting.
Because the bugtracker is only for reporting issues, please use our Dev-General Mailing List (https://oxidforge.org/en/mailinglists) for further questions about OXID eShop.
||Well, I used the bugtracker because it IS an issue / bug to me, not something I wanted to discuss ... and only because not all templates are affected doesn't qualify it as a "non-bug" imho :)|
||it´s a bug NOT a feature! no comment, really ...|
||... same issue here!! the customer need's a better user interface / better sorting of input fields, optimized custom templates, etc. for article data entry, but we have to say "sorry not possible! even with your enterprise edition :( ..."|
+1 for solving this issue
We had modules extending the block, but this also does not work anymore.
||+1 - we also have some problems with this. There is some hacks but this is not good way to make it that way.|