FormSaver Version History
What's New in Version 1.7.5 ?
- You asked.. we listened! FormSaver now ignores any fields named "submit". That means you can now use some HTML editors without having to edit your HTML manually after you create your forms to delete the "NAME=SUBMIT".
- Behind the scenes improvements and bug fixes.
- Recompiled with W*API 1.3
- Recompiled with MoreFiles 1.4.8
- Recompiled with the latest version of CodeWarrior (Pro 3, with the latest updates)
What's New in Version 1.7.4 ?
- Tested with AppleShare IP
- Better use of response buffers, and other network, memory, and speed optimizations.
- 68K code optimized for 020/030/040 processors. 68000 processor no longer supported.
- Bug fixes.
- Recompiled with the latest CodeWarrior libraries/compilers.
- The ACGI version has been retired.
What's New in Version 1.7.3 ?
- Encoded URL and form data support.
- W*API 1.2 Support, and backwards compatible with older servers.
- Quid Pro Quo 2.0 support
What's New in Version 1.7.2 ?
- Multi-homing support by using the workaround tag. The workaround tag is now always used if present.
- Updated all Mac and compiler libraries to the latest versions.
- FormSaver will continue to be a product of Pliner Products.
What's New in Version 1.7.1 ?
- Supports W*API 1.1. Plugin version now requires WebStar 1.3.2 or later.
- Now works with aliases in the file path! Even to volumes over a network!
What's New in Version 1.7.0 ?
- Now JavaScript Savvy! Put JavaScript code in your .fsr files! (FormSaver Plus only)
- New sample files and updated offline documentation now included.
- Fixed bug in plugin version where an extra space was being saved after last field.
- Forms at named anchors now work. (myform.html#here)
- PowerPC Instruction scheduling was turned on. Now FormSaver is even faster.
What's New in Version 1.6.4 ?
- Fixed a bug introduced in 1.6.3. This version was released 3 days after 1.6.3.
What's New in Version 1.6.3 ?
- The "workaround" field now works. The workaround field allows FormSaver to work
with the web browser included with AOL 2.6 and 2.7. It also fixes incompatabilities
with other browsers that don't need the workaround field, such as InterCon's.
What's New in Version 1.6.2 ?
- FormSaver now works with up to 5000 fields. (Was 999 as of version 1.3)
- More efficient memory usage. (That's why there's no additional memory required for the additional fields)
- Fixed bug that stopped FormSaver from working if a port number was in the URL.
- Fixed a bug that would prevent required fields from being checked, in some rare cases.
What's New in Version 1.6.1 ?
- New optional "command" tag, so that the "$SAVE" no longer needs to be in the URL. Instead, use
<INPUT TYPE="hidden" NAME="command" VALUE="SAVE">.
- (Previously undocumented feature) To make sure your forms are working, replace the word "SAVE" with "RESPOND" or "DEBUG". Access your form (don't forget to reload it), fill it out, and press the submit button. RESPOND will give a simple response. DEBUG will actually list all the field data that is submitted using your form. You can do this in the command tag listed above, or in the older method of putting the command in the FORM tag ($SAVE or $RESPOND). Don't forget to change it back to SAVE when making the file public.
- FormSaver now ships with FS Secure 1.0. Be sure to read the READ ME for FS Secure.
- Error messages now properly displayed for forms that are not set up properly (Bug introduced in 1.6.0)
- Source code consolidated between plugin and CGI versions.
What's New in Version 1.6.0 ?
- Plugin version now available! (For FormSaver Freeware or FormSaver Plus. Not for FormSaver ISP.)
- Now works with default files. With CGI's, the default file must be set to "default.html" in the
WebStar preferences. With the plugin version, you can set WebStar to use any filename you wish (such
as "index.html"), and FormSaver will still work with it.
- Data files (.fs) are now correctly saved with carriage returns AND line feeds at the end of
every line. This provides file compatibility with all platforms (UNIX, DOS, or Mac). This was not
always working in previous versions.
- Many internal changes, to improve speed, reliablility, and memory usage. These changes were
necessary for the Plugin version, and carried through to the CGI version.
- FormSaver Plus no longer verifies domain names or IP addresses. This was more for piracy
prevention than anything else. Now it'll be easier for you when your IP addresses change.
- FormSaver is now owned by Pliner Products, started by the author of FormSaver. Keep your eyes
out for new products!
What's New in Version 1.5.3 ?
- Freeware version now distributed as a FAT binary.
- Error messages were improved.
- FormSaver works if a port number is specified in the URL.
- When verifying domain name in registered versions, it checks that the machine name ends with your
domain name. For example, if you registered "domain.com" FormSaver will work with "www.domain.com",
"alt.domain.com", "domain.com", etc. This makes registration easier, because you only have to
register your one domain name.
- Default "Data Saved" message (Freeware version or if you don't have a .fsr file) was modified.
- Lots of internal changes to make managing the various versions easier.
What's New in Version 1.5.2 ?
Two changes affecting those odd web browsers (AOL, etc) which require the "workaround" tag:
- Serious bug fixed. This would give error messages to users and would sometimes save responses into the wrong data files, if you use more than one form with FormSaver.
- FormSaver now allows these browsers to create new data files when necessary.
What's New in Version 1.5.1 ?
- All references to the FormSaver web page and E-mail address have been updated to the new domain name, "pliner.com".
- Recompiled with the latest CodeWarrior updates
- Minor code improvements
What's New in Version 1.5 ?
- Compatible with WebStar SSL! (As of 1.4.2, which was not released publicly)
- Multiple-type fields are now supported! ("checkbox", "multiple", and multiply-defined fields)
- Numfields tag is now optional! Now it's even easier to set up your forms!
- Some bug fixes, minor enhancements, and better handling of low memory situtations
What's New in Version 1.4 ?
- Field name are no longer case-sensitive (1.4)
Field1, field1, FIELD1, and FiEld1 should all work.
- Workaround for Incompatible Web Browsers (1.4.1)
Some web browsers (AOL's/InterCon's, and IBM's) do not send the "referer" information to the Web server. FormSaver relies on this information. I have created a workaround for this problem.
Unfortunately, I had to change the form format again. You will need to update all of your forms. This new format will not work with previous FormSaver versions, so you must update all of your forms and the FormSaver.acgi all at once. The new format is better because it is more transparent to the user.
(Version 1.4 was not released, because 1.4.1 was almost done.)
(Version 1.4.2 was not released, because 1.5 was almost done.)
What's New in Version 1.3?
- Fixed incompatibility with clients using NetScape on a Sun.
- The number of fields is not limited to 49 anymore. It is now 999.
What's New in Version 1.2?
- A sample page is included. Sample.fsx and Sample.html. Put these online on your web server. They must be in the same directory. Load the web page and try out FormSaver. Use it as a template if you wish. Be sure to visit the documentation pages though!
- FormSaver now changes all carriage returns users enter into spaces. This way, the tab-delimited file will work when importing into a database. FormSaver already turned tabs into spaces.
- Several outdated links to the FormSaver web page were updated.
What's New in Version 1.1?
- The Freeware version now supports an unlimited number of pages! (Was 3)
- The Freeware version no longer requires domain names in preferences, for easier setup. In fact, installation is now a one step process (Put it in the Webstar folder.... That's it.) There is no preferences dialog anymore.
- FormSaver now supports designating required fields! FormSaver will tell users if they forgot to fill in a required field. You can even optionally set up a file that the user will see if this occurs. (Any version!)