Re: ZMS content -> SCORM export
Niels Dettenbach <[email protected]> Thu, 25 Nov 2010 09:39:10 +0100
| Newsgroups | gmane.comp.cms.zms.devel |
|---|---|
| Organization | Syndicat IT&Internet |
| Message-ID | <[email protected]> |
Dear Mr. Dr. Hoffmann, many thanks for your fast reply. Am Mittwoch 24 November 2010, 21:51:06 schrieben Sie: > ... then simply copy /common into the zope-folder/subinstance you want to > export. Not nice, but fast solution. Yes, this is what i still did but results in a high inefficiency here as we have at least 10 sub-instances (and plan more) in such a ZMS site and the same common stuff is used by all/most of them. But may be i misunderstand the concept behind master, client zms setups here. We currently run several ZMS "portal" setups which make hard use of the (really nice) master / client) concept as it allows maintaining more then one more or less differing zms site/instance very efficient (by aquisition). Some years ago i remember there was a ZOPE "transparent link" Product / object which did not seem to work with actual Zopes anymore. I thought ZMS.export.domains would do that job. Will try to read into ZMS sources to find a more elegant way (or - if required - will try to write a method / patch which allows the configuration of a list/tuple of folders / objects to include by aquisition in a export as "usual" within the zms standard web output). If i'm on a completely wrong way here or someone has another idea for a solution pls feel free to inform me here. many thanks again for you really nice work and best regards, Niels. -- --- Niels Dettenbach --- Syndicat IT&Internet http://www.syndicat.com T.-Muentzer.-Str. 2, 37308 Heilbad Heiligenstadt - DE --- Kryptoinfo: PGP public key ID 651CA20D Fingerprint: 55E0 4DCD B04C 4A49 1586 88AE 54DC 4465 651C A20D https://syndicat.com/pub_key.asc ---
signature.asc
(application/pgp-signature, 836 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iQIcBAABCAAGBQJM7iCuAAoJEM78prARigUnuXwP/i0ybDERKj1ywXgLSiyTXh9T a7VUFyCk/qaeGV0rqV0jvnLyQH16aeMPtduMzFiYHYa4BHwWB78wPGkeptNBqgtt lDMAVJXVGSGqxzUo37jyE3OpRkLYZ5CnmwgCsbhQsQ6j2SW8SUi3ff+cyfvqH2cY 8Av82aXtLIEBy+WHUc4p0ZYLCZFgiLfqk6RdCKvzJlTSeFhwFzSwM9KVNUyMtWsR MgsZ7LRN9rbstQcOvNEQiyXjrRNSh+4+YLNgbZRP78WVGSlC+tqS2rctKTvP5KqW hP9lZcmEeCv+/DL2376PVpu4MABY3hlDvWapwFSS+jdoqcVY4eXSXisqmax0QsQy Srzh4Bv+Sgu/wbCwnf7hatPauePfP7htBOfx7Ab1M+Nr/08GPhZAdDORjCxQ+BKx +5JjTqKNVSWkQTfS5SBnLg8/ZE6ClPxwPhJmETfcH3zVaBKhMj1WZRcIZV+Nymc3 X1Trn3dQtyQypJ/MeMzlDF0KtPQ0d2IYiM1nt7FaCxuGlhY+0oBvowAIFAulvJq6 Q6ZV52+ye54szHAf7yNy8/RoLJSAw5Hh4yyMgpMqB/wMRd45jGHFBn+DKiHXv/Yg C7y0Cjlzi44LqvCW43Zwjfgh854EtNY0ZN7teS5wZwZQ37+vnl88AE6F7VlAstlU viFD7iZ9kgRmuBNgJq5f =l1f+ -----END PGP SIGNATURE-----