Changes for page Explanation of the default properties in a Wonder project

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -8,7 +8,7 @@
8	8
9	9	{{/code}}
10	10
11		-The OGNL enable you to use the OGNL syntax for inline bindings (eg, putting bindings directly in the .html file instead of the .wod, for example: <wo:str value="$pageTitle" />). [[WOOGNL>>doc:WOOgnl Framework]] is automatically added to the classpath when you create a new Wonder project.
	11	+The OGNL enable you to use the OGNL syntax for inline bindings (eg, putting bindings directly in the .html file instead of the .wod, for example: <wo:str value="$pageTitle" />). [[WOOGNL>>doc:documentation.Home.Frameworks.WOOgnl Framework.WebHome]] is automatically added to the classpath when you create a new Wonder project.
12	12
13	13	{{code}}
14	14
...	...	@@ -77,7 +77,7 @@
77	77
78	78	{{/code}}
79	79
80		-Those properties are to enable support for [[migrations>>doc:Project WONDER-Frameworks-ERXMigration]]. If you are using migrations but you have models where the schema already exist in the database, uncomment er.migration.modelNames and put in a list (comma separated) of the models you want to use migrations with, if you let this property commented, Wonder will try to migrate all of your models, which would generate errors for models where your schema already exist.
	80	+Those properties are to enable support for [[migrations>>doc:documentation.Home.Frameworks.Project Wonder.Project WONDER-Frameworks-ERXMigration.WebHome]]. If you are using migrations but you have models where the schema already exist in the database, uncomment er.migration.modelNames and put in a list (comma separated) of the models you want to use migrations with, if you let this property commented, Wonder will try to migrate all of your models, which would generate errors for models where your schema already exist.
81	81
82	82	{{code}}
83	83