Changes between Version 3 and Version 4 of DeveloperGuidelines/Templates/Migration

Timestamp:

01/05/15 09:12:01 (10 years ago)

Author:

Dominic König

Comment:

--

DeveloperGuidelines/Templates/Migration

@@ -131 +131 @@
 It is therefore recommended to migrate all templates. Follow the steps above and/or ask for support on our mailing list to migrate your templates.
 
+== Importing Template Modules ==
+
+If you have template-specific modules inside your template folder, you can import them in config.py like in any other Python package, e.g.:
+
+{{{
+from controllers import index
+}}}
+
+Be careful with name collisions, though - ideally, module names like "gluon.py" or "s3.py" should be avoided inside templates. If there is an unresolvable name collision, make sure you are explicit about the import path for outside modules.
+
+To import shared modules from other templates, use the template-path, e.g.:
+
+{{{
+from templates.SSF.controllers import subscriptions
+}}}
+