1. Duplicate Document File Checking - When generating a Project, Webgenz will check to see if any Document is generated more than one time. If so, a warning will be produced.
   
   
2. Positioning of Webgenz Screen - The automatic centering of the main Webgenz screen upon startup will now take the Windows taskbar into consideration.
   
   
3. Macros Listbox Bug Fix - When displaying "all macros" in the Macros listbox, the ordering of Macros with the same name will be consistent with the inheritance hierarchy.
   
   
4. Macros Listbox Pop-Up Menu Displays Custom Options - The Custom Options displayed on the pop-up menus of the other listboxes on the main Webgenz screen will now appear on the Macros listbox pop-up menu.

1. Enhanced Command Line Interface - The following enhancements have been made to the Webgenz CMS command line interface:
   
   
   • You can now reference any Webgenz Project (.web file) on the command line. Previously, you were restricted to referencing projects that existed in the Webgenz Project History File. This restriction has been removed.
     
     
   • You can now specify the Document Root Path on the command line. The Document Root Path that you specify on the command line will override the Document Root Path specified in the Project file (.web file) and it will only be used for the one-time project generation that is triggered from the command line (i.e. it will not overwrite the Document Root Path setting in the Project file).
     
     
   • You can now specify the Generate Modified Documents Only setting on the command line. The setting that you specify on the command line will override the default setting for the one-time project generation that is triggered from the command line.
   
   Read more about the Webgenz CMS Command Line Interface >
   
   
2. Enhanced Project Browser - The Project Browser now allows you to reorder the list of Projects that appear in the Projects drop-down on the main screen.
   
   
3. The "Concatenate" Advanced Macro Tag has been Deprecated - With the "Improved Handling of Multi-line Macros" introduced in version 6.1.0 (see below), the "concatenate" Advanced Macro Tag has been deprecated. For backward compatibility, it can still be referenced, but it is no longer required.
   
   
4. Consolidation of webgenz.ini and ui.ini - The ui.ini file has been removed. The settings previously stored in the ui.ini file have been moved to the webgenz.ini file.

1. Support for Line Continuation Characters - If you place two backslash characters (this is configurable) at the end of a line, Webgenz will append the following line to it. This is helpful if you have long Macro definitions (especially when using parameters) and you want to allow them to wrap onto multiple lines.
   
   
2. Support for "Required Macros" - If you use the Advanced Macro Tag "$" (example: [@$SOME_MACRO]), Webgenz will produce a warning if the Macro value is blank.
   
   
3. Warning When Exceeding the Maximum Number of Parameters - Previously, Webgenz did not produce a warning when the maximum number of parameters for a Macro was exceeded. Webgenz will now generate a warning if you exceed the maximum number of parameters as defined on the "Properties -> Memory Management" screen.
   
   
4. Improved Handling of Multi-line Macros - Prior to version 6.1.0, a reference to a multi-line macro had to appear on a line by itself. Otherwise, a warning would be generated. This has been changed. Read more on how Webgenz handles multi-line Macros >
   
   
5. Additional Custom Application Options - You can now integrate a third custom application on the Webgenz toolbar. In addition, you can also include 2 more custom applications (for a total of 6) on the popup menu of the listboxes.
   
   
6. File Icons for Source Files Referenced from the Default Root Path - Source files reference from the default root path (if in use), will now display with a different icon in the listboxes on the Webgenz main screen (if the "Show Attributes" checkbox is checked). This is helpful to identify when you are accessing a "default" (and potentially shared) file vs. a file that is only used by the current Project.
   
   
7. Option to Ignore Missing Files During Project Generation - If a source file is missing when you generate a Webgenz Project, you now have the option to ignore the error and allow the Project generation to continue. Prior to 6.1.0, missing files always halted the generation of a Project.

1. Advanced Macro Tag for Conditionally Including Code - You can now use the Advanced Macro Tag [@{MACRO_NAME] to conditionally include entire blocks of HTML code if a Macro has a value. With the addition of this Advanced Macro Tag, the "Non-Blank Delete" Advanced Macro Tag has been deprecated. See an example >
   
   
2. Improvement to Parent Reference Advanced Macro Tag - The behavior of the "Parent Reference" Advanced Macro Tag has changed. Rather than reference the next file in the Content File hierarchy, the Advanced Macro Tag will now reference the next level in the Content File hierarchy. This will insulate your code from unintended changes which could result from changing the list of files in the Content File hierarchy. For backward compatibility, the setting parent-reference-tag-is-by-file has been added to the .web file for a Project.
   
   
3. Command Line Options - A new command line option has been added to Webgenz CMS that will allow you to run Webgenz CMS from the command line in a minimized state. This is useful if you prefer not to display the Webgenz CMS UI when running Webgenz CMS from the command line. Read more >

Webgenz CMS 5.9.5 (6/11/2002)

1. Improvements to "Generate Modified Documents Only" Setting - Webgenz now compares a newly generated Document against a previously generated Document to see if the Document has changed. If the Document has not changed it is not written and, accordingly, the timestamp is not updated. This is useful to ensure that certain file types (for example, .jsp files) are not unnecessarily recompiled when released into a production environment. (Previously, Webgenz only compared source files to determine if a Document should be generated when the "Generate Modified Documents Only" setting was checked).
   
   
2. Generated Files List - Webgenz will now write a list of generated files. By default, this list will be written to "generate.txt" in the Webgenz temp directory. The location of the file can be overridden by using the "generated-files-log-file" setting in the .web file for the Project. This file could be used as input to a release script or other process that pushes new or changed files to a production environment.
   
   
3. User Interface Performance Improvements - When using the "Show Attributes" option, there was previously a slight delay in refreshing the Documents and Content Files list boxes when changing Folders (especially if a Folder contained a large number of Documents). This delay has been eliminated.
   
   
4. Ability to View "Read-Only" or "Writable" Files - When using "View -> Content Files" or "View -> Templates" you now have the option of showing "All Files", "Read-Only Files", or "Writable Files". If you are using a source/version control system (see Tips & Tricks for more information) this can be used to see which files you currently have checked-out (and potentially avoid forgetting to check-in new files).
   
   
5. Duplicate Macro Definition Checking - Webgenz will now check for duplicate Macro definitions in the same Content File. If a duplicate Macro definition exists, Webgenz will generate a warning.

Webgenz CMS 5.9.1 (5/16/2002)

1. Webgenz now provides the ability to have two external root paths for source files (Content Files, Templates, and the Project Definition File) that will be used to locate files. These root paths appear on the "Source Files" section of the "General" tab of the "Project Properties" screen and they are labeled "Root Path" and "Default Root". If Webgenz does not locate a source file using the "Root Path", the the "Default Root" will be used. This is useful if you need to build multiple versions of essentially the same site using the same source base, but overriding specific files on a case-by-case basis. For example, an Application Service Provider (ASP) would find this useful as a way to create custom branded versions of the same web site.
   
   
2. Webgenz also provides the ability to override default value of Macro parameters. Consider the following Macro:

        [@TEST(@a:World)]:
        Hello (@a).
        [@]
        

   If you reference this Macro as follows:

        [@TEST(@a)]
        

   The result will be:

        Hello .
        

   By including the Macro parameter in the reference without a value, it overrides the default value for the parameter.

Webgenz CMS 5.8.9 (4/1/2002)

1. "Browse" support has been added when selecting default directories for Documents, Content Files, etc.
   
   
2. Syntax has been added to the Project Definition File to exclude Folders from using the Project Macro file (if defined). This syntax is as follows:

        [FOLDER_NAME]*
        

Webgenz CMS 5.8.7 (3/2/2002)

1. Support for adding formatting options to the reserved Macro DATE. This is accomplished by using the "format" parameter on the DATE Macro as follows:
   

        [@DATE]
         3/8/2004 4:38:41 AM
        
        [@DATE(@format:mm/dd/yyyy)]
         03/08/2004
        
        [@DATE(@format:dddd, mmmm dd, yyyy)]
         Monday, March 08, 2004
        
        [@DATE(@format:ddd, mmm dd, yyyy)]
         Mon, Mar 08, 2004
        
        [@DATE(@format:mm/dd/yy hh:mm:ss AM/PM)]
         03/08/04 04:38:41 AM
        
        [@DATE(@format:h:m:s a/p)]
         4:38:41 a
        

2. The addition of detailed search and replace results when using the replace function. If you've customized the pop-up menus to integrate with version control software, this screen now allows you to check-out read-only files.
   
   
3. The ability to access the customized pop-up menu from the Folders list box. If you are using the options on this menu to integrate with your version control software, you will now be able to check-out the Project Definition File from this pop-up menu.
   
   
4. The Editor Command Line Options field on the "Tool -> Options -> Advanced" screen now provides the ability to reference the file name with the replaceable parameter %FILE%. This is only needed for editors that expect the command line options to precede the file name. By default, Webgenz will assume that the file name precedes the command line options. To override this default behavior, use the parameter %FILE% to reference the file name. For example, to open a file in Emacs text editor and place the cursor at the correct line number you would use the command line options: +%LINE% %FILE%. Read more about text editor integration.
   
   
5. The Command fields on the "Tool -> Options -> Pop-Up Menus" screen also provide the ability to reference the file name with the replaceable parameter %FILE%. By default Webgenz assumes that the file name will follow the command and the command line options specified on the "Tools -> Options -> Pop-Up Menus" screen. However, some applications expect the file name to come before the command line options. If this is the case with the application that you are integrating into Webgenz you can use the replaceable parameter %FILE% to reference the file name in the command.
   
   
6. The Advanced Macro Tag to concatenate Macros will now allow parameters to be passed to those Macros.
   
   
7. The reserved Macro WEBGENZ_PROJECT_NAME has been added. When this Macro is used, it will be replaced with the name of the Webgenz Project.

Webgenz CMS 5.8.5 (1/10/2002)

1. The ability to define "project-level macros". Project Macros take precedence over Macros defined in all other Content Files. This can be useful to set paths or other environment variables at the time of a build, with very little administrative overhead -- no changes to the Project Definition File or other Content Files are necessary. You can set the Project Macro File path in the Project Properties -> Advanced screen.
   
   
2. The ability to open the "associated application" (in Windows) when double-clicking on a file in the Documents listbox. Many Webgenz users maintain XML and XSL files with Webgenz. This feature makes testing/viewing these files in an XML editor much easier. See the Tools -> Options -> General screen to set the default double-click behavior.
   
   
3. Prior to this version, parameter values passed into Macros were trimmed. This was undesirable as it did not allow you to pad parameter values with spaces, nor could you override a default parameter value by simply passing whitespace. Accordingly, parameter values are no longer trimmed. If you relied on the fact that parameter values were trimmed, you can maintain this functionality by adding the line "trim-parameter-values=1" to the .web file for your Project.
   
   
4. Improved search and replace functionality. In addition to increasing the size of the search and replace screens, the replace function will now report how many occurrences of the search string were found in read-only files.
   
   
5. More flexibility in the way HTML optimization is configured. You can now create an exception list for HTML optimization based on files extensions. You also have greater control over optimization on a file-by-file basis. See the Project Properties -> HTML Optimization screen for more details.
   
   
6. You now have more control when importing configuration options from a previous version of Webgenz. You can now enter a custom path for importing the Project History File. This is necessary when importing Program Options from another machine across a network.
   
   
7. You can now turn off all error message prompts during the generation process. If you turn off error message prompts, the errors will still be reported in the status window and in the log file. See the Tools -> Options -> Advanced screen for more details.
   
   
8. The default number of nested Macros has been increased to 50. In addition, Webgenz will now produce an error message if a Project contains more then the maximum number of nested Macros, as specified in the Project Properties.
   
   
9. The ability to control HTML optimization by using HTML comments within a file was not working. It is now fixed.

1. Webgenz now provides an option to automatically sort the items in the Folders listbox. As the size of your Project grows, you may want the ability to display the items in the Folders listbox alphabetically. You'll find this option on the "Tools->Options->Advanced" screen (in the Display section).
   
   
2. The Webgenz main screen can now be displayed about 50% larger. This is very useful if your Project has many Folders, Documents, etc. You'll also find this option on the "Tools->Options->Advanced" screen (in the Display section).
   
   
3. There are now reserved Macros to include the Webgenz Folder name and the Webgenz Document name in generated Documents. This is a debugging aid that helps associate generated Documents with their location in a Webgenz Project. It is especially helpful when working with dynamically generated pages (for example, .JSP pages, .ASP pages, pages served by a CGI program, etc.), where the URL of a web page does not always identify the source document.

   The reserved Macros are WEBGENZ_FOLDER_NAME and WEBGENZ_DOCUMENT_NAME. (You can override these default Macro names in the "Project Properties->Advanced" screen). A typical application of this feature would be to add a line similar to the following to a template file:

   <!--[@WEBGENZ_FOLDER_NAME]:[@WEBGENZ_DOCUMENT_NAME]-->
   

4. You can now continue past errors when generating a Project. For certain errors, you can now select to ignore the error and continue generating the Project. (This support has not been implemented for all types of errors). You will see a report of the error in the log file after the Project generation is complete.
   
   
5. You can conditionally add a space before the Editor Command Line Options. There is now a checkbox on the "Tools->Options->Advanced" screen to control this behavior. For example, when using TextPad you would set the command line options to:

   (%LINE%,1)
   

   and select not to include a space between the file name and the options.
   
   
6. This version also fixes a bug when using drag & drop from the Documents listbox.

Webgenz CMS 5.7.2 (9/16/2001)

1. Webgenz now includes the ability to perform a text search through generated web site documents. Previously, Webgenz provided the ability to search content files and templates. Now, you can also search generated files. This is useful to understand if certain macros are included in the generated documents. This option is available on the Main Menu under "Search->Find in Documents...". Also, if you double-click on the "Search Status" listbox after running a search, you will detailed search results in a text file.
   
   
2. To make it easier to upgrade from one version of Webgenz to the next, you can now import Program Options from a previous installation of Webgenz. This feature can also be used to share Program Options between multiple Webgenz users. You can access this feature from the Main Menu under "Tools->Import Options...".
   
   
3. When Webgenz generates a project, it stores temporary files in a "temp" directory. If you run multiple instances of Webgenz and generate multiple Webgenz projects simultaneously, you can now specify the directory for temporary files on a project basis. This option is available on the "Advanced" tab of the Project Properties screen. If you enter a relative path, it will use the Default Drive (if specified) in the Program Options.
   
   
4. The Project History file path in the Program Options can now be a relative path. If you enter a relative path, it will use the Default Drive (if specified) in the Program Options.
   
   
5. This version also includes some additional error checking and minor bug fixes.

Webgenz CMS 5.6.6 (7/26/2001)

1. Minor changes to the UI to avoid refreshing the entire display when the "Show Macros" list box is checked.

Webgenz CMS 5.6.5 (7/11/2001)

1. If you configured Webgenz to jump to a specific line in your text editor, this feature is now available from the Detailed Search Results listbox and from the Folders listbox.

Webgenz CMS 5.6.4 (7/8/2001)

1. With this release, Webgenz supports opening up a Content File in a text editor and positioning the cursor right at the Macro definition that you want to edit. This feature can only be used with editors that support a command line option to position the cursor at a specific line number. To use this feature, in the "Tools->Options->Advanced" screen, you need to set the "Editor Command Line Options" to the appropriate command string for your text editor to open a file and position the cursor. One editor that supports this feature is EditPlus. If you are using EditPlus, you would set the "Editor Command Line Options" to: "-cursor %LINE%:1".
   
   
2. Pressing the Enter key when the focus in on the Folders, Documents, Content Files, or Macros listboxes will have the same effects as double-clicking on the listboxes.
   
   
3. You can now view all Macros used in the generation of a document in a single list. In the "Tools->Options->Advanced" screen select the options "Show All Macros in a Single List". When you do this, you will see an "(all macros)" entry in the Content Files listbox. Select this entry to view all Macros in a single list. This is especially helpful if you are hunting for a specific Macro. Note: if there are multiple macros with the same name, these macros will be listed in their inheritance order.
   
   
4. Color-coding of Content File icons to represent local Content Files (yellow), folder Content Files (red), and global Content Files (blue).

Webgenz CMS 5.6.0 (5/23/2001)

1. A "Project Browser" (under the Tools menu) which allows you to view and edit any Project File (.web) or Project Definition File (.txt). This provides an easy way to edit these files across multiple Projects.
   
   
2. An option to avoid a refresh of the display after a Project is generated. The only time this is really necessary is when you are using the "Show Attributes" option. Depending on the size of your Project there may be a slight delay when refreshing the display after a Project is generated. To avoid refreshing the display you can uncheck the "Auto-Refresh After Document Generation" option in the "Tools->Options->Advanced" screen.
   
   
3. There are now icons to indicate if a document is using HTML Optimization when using "Show Attributes". If Level 1 optimization is used a small blue square is displayed. If Level 2 optimization is used, a small black diamond is displayed.