Newsgroups: wclistserve.win.server
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.6)
for WINServer@winserver.com; Sat, 24 Nov 2018 22:22:25 -0500
Received: from [192.168.1.68] ([99.121.5.8])
by winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP
id 2113079359.1.3596; Sat, 24 Nov 2018 22:22:24 -0500
Message-ID: <5BFA1578.80507@winserver.com>
Date: Sat, 24 Nov 2018 22:22:32 -0500
From: Hector Santos
Organization: Santronics Software, Inc
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101
Thunderbird/24.8.1
MIME-Version: 1.0
To: WINServer@winserver.com
Subject: Re: [WINServer] HTML Who is Online
References:
<025101d48431$993a0f50$cbae2df0$@robertwolfe.org>
<11c301d4845b$28ad3f80$7a07be80$@robertwolfe.org>
In-Reply-To: <11c301d4845b$28ad3f80$7a07be80$@robertwolfe.org>
Content-Type: multipart/mixed; boundary="------------070508010403060407010907"
Yes, HTML-WHO.WCX is built in. So if you have a standalone
HTML-WHO.WCX, you might want to delete it unless you have something
customized.
Ok, checking this out, it appears to be an issue related to Virtual
Domain Groups (VDG) and the access profiles. I was able to repeat the
problem and to make a long story short, you have to make sure the
domain the user used in the URL is in the VDG listing and not rely on
the default host name which may not be the same.
For example, on my home machine, I have "home.winserver.com" domain,
but in my VDG setup I havethe computer name "HDEV21" setup as the
default domain. I don't have "Home.winserver.com" in the table/.
What that means is this, when the user uses the domain
home.winserver.com in the URL for the browser, WcWEB will lookup
home.winserver.com in your VDG table to get the access data. If the
domain is not listed, it will use the one marked as the default. For
me, that was HDEV21 and the access profiles was set to allow "New
User" so it should of worked. But the template was skipping the node
display because it was using the new "WHO.VDG" template variables that
regulates how the virtual domains are displayed in Who's Online.
In the WHOS_ONLINE.HTM, template, it has these options:
@set Who.VDG = 1@ @//@ set 1 to enable vdg support
@set Who.VDG.Column = 0@ @//@ set 1 to show column
@set Who.VDG.Filter = 1@ @//@ set 0 - show all, 1 - current, 2
- user, 3 - accessible
This is complex and I have to remember my design details, but the idea
was to give you control over what the user the can see. Overall, for
the "normal" user, you don't want home to see who's online for other
domains. So the ideas were:
0 Show all user nodes, master sysop, administrator, etc.
1 Show nodes only with the same current domain of the user
2 Show only the user node (private idea)
3 Show the domains the user has access too.
Again, I'm on complexity design recall, but doing some debugging, with
the Who.VDG.Filter=1, the user's current domain was blank so it didn't
show the nodes. I have to see why it was blank but it appears it is
because, I didn't have a "home.winserver.com" VDG domain.
To prove that this was the problem, I removed the home.winserver.com
from VDG and then use the url http://hdev21 and it worked.
So its related to the VDG and somehow the default is not set in the
connection node records.
Your solution for now is:
1) Make sure the URL domain is also in the VDG table, make sure the
access profiles are set.
and/or you can play with the template:
2) Put a copy of WHOS_ONLINE.HTM into the http\template\custom folder,
and edit it. Play with the WHO.VDG option, set it to 0.
@SET WHO.VDG = 0@
and see what happens. It will be interesting if you have many virtual
domains to see how it will display.
Keep in mind that this appears to be minor bug with the default domain
not being set in the TConnectionInfo record for the node. Penciled in
for review, but you have a solution by setting the URL domain in the VDG.
On 11/24/2018 8:06 PM, robert.wolfe@robertwolfe.org wrote:
> Actually, I believe the web interface calls html-who.wcx which I
> believe in built into the WILDCAT.WCL archive. Hector, please
> correct me if I am wrong and set the record straight.
>
> *From:* listadmin-winserver@winserver.com
> *On Behalf Of *Terry Roati
> *Sent:* Saturday, November 24, 2018 6:42 PM
> *To:* WINServer@winserver.com
> *Subject:* RE: [WINServer] HTML Who is Online
>
> I am using http (built in web interfaces of WINS) and have checked the
> access levels for WCX and Clients which are all ok. It is only
> Whos Online with a issue, Files, Messages, Chat and
Properties
> etc are ok.
>
> I checked and I am not using any WCX for Whos Online HTML.
>
> *From:* listadmin-winserver@winserver.com
>
> > *On Behalf Of
> *robert.wolfe@robertwolfe.org
> *Sent:* Sunday, November 25, 2018 6:09 AM
> *To:* WINServer@winserver.com
> *Subject:* RE: [WINServer] HTML Who is Online
>
> Technically, for the web interface, I believe you ARE using a WCX for
> the web clients (files, messages, who is online, etc). But, I may be
> wrong.
>
> *From:* listadmin-winserver@winserver.com
>
> > *On Behalf Of *Terry Roati
> *Sent:* Saturday, November 24, 2018 2:14 AM
> *To:* WINServer@winserver.com
> *Subject:* [WINServer] HTML Who is Online
>
> Hello Hector,
>
> I am not using any WCX.
>
> When I log in as Sysop it is ok.
>
> When I log in as a Regular user, it
doesnt show a user.
>
> Just to let you know that when I tried to compile html-who.wcc it has
> errors.
>
>
--
Hector, Engineering & Technical Support
Santronics Software, Inc.
http://www.santronics.com (sales)
http://www.winserver.com (support)
http://www.winserver.com/AupInfo (Online AUP Help)
Office: 305-248-3204
begin:vcard
fn:Hector Santos
n:Santos;Hector
email;internet:winserver.support@winserver.com
tel;work:305-248-3204
version:2.1
end:vcard
--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
SEEN-BY: 1/123 15/0 90/1 105/7 10 11 44 81 85 500 106/201 120/340
SEEN-BY: 123/131 129/305 153/7715 218/700 226/30 227/114 229/110 111
SEEN-BY: 229/112 113 114 206 307 317 424 426 428 470 550 664 700 266/512
SEEN-BY: 282/1038 317/3 320/219 322/757 342/200 396/45 460/58 633/280
SEEN-BY: 712/848
PATH: 105/81 229/426
|
