Date: Sat, 10 Mar 2007 05:02:41 -0400
From: WINSERVER SUPPORT
To: all
Subject: Re: [WINServer] AUP GAMMA v6.2.452.1 is now Available
Newsgroups: winserver.public.gamma.testing
Message-ID: <
1173521232.40.0@winserver.com>
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 149
Thanks to Dave Gourd who founds some missing images.
The AUP GAMMA was updated to include the missing images. Answer yes to
the GRAPHICS update question and manually unzip WCWEBAUTH.ZIP to get the
new errors.wct.
The images in question were:
http\public\graphics\loginnew.gif
http\public\graphics\wcLogoTop.gif
Other images were added as well:
http\public\graphics\loginhtml.gif
http\public\graphics\loginclient.gif
With the three login*.gif images, these are the three buttons you see at
http://beta.winserver.com. These buttons are included in the new CD distribution as part of the new DEFAULT.WCT public home page.
WcLogoTop.gif is just a SSI Wildcat! logo image that will be shown by ERRORS.WCT if the "site.info.image" is not found.
To define your site.info.image file, do the following:
1) Create a folder HTTP\TEMPLATE\CUSTOM
2) Copy HTTP\TEMPLATE\GLOBALOPTS.INC to the CUSTOM folder.
3) Edit the copy and at near the bottom you will see:
<!-- Site Info -->
@set site.logo.image=@
@set site.logo.image="/public/graphics/banner.gif"@
You might still have this banner.gif from an old distribution. We
renamed it to DEMOBANNER.GIF to allow you to create your own and call it banner.gif.
In any case, this is where you define the path to your site.logo.image
file. If the file is missing, then /public/graphics/wcLogoTop.gif will
be displayed instead.
By creating and using the CUSTOM folder, you can edit any of the
template files and not lose your changes in future updates.
--
HLS
Hector Santos wrote:
After I installed this new update at winserver.com, with my custom
pages, I discovered I needed two changes to two templates to make it
perfect for everyone:
1) in http\errors\UserNotLogged.wct, we want to disable the inclusion of ERRORS.WCT at the top and also display the HTTP.HTTP.ERRORMSG display:
2) in http\public\login.wct, we want to add the inclusion of errors.wct
if cookie-based login is off.
This makes it 100% perfect and it also SOLVES the old complaint that
when the user clicks the LOGIN button on your home page, we get the
login form with the initial erroneous "Unauthorized access" message.
Now it is PERFECT and it works for ALL Modes:
- No more initial Unauthorized Error when you first
click LOGIN like many of you wanted, and
- It displays the proper error when the user cancels or
enters bad information.
PERFECT!
The AUP GAMMA server was updated with the two changes in WCWEBAUTH.ZIP.
Unzip it when you update.
Also, thanks to Rob Williams for finding a NT 4.0 RPC loading issue.
This is described in the AUP.CHM where the server was updated for
Windows XP/2003 Remote RPC related security issues. The new RPC feature added made the Wildcat! server fail to load under NT 4.0. That was also fixed in the current gamma update since obviously NT 4.0 can't use the
new XP/2003 RPC security feature. Thanks Rob!
--
HLS
Hector Santos wrote:
The new v6.2.452.1 AUP GAMMA is now available to AUP subscribers.
To access the AUP GAMMA server, type the following from your Wildcat folder: >>
AUTOUPDATE /GAMMA
This is a major update with many new features and enhancements, mostly
on the web side. Some fixes, a few security oriented. Overall, it is
an incredible update to prepare us the future.
It is PLUG and PLAY, but to gain 100% of the new benefits in the new
LOGIN error displays, you to manually unzip WCWEBAUTH.ZIP or just
extract, two files:
http/errors/errors.wct
http/errors/usernotloggedin.wct
and delete (or rename it), any of the following IF IT EXIST
http/closed.htm (or .wct)
http/errors/closed.htm (or .wct)
http/errors/unauthorized.htm (or .wct)
If they don't exist, you are all good. If they exist, you may keep it
without a problem, but you won't see the new and improved logic in
errors.wct.
The new http/errors/errors.wct is a "catch all" login error display file
which will explain to the user whats going on with the login error and
it will enable all the options the user can use. For example, if you
have an OPEN SIGNUP system, it will give the user the option to click
"CREATE NEW ACCOUNT", if you have a CLOSE/QUESTIONNAIRE and you have a
QUES\QUESCLOS.DAT file, it will offer the user the option to run the
questionnaire, etc. If you have a CLOSED system the user has no options
but to go back to the home page or try to login again, etc.
To see what I mean of what the errows.wct looks like, you can go to
http://beta.winserver.com. I have not updated http://www.winserver.com
yet with this gamma, but I will either tonite or tomorrow.
Again, you don't need to use it, and your update will work the same.
Either way, please send all comments here or directly to me at
winserver.support@winserver.com
I want to thank all the testers, especially Chris Weis for all their
hope and input.
Enjoy and TGIF!!
--
HLS
--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)