Izharul Haque Aazmi (Izhar Aazmi) | |
Bhartiy Digital Laboratories and Bhartiy Web Technologies, 11 - Kaveri Enclave - II, Near Swarn Jayanti Nagar, Ramghat Road, Aligarh - 202 001 (UP), India |
|
Visit: www.izharaazmi.com |
--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cms+unsubscribe@googlegroups.com.
To post to this group, send email to joomla-dev-cms@googlegroups.com.
Visit this group at https://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.
These files were used in 1.5 when there was no layout specific file for a menu item. In 1.6 that feature was removed "on purpose" (because the person that did remove it did not understand what it was for) and despite protest from several people, it was not put back in. Thus: these files are useless in joomla as of 1.6.
Hannes
AFAIK there isn't any DTD for these files. If someone does know the structure though it'd be good to get one added to https://github.com/joomla/schemas
On Fri, Oct 14, 2016 at 9:54 AM, Izhar Aazmi <izhar...@gmail.com> wrote:
I tried looking up for a place where I could reference as a guideline for creating the correct metadata xml for views and layouts. But I was not able to find some good examples.Is there any documentation where I can get to know the full structure for those xml files? if not the DTD itself then few samples which are utilising all available features would be sufficient too.PS: Please do not consider this as a general development related query, trust me this isn't.
Izharul Haque Aazmi (Izhar Aazmi) Bhartiy Digital Laboratories and Bhartiy Web Technologies,
11 - Kaveri Enclave - II, Near Swarn Jayanti Nagar, Ramghat Road, Aligarh - 202 001 (UP), India
Visit: www.izharaazmi.com
--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cms+unsubscribe@googlegroups.com.
To post to this group, send email to joomla-...@googlegroups.com.
Visit this group at https://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.
Well, in that case what are the alternatives for the purpose they served? As I can see the cms still uses them to create menu item types.
I have seen the PR from @bakual, that is regarding removal of unused or overall impactless metadata.xml files from the core components. It does not involve any logic that says we won't use metadata.xml files anywhere anymore.
His another PR also adds inheritance logic to the layout/view/component level metadata.
Therefore the question still remains the same – that how should these metadata files be written to possibly make use of all available features wherever applicable.
<metadata> | |
<view title="COM_XXX_VIEW_TITLE"> | |
<message><![CDATA[COM_XXX_VIEW_AAA_DESC]]></message> | |
<options> | |
<default | |
name="COM_XXX_VIEW_AAA_TITLE" | |
msg="COM_XXX_VIEW_AAA_DESC" | |
/> | |
</options> | |
</view> </metadata> | |
<metadata> | |
<layout title="COM_XXX_VIEW_AAA_TITLE" option="COM_XXX_VIEW_AAA_OPTION"> | |
<message><![CDATA[COM_XXX_VIEW_AAA_DESC]]></message> | |
</layout> | |
</metadata> |
<metadata> <view> <options var="layout"> <default name="COM_EXAMPLE" msg="COM_EXAMPLE_DESC"/> <option name="COM_EXAMPLE_EXT" msg="COM_EXAMPLE_EXT_DESC" value="my_specific_layout" /> </options> </view> </metadata>