The Module version field is used to specify
4. Create resources subfolder: If this is checked, a folder named resources will be created in the module folder. Resources are supporting files such as images, javaScript, and cascading style sheets that templates use. If you create a templates subfolder, you should also create a resources subfolder. 5. Create classes subfolder: If this is checked, a classes folder will be created for this module, along with the requisite java class structure subfolders. For example, in the case of our module, the path classes/tv/alephnull/ modules/templates would be created. This option is useful to developers who intend to write custom java classes or use custom resource bundles in OpenCms. Compiled class files stored in this folder will be loaded when OpenCms starts up. We will not be using this folder. 6. Create lib subfolder: If this is checked, a lib subfolder will be created. This folder is used to store java archives (JARs) that contain compiled java code and associated resources. Libraries in this directory will be loaded when the server starts. Clicking Ok will create the new module. You can now navigate to the new folder in the VFS. In the OpenCms toolbar, change Site from /sites/default/ to /, and change to the explorer view. Now navigate to the /system/ modules folder. The new module folder (tv.alephnull.modules.templates) should be listed in this folder. File History The fifth screen in the administration view is the File History screen: OpenCms maintains history information for every file in the VFS. As we saw in Chapter 3, you can browse a file’s history from the explorer view. You can even choose to revert to an earlier version of the file if you need. The File History screen can be used to access two other screens for dealing with the history features of OpenCms.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Inexpensive Web Hosting services