blog documentation FAQ followers forum marketplace services youtube

solved Ningja vs Ninja and a Cloned Ningja skin used for customizations

The Jamroom Network » Forum » Ning To Jamroom » Page » Ningja vs Ninja and a Cloned Ningja skin used for customizations
researchcooperative
@researchcooperative
6 years ago
694 posts
The customized skin on my site is based on a clone of Ningja, and is my active skin.

In my skin templates compare tool I see a pull-down list of template versions for Ningja and Ninja.

Should I delete the jrNingJa skin from my system, or is it best to keep both the Ningja and Ninja skins installed?

Are updates only happening to the jrNinja skin?






--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
updated by @researchcooperative: 04/08/18 02:24:29PM
paul
@paul
6 years ago
4,326 posts
We initially developed the Ningja skin specifically for Ning migrants and named it as such. We then got worried about potential infringements so switched it to Ninja.
They are basically the same skin but only Ninja is now supported and Ningja is removed from the marketplace.
hth


--
Paul Asher - JR Developer and System Import Specialist
researchcooperative
@researchcooperative
6 years ago
694 posts
I think this means I won't damage anything or lose anything by deleting or uninstalling the original NingJa skin from my system, since I have the new Ninja skin installed.

Having it there adds a whole lot of early versions in my compare tool, making it difficult to correctly find and select the current Ninja version that I should be updating to.

So... is it OK to delete the old skin?

Thanks


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
paul
@paul
6 years ago
4,326 posts
Yes - Delete it.


--
Paul Asher - JR Developer and System Import Specialist
researchcooperative
@researchcooperative
6 years ago
694 posts
Thanks, I have done that. Have also deleted old cloned skins that were not active.

All past versions of the current active skin are held in the datastore, so I don't need unused clones cluttering up the system.

I suppose I also do not need the current default skin of the JR system, namely Elastic 2.

Or does it have special status as the default skin?

If I happen to ask a developer to modify my skin, would it be useful to have the default skin installed?

What should I do in this case?

Can I delete Elastic 2, leaving just the current jrNinja skin and my active, NingJa-origin custom skin?


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
updated by @researchcooperative: 01/06/18 07:08:05AM
paul
@paul
6 years ago
4,326 posts
Elastic2 has no special status so ok to delete it.


--
Paul Asher - JR Developer and System Import Specialist
researchcooperative
@researchcooperative
6 years ago
694 posts
I think the reason I installed Elastic2 was that I thought it might be useful to use this as an Admin skin in conjunction with the Admin Skin module.

Is there any situation where it is not useful to keep the Admin area constant, using the Admin Skin module, while developing a custom skin for the front end?

i.e. If I were to keep Elastic2 installed and use this in conjunction with the Admin Skin module, would this make management of my site simpler in the long term, or less simple?


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
paul
@paul
6 years ago
4,326 posts
All ACP functionality is available across all skins so using the AdminSkin module and different skins is just down to personal preference. Personally I use the same skin sitewide on all my sites to save any complications.


--
Paul Asher - JR Developer and System Import Specialist
researchcooperative
@researchcooperative
6 years ago
694 posts
paul:
...Personally I use the same skin sitewide on all my sites to save any complications.

Thanks Paul,

Sounds good to me. I'll do the same.

Cleaning out the unneeded skin modules has helped me focus on learning how to update templates in my own custom skin.

Cheers (calling this thread solved)


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
updated by @researchcooperative: 01/07/18 02:46:38AM