The reason you're seeing extra options in Ningja is because they were put there by the skin designer.
When a skin designer designs a skin and wants to put an extra section in somewhere, they want to give you the option of being able to adjust that section without the need to alter the templates.
So they add a button in the ACP. One that exists in Ningja but not in Lucid is "Coming Events Box":
ACP -> SKINS -> NINGJA -> GLOBAL CONFIG -> EVENTS -> Coming Events Box
Which is a checkbox. When you check that checkbox,
the only thing that happens is a variable gets stored in the database. That variable is then available in the templates. That particular variable is:
{$_conf.jrNingja_event_active}
If that is then used anywhere in the skin it will output either
'on' or
'off', THATS ALL.
Its usefulness comes into play when used in conjunction with Template Blocks:
Docs: "Template Blocks"
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-developers-guide/3126/template-blocks
Now because the designer has your input on the matter, they can use Template Blocks to either hide or show a section of code. This saves you the hassle of going and adding or removing that section of code via the Template Editor:
Docs: "Using the Template Editor"
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-admin-handbook/3183/using-the-template-editor
The specific section of the skin that uses that $_conf.jrNingja_event_active variable is this one:
/skins/jrNingja/index.tpl
{* This is the embedded template that is shown for EACH event entry on the right side *}
{if jrCore_module_is_active('jrEvent') && isset($_conf.jrNingja_event_active) && $_conf.jrNingja_event_active == 'on'}
.........
around line 97 and again around line 400.
That particular line reads in english:
"If the Event module is active, and we have a value for $_conf.jrNingja_event_active and that value is on, then show this section"
You could take the inner section of template code from that template and use it in the lucid skin and it would work. The difference is the skin designer is setting the skin up for a particular purpose, they expect that you will have the Event module active for this skin.
updated by @michael: 09/21/16 06:17:26PM
JAMROOM
