# Customize Admin Templates for Professional and Enterprise Editionen

**URL:** <https://forum.oxid-esales.com/t/customize-admin-templates-for-professional-and-enterprise-editionen/97866>\
**Category:** Blog Posts über OXID\
**Tags:** entwicklung-dev\
**Created:** [May 26, 2021, 10:26am UTC](https://forum.oxid-esales.com/t/customize-admin-templates-for-professional-and-enterprise-editionen/97866 "2021-05-26T10:26:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![benjamin.joerger](https://forum.oxid-esales.com/user_avatar/forum.oxid-esales.com/benjamin.joerger/32/220_2.png) [@benjamin.joerger](https://forum.oxid-esales.com/u/benjamin.joerger)\
**Post date:** [May 26, 2021, 10:26am UTC](https://forum.oxid-esales.com/t/customize-admin-templates-for-professional-and-enterprise-editionen/97866/1 "2021-05-26T10:26:59Z")

</div>

By default, the templates in `source/Application/views/admin/tpl` cannot be customized/extended if they are also delivered in OXID eShop Professional and Enterprise Edition (see bug record [0006822: Admin templates can't be changed in source if they are overwritten in pe/ee - OXID eShop bugtrack](https://bugs.oxid-esales.com/view.php?id=6822)). The reason for this is the mandatory loading priority of the admin templates. But what if an individual template for PE/EE is needed?

Using `article_extend.tpl` from EE as an example, I would like to show you a solution.

First, create a patch from `vendor/oxid-esales/oxideshop-ee/Application/views/admin/tpl/article_extend.tpl` that includes the desired changes and save it to your repository under `patches/oxideshop_ee/article_extend_custom_block.patch` .

The content of the patch could look like this:

```auto
Index: Application/views/admin/tpl/article_extend.tpl
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/Application/views/admin/tpl/article_extend.tpl b/Application/views/admin/tpl/article_extend.tpl
--- a/Application/views/admin/tpl/article_extend.tpl	(revision e0412f0c2cca7d44036fca5ca036ed99d9ccee65)
+++ b/Application/views/admin/tpl/article_extend.tpl	(revision e158f8c52b9dd378b3101445b24bb03e41b2181a)
@@ -109,6 +109,7 @@
                   [{oxinputhelp ident="HELP_ARTICLE_EXTEND_MASS"}]
                 </td>
               </tr>
+ [{block name="myCustomBlock"}][{/block}]
 
               <tr>
                 <td class="edittext">

```

Next make sure that this is rolled out using Composer (basis for this is [Applying patches to OXID eShop projects with composer](https://oxidforge.org/en/applying-patches-to-oxid-eshop-projects-with-composer.html)), i.e. we have to modify our composer.json like this:

[![composer adjustments](https://forum.oxid-esales.com/uploads/default/original/2X/9/94dd67fbfacb426d593fdd20b784488eee0e4f88.png)](https://oxidforge.org/wp-content/uploads/2021/05/composer-adjustments.png)

Run composer update now and you have a consistent patch for the EE template, which is applied under `vendor/oxid-esales/oxideshop-ee/Application/views/admin/tpl/article_extend.tpl`.

[![apply patch](https://forum.oxid-esales.com/uploads/default/original/2X/7/78a1652f55372d9f7f1afbcfe07892a29d3ce3ba.png)](https://oxidforge.org/wp-content/uploads/2021/05/apply-patch.png)

---

<div class="post-metadata">

**Author:** ![system](https://forum.oxid-esales.com/user_avatar/forum.oxid-esales.com/system/32/4245_2.png) [@system](https://forum.oxid-esales.com/u/system)\
**Post date:** [May 26, 2022, 10:27am UTC](https://forum.oxid-esales.com/t/customize-admin-templates-for-professional-and-enterprise-editionen/97866/2 "2022-05-26T10:27:14Z")

</div>

Closed on May 26, 2022, 10:27am UTC

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
