LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Eric Thomas <[log in to unmask]>
Thu, 30 Nov 2006 04:09:10 +0100
text/plain (47 lines)
I know this looks like one problem, but in reality it is two completely
separate problems that happens to have similar symptoms. Problem #1:

>>> Error in line 1642 of default.mailtpl: invalid argument <<< -> .FO OFF
<-

This is because of a human error that caused at least some of the unix kits
we put out on Release Day to contain the Windows version of default.mailtpl
:-( This file has CRLF line ends as you would expect on Windows. All unix
kits were refreshed as soon as we found out. You can remove the CR in
default.mailtpl using for instance 'zip -ll' or any other suitable method,
and this error will disappear. You do not need new binaries to correct this.

This error only happened on unix. We put the appropriate file in all other
kits.

Problem #2:

> problems with the dynamic pages (exposed javascript and template
> comamnds and comments on every page). Now it works better, but it
> looks like spaghetti and the javascript stuff is futzed.

This is a bug in WA that unfortunately was missed during testing. I know
that, at this point, it may be hard for you to believe that we could
possibly have missed something that obvious ;-) But, if you restore the
original default.wwwtpl from the kit (and make sure it gets copied to the
web archive directory), you will find that all the errors are magically gone
until you dig really deep into the interface. It took me a while to believe
this as well, as it seems totally illogical, but it is true! Only a few
functions are affected with the original file. Because of the similarity, it
took us a while to realize that customers reporting problem #2 (and, in most
cases, also reporting problem #1 in the same incident) were not customers
who would become happy campers after applying fix #1. We thought the updated
kit with the correct file would solve both problems, but that was not the
case.

This bug only happens on unix and VMS. The only solution is to reinstall
using the updated kits. You need not only a new default.wwwtpl but also a
new wa binary. In a pinch, restoring the original default.wwwtpl will buy
you time to download and install the updated kit.

I will let my colleagues comment on the script errors as I have no
involvement in creating any of the installation scripts. I don't even know
how they work :-)

  Eric

ATOM RSS1 RSS2