Skin Templates

Is it possible to call a "module template" using {jrCore_include} directly into a site-builder page using Template Code?

Currently, I have several pages using this template that I have added into the skin directory:

However, periodically for no known reason, that tpl file is being deleted from the skin directory. This is important because I have determined, from a time investment standpoint, that it is not financially feasible to manage a custom skin with all of the updates that come out. So I need to use an out-of-the-box skin. My modifications are easy to manage and compare (within the skin template manager), but new template files that I add are being deleted. Of course, I expect this to happen when I update the skin, but these files are being deleted randomly.

So anyways, I am tired of fighting with it and just want to create a module where I can manage these additional templates. Is this possible?


--
The Patria Company - patriaco.com / quality-trades.com / a-t.life - doing Jamroom since v3
updated by @the-patria-company: 09/21/18 01:02:22AM

To include a template from a module, use this -


But I am concerned that you say files are being randomly deleted.
If you upgrade a stock skin, a new 'symlinked' folder will be created for it, so yes, your template will 'disappear' but it should still be in the previous skin folder. Only if you then 'Rebase' your skins will it actually be deleted.


--
Paul Asher - JR Developer and System Import Specialist
updated by @paul: 06/15/18 07:08:16AM

Hey Paul! Thanks!

The only thing I can think is that I left the site in Developer Mode overnight a few times. Does developer mode rebase automatically?


--
The Patria Company - patriaco.com / quality-trades.com / a-t.life - doing Jamroom since v3

No, being in developer mode will not rebase automatically.


--
Paul Asher - JR Developer and System Import Specialist

This will also happen if you are not using a cloned skin.

Hope this helps!


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos

Thanks @douglas and @paul.

After many trial and error issues with cloning and customizing skins, we have determined that it is just not practical. We have decided that creating modules for custom profile pages and making modifications from the skin template admin area (because they do not get trashed during an update) is the most profitable way to manage a JR site.

Honestly, the new templates are amazing and with a little css styling added to the meta.tpl you can get a very unique look with minimal effort. The site builder has really matured over the last few years and its overall flexibility makes it a really powerful tool.

Bottom-line: no more adding custom tpl files to the skins directory for us. Thanks again Paul for this answer, you have saved us hundreds of hours of work going forward.


--
The Patria Company - patriaco.com / quality-trades.com / a-t.life - doing Jamroom since v3

The intention of the system is the reverse of that.

It was hoped that the skins would be a starting point that you turn into whatever you want. The skins exist to show off the capabilities of the back end system. No skin shows off all of the possibilities.

You're supposed to build your own stuff and not worry about what the skins are doing after that. Once you clone, make the skin yours and forget about what it was when you started.

I built this site on jamroom: https://aikidotravel.com its never going to get an update from its original skin again. Im thankful the original skin existed to get me started, but from there its time to leave the shoreline behind.

don't give up on it.

Not giving up, just trying to be efficient. WP has a brilliant concept called a "child theme". All of the core aspects of the parent theme are untouched and updates to important functions and scripting can happen without interrupting a live website. The child-theme is completely customizable.

Doing file comparisons with a cloned skin after a skin update is just too time-consuming.

It is the functionality of the "child-theme" concept that we are trying to replicate because it is just so much more profitable.

I do understand the amazing capabilities of cloning a skin, but it just doesn't make sense for us financially. If there are others that find themselves spending an enormous amount of time updating their cloned skins - because we all love new features - then this concept may help save some time, money and effort.

We really appreciate that Jamroom is so flexible that we even have this option available to us. Thanks for all you do @michael. Again, the site-builder is a game changer for producing large dynamic content websites. Jamroom has no equal.


--
The Patria Company - patriaco.com / quality-trades.com / a-t.life - doing Jamroom since v3