Henriette - Revision history

152.78.91.187: /* Sintana_ark */

2007-08-09T10:39:56Z

‎Sintana_ark

2007-08-09T10:36:37Z

‎Sintana_ark

2007-08-09T10:32:03Z

‎Module settings file

2007-08-09T10:31:31Z

‎Module settings file

2007-08-09T10:31:09Z

‎Module settings file

2007-08-09T10:30:38Z

‎Module settings file

2007-08-09T10:29:34Z

‎Module settings file

2007-08-09T10:29:14Z

‎Setting file for module

2007-08-09T10:10:37Z

‎Database setup

2007-08-09T10:10:13Z

‎Module setup

@@ Line 181: / Line 181: @@
 **eggerstype - 79
 **straumetype - 80
 *numbertypes
 **rouendfac - 1
@@ Line 186: / Line 194: @@
 **height - 3
 **rimdia - 4

@@ Line 127: / Line 127: @@
            );
-The itemkey fieldallows you to access the alias and information about the module itself.
+The itemkey field allows you to access the alias and information about the module itself.
      $conf_field_cxtxmi =
      array(
@@ Line 144: / Line 144: @@
          'edt_validation' => $xmi_edt_validation
            );
 ==Clarent==

@@ Line 124: / Line 124: @@
          'hidden' => FALSE,
          'add_validation' => $key_add_validation,
-         'edt_validation' => $key_edt_validation );
+         'edt_validation' => $key_edt_validation
 The itemkey fieldallows you to access the alias and information about the module itself.
-$conf_field_cxtxmi =
+    $conf_field_cxtxmi =
      array(
          'dataclass' => 'xmi',
@@ Line 141: / Line 142: @@
          'hidden' => FALSE,
          'add_validation' => $xmi_add_validation,
-         'edt_validation' => $xmi_edt_validation );
+         'edt_validation' => $xmi_edt_validation
 ==Clarent==

@@ Line 112: / Line 112: @@
 The settings file begins with some custom fields settings. Normally all field setting sshould go to the field_settings.php file from where they can all be reused in other modules. However a few are very module specific and should be set in the modules own settings file.
-$conf_field_itemkey =
+    $conf_field_itemkey =
      array(
          'dataclass' => 'itemkey',

@@ Line 107: / Line 107: @@
 If you wish to have aliases in other languages you must create first the original alias (i.e. the english one) and then create a new alias instance with the same itemkey and itemvalue as the first but with a different language (e.g. it for italian).
-====Setting file for module====
+====Module settings file====
 ==Clarent==

@@ Line 69: / Line 69: @@
 In all the stuff we are creating now everytime it says 'sfi' this must be changed to your unique module short form
-====Database setup====
+====Module in database====
 #In the database (portus_ark) create a new table called '''sfi_tbl_sfi''' with the fields. This table will be fileld automatically with all the instances of the module
 ##''sfi''_cd - varchar(30)
@@ Line 105: / Line 105: @@
 ##cre_by = 1 (or your number)
 ##cre_on = NOW
 If you wish to have aliases in other languages you must create first the original alias (i.e. the english one) and then create a new alias instance with the same itemkey and itemvalue as the first but with a different language (e.g. it for italian).
 ====Setting file for module====