Please choose the fields that should be shown in the admin table of this level. Write the name of each field in the order you would like them to appear, seperated by a comma (,).
The "name" field, which will be the edit link, is mandatory. (There will also be a delete link added).
In this case, we would have 3 levels : we may call the first 'Type' (Fiction/Non-fiction) and the second 'Sub-type' (Science-Fiction/Romance/Philosophy), the third being the books themselves (La Gaya Scienza). We will then say that Science-Fiction and Romance sub-types are children of the type Fiction (which is their parent). Typically, the last level (here 'books') will have the most fields, the others being for classification purposes, but you may like a category description or something... Up to 9 levels are supported, which is completely arbitrary, but I couldn't see why we'd need more.".$lang['help_think']."
CTLModuleMaker has detected that you may changes to the initial dna file you imported. If you wish, an upgrade function will be created with the module, so that these changes can be made in the database without the need to reinstall the module. Obviously, this upgrade will only work with modules that were created with the dna you first imported.
Any field that was renamed is considered to be deleted and recreated (which means that upgrading would lose the data in those fields). Therefore, please make sure that you really made the following changes:
Here you must define every field (every attribute or piece of information) that this level has. Keep in mind that some additional fields not directly defined by you will also be created for the module basic functionalities. These fields are:id, name, alias, item_order, parent, active and defaultDo not plan fields for these!
For each field, you will be asked a name and a friendly name. The name will be used in the code, in the templates and in the parameters only. It is the friendly name which will be visible to your visitors.
A mandatory field means that you won\'t be able to create a new item without giving a value to this field. It won\'t have any effect on file fields and may not work with lists.
Indexing a field for the Search Module means that if someone search your whole site with a keyword that is contained in this field, this item will be returned.
To have a field show up in the advanced search form means that if you use the module\'s search action in the searchmode "advanced", the user will have the possibility to make a search using this specific field (search an item in which this field has a particular value).
The field type defines what the field contains and the way the information will be entered. Here is a small explanation of each:
Here is what the list modes look like:
To display a list of elements, your module admin will have the possbility of choosing a different template for each level. The question here is about the display template for the final level (when we\'re displaying the details of one of the final level elements).
Let\'s say you have two levels (categories and items), and two categories. Every item of the first category will be displayed in a certain way, while items of the second category will be displayed in a different way. This means that you would need each category to have its own template for the detail display of its final level children. In other words, the "template level" here should be the "category" level.
If the display template for a final level item doesn\'t depend on its parent, leave this to "Only one template".
For each level, you must decide which fields will be shown in the listing table of the admin panel. Remember that this is mostly for the editor to find his way through the items or seek quick information. The other fields will still be editable when an item is clicked.In uncertainty, leave what\'s already there.
File fields cannot be shown normally in the admin panel. To do this, you will need the create a condition in the adminpanel template (see FAQ)
To give you an idea, here is what an adminpanel for a level may look like:
Unfortunately, there is currently no help specific to this step of the creation process. You may consult the module general help.
If you think this step needs more explanation, please post your request on The Forge.
Create and modify fully functional catalogue-like content modules.
This should be pretty easy to use without help... but for each step of the creation process, you may look at the help tab for advices on this particular step (you can also find this help all bundled here).Although this creates fully functional modules, please keep in mind that the primary intent behind this project was at first to provide basic modules for programmers to modify.
Important: If you use Internet Explorer during the creation process, or meet some problems (blank pages) during the creation, go in the parameters tab of the module and make sure that the option to use sessions to store temporary data is activated.
Before starting the creation process, make sure the module folder is writable (a writing test will be done) and that no folder with the name of the module you wish to create exist. JavaScript should also be activated.
Obviously, the installation/upgrade/uninstallation of this module will have no effect on modules already created.
DNA files are not modules, and have nothing to do with the module xml files. They are used by CTLModuleMaker to store the input data of the module you create - that is, every informations you enter to build your module. This means that if you wish to recreate the same module or change something in it, you don\'t have to get through all the creation process again and may simply enter the DNA file.Unless you change your preferences, at the module creation a dna file of your modules are automatically saved in modules/CTLModuleMaker/autosaved/.Finally, should you have to report a bug in the forge, it would help a lot to include a dna file!
For more help, you may take a look at the FAQ.
CTLModuleMaker is released under the GNU Public License.
Please submit any problem you encounter or any suggestion at the Forge!