Miva Engine 3.75
Release Notes

Miva Engine 3.75, released November 13, 2000 adds the following functionality
and fixes.

New Functionality
-----------------

Windows ® Platform

• Windows 2000 support.
• The ability to change the default user in Windows NT ® . This feature fixes the
  problem where unauthorized users could gain access to Miva scripts through
  FrontPage ® extensions.


Unix Platform

• A new configuration file option, authuserdir. It authorizes all users (except root)
to use Miva. If the value starts with slash (/), then it is assumed to be an
absolute path, and no other checking is done. If it does not start with a slash,
the directory is appended to the user's home directory.
Note: If you also specify an authfile, an entry for a user in the authfile will override the
authuserdir setting for that specific user.


Fixed Items

The following items have been fixed in this release.

Function & Tag Fixes

• Fixed a problem where characters above 128 that were being passed to
  asciivalue output a negative number.

• <MvHIDE> encrypts the text properly. It encodes the contents in a hidden
  variable. This allows you to use <MvHIDE> with a variable that contains
  quotation marks, and other characters.

• <MvReINDEX> is indexing the deleted records.

• <MvPRIMARY> now properly requires either a View or Index attribute,
  otherwise returns a syntax error.

• Missing commas in <MvCREATE> are now detected.

• <MvLOCALIZED-TEXT> now reads %% as % so it can be placed in text.

• All <MvCOMMERCE> errors are now fatal, by default.
  BSD Fixes

• The built-in timezone ( ) function in FreeBSD and BSDi4 now properly display
  the date in DST (Daylight Savings Time).

• BSDI logs the correct year (2000).

• Fixed problem with the Miva Engine receiving a SIGPIPE signal when an
  invalid response is received from an SMTP server.


Script Fixes

• When two scripts attempt to simultaneously pack the same database in the
  Windows NT environment, a crash no longer occurs.

• ASCII char 0xFF no longer causes scripts to exit.

• On Windows NT, the Miva Engine no longer allows scripts if the user did not
  specify a data directory.


Miscellaneous Fixes

• All available packages are being displayed in packages.mv.

• If workdir is defined, explicitly denied users will not be able to gain access to
  Miva scripts.

• Miva Engine handles a bad index file appropriately (no longer crashes).

• Empty Macros are treated appropriately.