Common Modules
Oct 07, 2011
By
Colin Eagles
Hey all,
I've run into a minor snag and was wondering if anyone had any advice. I have built about 10-15 individual modules that each use a common Engage module as a player tab (it's a Glossary of Terms). I was wondering if there is any way of tweaking the coding to allow them to 'point' each of the modules to a central version of the Engage module, rather than calling 10-15 copies. I am using company servers (non-LMS), so, each time I change the glossary (often), I've been republishing the Engage and using scripts to copy it to the 10-15 folder locations. However, as I continue to build additional modules (that will all continue to use this Engage), I'm worried that I'll end up missing one or two.
Any ideas?
2 Replies
Hi Colin we have done this using a custom skin that loads a glossary from a specific location, and even loads the custom skin swf from a specific location, not sure if it is possible using the standard player, you may have to see if you can put a path in the presentation.xml
Thanks Phil, I'll give it a try
This discussion is closed. You can start a new discussion or contact Articulate Support.