Clicking Ok at the bottom of the results screen will take you back to the External Link Validation screen. Managing Galleries The Gallery Overview screen is a convenient interface to access all the galleries in the VFS. As we saw in Chapter 3, galleries are a special type of folder (extended folder) used to store a specific type of information. For example, image galleries are used for storing files of type Images, and external link galleries are used to store External Link files. Galleries can be stored anywhere in a site. In some respects, this can be very convenient, allowing editors to locate galleries in the same part of the file system as the content which uses them. But managing a decentralized collection of galleries would be difficult without the tools accessed from the Gallery Overview screen. There are five buttons on this screen (one for each type of gallery), Download Galleries, HTML Galleries, Image Galleries, External Link Galleries, and Table Galleries. Gallery Overview is one of only two tools available to anyone in the User group. (The other screen is Link Validation.) A user need not be an administrator or project manager to use this screen to access the galleries. However, the user is still constrained by the permissions of the galleries, so that he or she cannot view a file through the Gallery Overview screen that he or she could not view in the explorer view. All five of these tools function identically, so for the sake of brevity I will only cover one. The same procedures can be applied to the other four gallery tools.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Discount Web Hosting services
External Link Validation The External Link Validation screen is used to search all the Page-type documents for links that point to a remote server and tests all of these links to see whether they are valid. It has two buttons: Clicking the first button, Results of the Last Validation, will display a summary of the broken links found last time the validation was run. Clicking the second button, Validate External Links, will run the validation tool: Clicking Ok will begin the link check. OpenCms will display progress information, warning you at the end whether any broken links have been found. A failed link may be the result of network connectivity issues or temporary outages on the remote site. OpenCms has no control over this and simply reports the failed request. To fix a broken external link, you should switch to the explorer view and edit the file, locating the offending link and deleting or modifying it. While OpenCms checks internal links during the publishing process, it does not check external links. Thus, it is a good idea to periodically run this validation process in order to catch any broken or obsolete links.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Discount Web Hosting services
All you need to do to start the verification process is click Ok. OpenCms will then search all of the modified folders in the VFS and check all of the changed files looking for broken links. Progress is displayed on the screen. If any file contains a broken link, an error message will be displayed: In the screenshot above, the link validator warns that the files /playground/index.html and /playground/other_stuff.html both contain links to the non-existent page /playground/Bogus_page.html. To fix this, I would have to switch back to the explorer view, edit the files, and remove or change the problematic link. Returning to the administration view, I would be prompted to revalidate the links. Fortunately, OpenCms does not force you to fix the offending files at this stage, but when you attempt to publish the files, OpenCms will ask whether you want these files to be published when they have broken links. Clicking the Ok button at the bottom of the screen returns us to the Link Validation screen.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Discount Web Hosting services
When clearing history, you have a number of different options. You can either specify how many of the existing history entries to keep, or you can specify that history entries prior to a specific date be deleted. Looking at the History Settings screen, we saw how to set the number of stored file versions. On this screen, we can choose to delete existing history entries prior to a specific entry. Suppose that we set Number of stored versions in the History Settings screen to be 10 (the default). On the Clear History screen, the first drop-down list, Number of file versions to keep in the system, has the numbers 1 to 10. If we choose 3, for example, only the three most recent versions of each file will be kept in the VFS, and versions four to ten of the files will be deleted. This does not reset the number of stored versions to a value other than 10. The number of history items stored from this point on will still be ten. This is one way to reduce the amount of history data stored. But another way one which is often more useful in the practical world is to delete history information older than a specific date. You can do this with the Delete versions older than field. You can either enter a date into the text input field in the format mm/dd/yyyy (for example, 01/06/2006), or you can click the calendar icon and select the desired date from the pop-up calendar widget. Once you have selected one of these two options, clicking the Ok button will begin the deleting process. OpenCms will present a screen showing the progress. Once the process is complete, you can click the Ok button at the bottom of the screen to return to the File History screen.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Discount Web Hosting services
When you installed OpenCms, historical versions of all of the OpenCms default content were created. Clearing the history may result in clearing versions of those files. This is OK, as there is not necessarily a reason to keep this history information in the database, but it may be surprising to see that the history has been deleted for files that you have never edited. Link Validation The sixth screen in the administration view is called Link Validation. This screen contains tools for verifying hyperlinks contained in Page-type files in the VFS. This screen has two buttons, Internal Link Validation for verifying links to resources on the same server and External Link Validation for verifying links to some other server. The Link Validation screen is one of only two tools available to anyone in the Users group. (The other is the Gallery Overview screen.) Users who are not administrators or project managers can access the Link Validation screen and validate links on their own. If you are working with the Online project, the links for currently published resources are checked. If you are working with the Offline project or one of its sub-projects, links in documents in the Offline project are checked. Internal Link Validation Clicking on the Internal Link Validation button brings up the screen for testing links whose destination is within this instance of OpenCms. This validation tool will make sure that the link points to a resource that exists in the VFS. It tests links to images and downloads as well as links to other files.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Discount Web Hosting services
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
The History Settings The first of these screens, History Settings, allows you to specify how the history facility behaves. The first item, the Enable file history radio buttons, gives you the option of disabling history altogether. While this may conserve some space in the database, it will remove the safety net provided by the ability to revert to a previous version. The second item, the Number of stored file versions field, allows you to specify how many older versions of the file ought to be retained. You will only be able to revert back to these versions. By default, this value is set to 10, meaning only the ten most recent versions of the document will be retained in the history database. Usually, this is sufficient. A history entry is created each time a resource is published, not each time a resource is edited. If the default value is set to 10, then the last ten published versions of the file will be saved. Clicking Ok will save and apply the changes and return you to the File History screen. Clearing the History Clicking the Clear History button in the File History screen loads a screen that provides a way to selectively remove history information from 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
The Module version field is used to specify the release level (and the level of stability) of the module. In general, the OpenCms community uses the following convention: ... So 1.0.1 indicates that it is the first major release of the module, and that one minor revision (which usually includes only bug fixes) has been made. If a significant feature has been added, the minor version number should be incremented. If the module has gone through any major changes (particularly in the API), then the major version number should be incremented. Typically, until the module is stable, modules use 0 as the major version number. By default, then, OpenCms assigns our module the version number 0.1 the first minor version of the module. The Module group field is used to sort the modules by category. There are no established categories. Since our module is going consist primarily of templates, I have put it in the module group Templates. Sometimes a module needs to run special code during certain OpenCms events (such as startup, shutdown, publish, or module installation). To do this, developers can create a class, specified in the Action class field, that handles particular events. Specifying the class name here will ensure that the class is loaded and executed by OpenCms. An action class must implement the org.opencms.module.I_CmsModuleAction interface. In the Module Creator section, the Author name and Author email fields are used to provide information about you, the module creator. Beneath the Module Creator section, there is a section called Module Folders, which has six checkboxes. These checkboxes determine which folders are automatically created in the VFS. 1. Create Modulefolder: If this is checked, a folder module will be created in /system/modules. The module folder is where we will put all of the module files, so this box should almost always be checked. The five other folders listed here are subfolders of this folder, so this checkbox must be checked for the others to work. 2. Create templates subfolder: If this is checked, a folder named templates will be created in the module folder. When we create new templates in Chapter 6, we will use this folder, so it is a good idea to create it now. 3. Create elements subfolder: If this is checked, a folder named elements will be created in the module folder. This folder is used for storing pieces of jsp code or text files that the module requires. Usually, you should check this box.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Inexpensive Web Hosting services
During the course of module installation, OpenCms checks that all of the new module’s dependencies are already installed. If they are not, OpenCms will not allow the new module to be installed. The Module dependencies screen provides information on the module’s dependencies. These dependencies are listed in the Module dependencies table. If you create a module that uses resources from another module, you have create a dependency. But OpenCms does not automatically detect this. You will need to use the New module dependency button on the Module dependencies screen to add information about this dependency. When the module is exported, dependency information is exported with it. The Export Module Screen Clicking on the Export Module button on the first Edit Module screen will promptly export the module to the file system. Each time you export the module, the module minor reversion number will be incremented by one. That means that when we export the 0.5 version of the St. Nicholas Template module, it will become version 0.6. You can manually edit this field from the Edit Module (tool) button on the Edit Module screen. The new module will be written to the server’s file system, in the directory $CATALINA_HOME/webapps/opencms/WEB-INF/packages/modules. Deleting a Module The seventh and last button on the first Edit Module screen is called the Delete Module button. Clicking on this button will immediately remove the module from OpenCms. Creating a Module Modules can provide a very convenient way of packaging your resources. In particular, templates, jsp files, and java code ought to be stored in modules. As we begin working with templates, we will use a particular module for storing the new template files. We will create this module now. Clicking the first button on the Module Management screen loads the New Module screen.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Low Cost Web Hosting services
The Package name field is for the complete java package name. The format is top-level domain name (e.g. .com, .org, .edu), specific domain name (e.g. packtpub), and then any number of additional package names. It is like a directory path that points to the particular project within your organization it should be distinguishable from all other packages on the Internet. The second field, Module name, should contain a human-readable title for the module, and the third field, Module description, should describe what the module provides.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Low Cost Web Hosting services