Hi Team,
I just wanted to advise regarding the way your K2 set up has been done.
Although it is working, it has not been set up as well as it should and could cause some problems when obtaining K2 support or when using some K2 plugins, such as the CC4K2.
CCS4K2 is a plugin which allows an additional css over ride file to be entered into each new K2 Template which is created.
As it stands at the moment, your layout has no Template folder for further K2 templates to be created by your users thus drastically reducing the styling and layout potential for your users.
Ideally, the K2 template over rides structure should be as follows.
Main K2 micro template location templates/ja_pyro/html/com_k2/templates
Within this folder can be stored:
- generic.php
- user.php
- profile
- register
- /YOURK2TEMPLATENAME
Within the folder YOURK2TEMPLATENAME you would then have:
- category.php
- category_item.php
- category_item_links.php
- item.php
- item_comments_form.php
- latest.php
- latest_item.php
If you used CSS4K2, then each new YOURK2TEMPLATE that is created would also have a YOURK2TEMPLATE_style.css file in its folder, further information can be found here.
Further information on setting up K2 templates can be found in the documentation on here.
This not a criticism but just advise to help you maintain K2 flexibility for your users.