As per the title,
If I were to use this code within a <xen:popup> tag in an admin template:
Neither the class or data attributes are compiled into the resulting template:
If this is "As Designed" then please consider adding those as valid attributes. It seems to me like that functionality could be useful even for parts of the core. e.g. the Uninstall or Upgrade links in the Admin CP add-ons list where consistently in other places they are triggered in an Overlay.
Thanks!
If I were to use this code within a <xen:popup> tag in an admin template:
Code:
<xen:link href="{xen:adminlink 'add-ons/build', $addOn}" displayif="{$canAccessDevelopment}" class="OverlayTrigger" data-cacheoverlay="false">{xen:phrase build}</xen:link>Neither the class or data attributes are compiled into the resulting template:
HTML:
<a href="admin.php?add-ons/SomeAddOn/build">Build</a>If this is "As Designed" then please consider adding those as valid attributes. It seems to me like that functionality could be useful even for parts of the core. e.g. the Uninstall or Upgrade links in the Admin CP add-ons list where consistently in other places they are triggered in an Overlay.
Thanks!
Upvote
0
