WWW_ALLOW_LEGACY_INTERFACE
Platforms
Non-VM 17.0 and later
Abstract
Numeric value determining whether the site, and by extension, individual lists, may continue operating in legacy 16.5 "compatibility mode".
Example
z/VM: |
<not available> |
Unix: |
WWW_ALLOW_LEGACY_INTERFACE=0 |
Windows: |
WWW_ALLOW_LEGACY_INTERFACE=0 |
Note for Unix: WWW_ALLOW_LEGACY_INTERFACE has been pre-exported in the "go" script which ships with LISTSERV 17.0 and does not need to be exported separately in go.user |
Details
WWW_ALLOW_LEGACY_INTERFACE allows the site administrators to decide whether the site, and by extension, individual lists, may continue operating in legacy 16.5 "compatibility mode". The options are as follows (the default value is in bold):
WWW_ALLOW_LEGACY_INTERFACE=0 |
The web interface operates in 17.0 "native mode", and the 16.5 legacy interface is not allowed. This should be the standard setting once migration to the new interface is complete. This will be the default in the next version of LISTSERV. |
WWW_ALLOW_LEGACY_INTERFACE=1 |
The web interface operates in 17.0 "native mode", but the 16.5 legacy interface is allowed, either for the whole site or on a list-by-list basis. This is the default for 17.0. |
WWW_ALLOW_LEGACY_INTERFACE=2 |
The web interface operates in 16.5 "compatibility mode". The 17.0 interface is not allowed, and all new 17.0 features in the interface are disabled. This setting is supported only with OLD_WEB_INDEXES=2. This is a compatibility mode only. |
While there are three available settings each for the two new variables, it should be noted carefully that not all combinations are supported. Following is a compatibility matrix indicating which combinations are supported (green), supported for special situations (yellow) and unsupported (red):
OLD_WEB_INDEXES=0 |
WWW_ALLOW_LEGACY_INTERFACE=0 |
Supported Standard setting once migration to the new interface is complete. This will be the default in the next version. |
WWW_ALLOW_LEGACY_INTERFACE=1 |
Supported Default setting for 17.0. This setting allows staged migration to the new interface. |
|
WWW_ALLOW_LEGACY_INTERFACE=2 |
Unsupported Degraded functionality. |
|
OLD_WEB_INDEXES=1 |
WWW_ALLOW_LEGACY_INTERFACE=0 |
Unsupported Maintaining both old and new indexes only makes sense if both interfaces are allowed. |
WWW_ALLOW_LEGACY_INTERFACE=1 |
Special Situation This setting can be used if some lists need to use the old interface for a long time. However, rebuilding both sets of list indexes for lists with very large archives can slow down the server. |
|
WWW_ALLOW_LEGACY_INTERFACE=2 |
Unsupported.
|
|
OLD_WEB_INDEXES=2 |
WWW_ALLOW_LEGACY_INTERFACE=0 |
Unsupported
|
WWW_ALLOW_LEGACY_INTERFACE=1 |
Unsupported
|
|
WWW_ALLOW_LEGACY_INTERFACE=2 |
Level Set Mode
|
The combinations highlighted in red are not supported and will not be discussed further. The combinations highlighted in yellow are supported but not recommended for general use.
Default Value
1
See also
List level setting Misc-Options= LEGACY_INTERFACE
What's New in LISTSERV Version 17.0