Emaze WebThread 1.0: Instruction Manual & FAQ

This FAQ is for both the commercial and freeware versions of WebThread 1.0 . If you ever have any comments, questions, or suggestions for new features, please let us know. Simply jump to our customer service / feedback forums from our home page at http://www.emaze.com or email us at support@emaze.com .

If you wish to change any of the files on your webserver, please edit a copy of them. This will prevent you from overwriting what may be the only correct version you have of that file.

How do I ... / What is ... ? (FAQ with required authorization in parentheses)
0. Additional conferences
0.1  Run multiple conferences *
0.2  Run multiple conferences using a separate user database
       (requires additional licenses)

1. Customization of each conference, usage information
1.1  Edit variables in WebThread configuration file **
1.2  Login page: login.html
1.3  Introductory message at top of main screen: intro.html
1.4  Add new users page: add.html
1.5  Help screens
1.6  View error log
1.7  View login records (trackUse) *

2. Using WebThread (required auth)
2.1  Create a new user login (add a new username) (adduser)
2.2  Modify your user information (user)
2.3  Read a thread (read)
2.4  "Index only", "messages only", or "index and messages" (read)
2.5  Thread info (read) *
2.6  Post a message (post)
2.7  Post to a new thread (new)
2.8  Post as html instead of plain text (post) *
2.9  Main screen, logout, new login and help buttons (read)
2.10 Unpost a message (unpost)
2.11 Links to move within a thread: first new in index, first new
       message, first message, last message, switch threads; and no 
       unread messages (read)

3. New users (required auth)
3.1  Auth definitions
3.2  Set the default auths for new users (superuser)
3.3  Add a new user to the user database (adduser)
3.4  Require guests to add themselves to the user database before
       reading or posting (adduser)

4. Information and Auths of Existing Users -- requires superuser auth
4.1  Modify information of a user: username,password,auths,name,email
4.2  Delete users from the user database
4.3  View and modify the auths of multiple users *
4.4  Give or deny auths to all users regardless of their individual
       settings (masking) *

5. Manage threads -- requires admin auth
5.1  Create new threads
5.2  Designate threads as active or inactive
5.3  Delete threads
5.4  Delete posts
5.5  Ticket registry (superusers also have access to this function)

* This feature is not available in the freeware version of WebThread.
** The freeware version does not include the following options: add a company logo or other icon to threads, use graphic files in place of buttons, post messages as html, and track login records.


0. ADDITIONAL CONFERENCES

0.1 -- Run multiple conferences: WebThread allows you to create additional conferences which are separate from the initial conference you created during installation. There are several reasons for creating multiple conferences:

* Please note that the ability to create multiple conferences is not enabled in the freeware version.

1. On your web server, create another directory within the projectDIR directory. This new directory can be called msgtree2 or anything else you want, e.g. the name of the product it will be used for or the group using it.

2. Copy the login.html, intro.html, and add.html files from a pre-existing conference directory (e.g., msgtree1) to the directory you just created. You may want to edit or change them later to customize them for this particular conference (faq 1.2 - 1.4).

3. Make a copy of the WebThread configuration file (or whatever you renamed it) associated with a pre-existing conference, which is in the cgi-bin directory. (You can also use the original distribution version, but it will require you to set all of the variables which are already correct in your existing conferences). You can call the new file whatever you want, but remember the name will be part of the URL. For the purposes of the instructions, we will refer to this new file as "WT2". Now open WT2 in any text editor or word processor.

4. In WT2:
Line 19: Change the init variable from 0 to 1 so that WebThread initializes the new conference.
Line 33: Edit the msgtree variable to point to the new directory you just created in step #1.
Line 64: Change the lnf_name variable to the name of the new conference.

You are welcome to change any of the other variables (see faq 1.1) as well, with the exception of the perl path and projectDIR directory since the new conference must be in the same main directory.

5. FTP WT2 to the cgi-bin directory as an ASCII text file, not as binary.

6. Access the conference using your web browser at the same URL of the original conference, except using "WT2" instead of "WebThread". WebThread will initialize the new conference, however it will not create a new user (master) as it did the first time. Rather, it gives the 'master' user full auths for the new conference.

7. FTP WT2 from your web server back to your computer, open it, and change the init variable from 1 (one) to 0 (zero). Now ftp it back to the web-server's cgi directory, overwriting the original version of WT2. As usual, the file must be ftp'd as ASCII text files, not as binary files.

8. The new WebThread conference is now ready to run. Access it using the correct URL and log in using the original 'master' username and password. If you did not change the password for master after the initial installation and therefore do not know it (or otherwise simply forgot it), just do the following:
  1. Login to an older conference using any username that has superuser privileges
  2. Click on the "edit other users info" button
  3. Choose to edit 'master'
  4. Change the password for master by entering a new password, re-entering it to verify, entering your password (for the superuser you logged in as) at the bottom, and click update
  5. Logout from the older conference
  6. Login to the new conference using the master username and password.
  7. Send email to we-told-you-so@emaze.com (this step is optional)

After logging in as master, you will have full authorization just as in the original conference. All of the users in the user database of the original conference(s) will also be eligible to access this conference. However, because you can vary user auths by conference, no users are automatically given any auths for the new conference (other than master). So if any or all users should have access to this conference, you can edit their auths (see FAQ 5.3).

One easy way to avoid changing individual auths for a second conference is to use the masking feature to give all users the same auths you gave them in the original conference (see FAQ 5.6). This is especially useful if all users in conference 1 will have access to conference 2. Just be sure that new users add themselves to the original conference first, rather than the new conference. This is because if you simply "give" all users the same auths you gave them in conference 1, it is not possible to create a user in conference 2 which is only allowed to add a new user. They also will not have access to the first conference unless you use the masking option there too.

Important -- No matter how many conferences you create, the entire WebThread system maintains only one user database. Therefore, every user is automatically eligible to access every conference (subject to the masking settings in each one). There is no need for a user to add herself to the user database in every conference. And if a user changes any information, including the password, then it is changed for all conferences. However, no users other than master are ever automatically given any auths for new conferences.

Top of the FAQ

0.2 -- Run multiple conferences using a separate user database: To run additional conferences, but with a completely separate user database, you must install WebThread a second time, using the same installation instructions. You will need to install WebThread in a completely separate directory, i.e., create a second distinct projectDIR.

The second installation of WebThread will run completely separate from the first. As with the first installation, you can run multiple conferences with the same user database. There really is no reason to run a conference using a separate user database unless you have so many users that you are running out of usernames. However, this is unlikely to happen.

Please note that the copyright agreement does not allow you to install WebThread a second time, even if on the same webserver, without purchasing an additional license from Emaze. Each additional license costs $25 and the additional licensed copy of WebThread can be installed only on your site's servers. If you wish to install additional copies of WebThread on servers for other companies, you must pay the $39 price for each copy. More information is available by emailing Emaze at license@emaze.com .

Top of the FAQ
1. CUSTOMIZATION OF EACH CONFERENCE, USAGE INFORMATION

1.1 -- Edit variables in WebThread configuration file: To change any of the variables listed below, just ftp the WebThread file (or whatever you renamed it) in the cgi-bin directory to your computer, and edit a copy of it in any text editor or word processor. The links refer back to the Installation Instructions in INSTALL.htm to give you an explanation of each option.

* This feature is not enabled in the freeware version of Webthread.
** The freeware version does not allow you to use graphics instead of the buttons, although you can change the text of the buttons.

Top of the FAQ

1.2 -- Login page (login.html): The login.html file is the top of the login page, which is the first page users see and where they login to WebThread. It is located in the msgtree1 directory (or whatever your renamed it) and there is a separate copy in each conference directory.

To edit this page, ftp the login.html file to your computer and open it in any text editor, word processor, or html authoring program. You cannot change the filename and it must be in html format. You only have to include the information between the <body> tags since the <body> tags themselves will automatically be added when the page is created. You may want to limit how much you put in this file since the username and password fields and the login button will appear below this information.

When you are done editing the file, just ftp it back to the proper directory for that conference to overwrite the old version. As usual, please ftp the file as ASCII text, not binary.

Top of the FAQ

1.3 -- Introduction message at top of main screen (intro.html): The intro.html file is the top of the main screen page. This is the first page users see after logging into WebThread, and is also the screen where the "Add a new user" and "Edit your own info" buttons are located. The main screen also contains buttons for admin and superuser functions. The file is located in the msgtree1 directory (or whatever your renamed it) and there is a separate copy in each conference directory.

To edit this page, ftp intro.html to your computer and open it in any text editor, word processor, or html authoring program. You cannot change the filename and it must be in html format. You only have to include the information between the <body> tags since the <body> tags themselves will automatically be added when the page is created.

You may want to limit how much you put in this file since the actual system options, such as "Read a Thread," will appear below this information. However, you should at least include a message informing users that they should not use the Back, Forward, or Reload buttons on their browser. Rather they should use the buttons WebThread provides to navigate through the system, otherwise they may cause an error and will have to login again.

When you are done editing the file, just ftp it back to the proper directory for that conference to overwrite the old version. As usual, please ftp the file as ASCII text, not binary.

Top of the FAQ

1.4 -- Add new users page (add.html): The add.html file is the top portion of the "Add a new user" screen. To edit this page, ftp add.html to your computer and open it in any text editor, word processor, or html authoring program. You cannot change the filename and it must be in html format. You only have to include the information between the <body> tags since the <body> tags themselves will automatically be added when the page is created.

You may want to limit how much you put in this file since the actual form will appear below this information. It currently contains information about how to properly complete the new-users form. You should include a note that this is the one place where they may need to use the should the Back button on their browser if there is a problem with their entry. When you are done editing the file, just ftp it back to the proper directory for that conference to overwrite the old version. As usual, please ftp the file as ASCII text, not binary.

Top of the FAQ

1.5 -- Help screens: At the top and bottom of each thread, and the bottom of all other screens, there are 4 buttons: main screen, logout, new login, and help (in that order). The 'help' button transfers you to the help screen, however which help screen it is depends on whether you have admin and/or superuser authorization. If you do have admin and/or superuser authorization, you will see the file faq-admin.html; if not, you will see faq-user.html . Both help files include part 2 of this faq, but the admin file includes parts 3-5 as well (everything you can do from within WebThread).

You are welcome to edit these pages if you want. This will allow you to include even more useful information, or even delete entries in faq-user.html for the authorizations which you do not give to users, such as modifying their own user information, posting to new threads, unposting their own posts, and posting as html.

Both files (faq-user.html, faq-admin.html) are located in the doc directory within the main directory in which you installed WebThread. Unless you changed the directory name during installation, this is the WT-dist directory. To edit the files, just ftp them to your computer and open them in any text editor or word processor.

Just as with the add, login and intro files, both faq files are partial html documents containing all information within the <body> tags. You do not need to include the <body> tags. And as always, be sure to ftp the files back to your webserver as ASCII text. You way want to have a backup copy of the files just in case. Note that the help files are global to all conferences and there is no way to restrict your access to the faq-user help screen other than to delete it.

Top of the FAQ

1.6 -- View error log: The error log gives you a list of system errors that your users received. This is useful in case something was changed after the initial installation on your webserver since you can notice that many users have been receiving a certain error before you get dozens of calls complaining about it. To view the error log, ftp the WT-error-log file in the main WebThread directory to your computer and open it in any text editor. Please note that to view the error log, you must have chosen the 3rd errorLog option during installation.

This file does not contain all errors though, only system errors which are relevant to ensuring that WebThread is running correctly. It does not contain user errors caused when users do something wrong, such as using the Back, Forward, or Reload buttons on the browser and then having to login again. Below is an example of sample entries, with their meanings:
7/ 8/96 15:53:05 (pid 18971, uid ): WebThread "howdy" warning: possible crack attempt from 198.115.98.20: incorrect password entered for login by master

Meaning: Someone tried (and failed) to guess master's password.
7/ 8/96 15:56:59 (pid 19011, uid 3): WebThread "howdy" error: fatal: could not create ticket /www/data/httpd/cgi-user/dmacks/WT-test/msgtree1/tickets/3-839534219-6LiciLliYw2uw: No such file or directory

Meaning: File system is full or some pathname in the WebThread configuration file does not match the actual file locations. (This is a problem if it continuously occurs, but it will not happen only every once in a while.)
7/ 8/96 15:43:55 (pid 18872, uid 3): WebThread "howdy" user: login: su

Meaning: User with username 'su' logged in. This message will only appear in this file if you chose $trackUse=1 (record according to errorLog). Because systems other than WebThread might use this file and all conferences share this file, "WebThread" and the conference name ("howdy") are specified.

Top of the FAQ

1.7 -- View login records (trackUse): The login records keep track of when all users login to a particular WebThread conference. The records are stored in the user-log file in the directory of that conference. To view the records, simply ftp or copy the user-log file to your computer and open it in any text editor to see the records.

Note that to use this feature, you must have chosen 'trackuse = 2' during the initial installation. If you chose 'trackuse = 1', the records will be stored in the same WT-error-log file used to log system errors, or sent to STDERR with the error records. Below is a sample of the records, and what it means:
7/ 8/96 15:11:30 (pid 19030, uid 8): login: ernie

Meaning: User with username 'ernie' logged in ($trackUse=2). It does not specify which conference because WebThread saves this information in a separate file for each conference.
7/ 8/96 15:43:55 (pid 18872, uid 3): WebThread "howdy" user: login: ernie

Meaning: User with username 'ernie' logged in to the conference named "howdy." The conference name will appear if you chose for the login records to be recorded according to errorLog, meaning that there are not separate login records for each conference.

Top of the FAQ
2. USING WEBTHREAD

2.1 -- Create a new user login (add a new username) (adduser): Log in using the given name and password. At the bottom of the main screen (the first page you see) under the heading 'Other functions', click on the 'Add a new user' button. There are 5 forms on this page: username, password, re-enter password to verify, real name, and email address.

You can choose your username and password. While you can change your password later, you cannot change your username, so be sure to choose something you will remember. Usernames and passwords can be anything, including numbers, except the following characters (: ; > < & "). Both are case-sensitive, meaning that if you use capital letters, they are different from lower-case letters, so you must remember this when logging in. Please note that each user must have a unique username, but more than one user can have the same password, name and email address.

Choose your username and password, then re-enter your password to verify that you entered it correctly. Below the username and password fields, you will also see a list of auths, which are usage privileges. Here are auths you might be granted and what each allows you to do:

   access   login
   read     read threads
   post     post a message to an existing thread
   new      begin a new thread (i.e., post message to new thread)
   unpost   unpost your own messages
   user     modify your own user information: name, email, password

Below the auths are the real name and email fields on the form. Enter your name and full email address. The system assumes your name is entered in 'first last' order. Again, please do not use any colons. After completing the form, click on the 'add' button at the bottom. A new user is created with the default settings for auths and you are sent to a confirmation page which tells you whether your entry has been accepted. If you get an error message, the message will tell you what is wrong.

There are a few reasons you might get an error, such as the username is already being used or your password and re-entered password were not the same. If you get an error, just click on the 'Back' button on your browser to back up to the form, and fix the incorrect field. If the username is already being used, just choose a new one. If your password and re-entered password were not the same, just re-enter both of them. Then click on the 'add' button again.

If your entry was accepted, the message will say that a new user with your username has been added to the user database with the default authorization settings. Now just click on the 'new login' button at the bottom-middle of the page to login as your newly-added self. This will send you back to the login screen to enter your username and password.

Top of the FAQ

2.2 -- Modify your user information (user): From the main screen, click on the 'Modify your user information' button. You will see a screen similar to the screen you initially used to sign up for your own username. Then change the information you want, including password, name and email address. Please note that if you change your password, you must re-enter it to verify that you have entered it correctly. Also, you cannot change your username (although a superuser can).

When you are done updating the information, just enter your password at the bottom and click on the 'update' button. If you changed your password, you must still enter your old password at the bottom. The screen will reload with the updated information, and you can then click on the 'main screen' or 'logout' buttons.

Top of the FAQ

2.3 -- Read a thread (read): After logging in, the first option will be 'Read a thread.' Choose the thread you want to read, whether you want to view index and/or messages, and then click on the 'read' button. The threads are listed in order of creation, with the newest threads at the top. Please note that messages are listed in order from oldest to newest, putting the newest messages at the bottom of the thread.

To switch to a different thread while reading an existing thread, simply scroll to the bottom of the thread and choose the thread you want to read. At the top of each thread, there is also a link, 'Switch threads,' which links to the bottom of the thread where you can choose to read another thread, or even reload that thread.

Top of the FAQ

2.4 -- "Index only", "messages only", or "index and messages" (read): The index is a table with information about each post in that thread. It contains the user's real name, the summary, and the date of the post. To the left of each entry in the index is a number which links to that particular message below in the thread.

index only only the index of that thread and not the actual messages
messages only only the messages and not the index
index and messages both, with number of each index entry linking to actual message below

Please note that it is not possible to add the messages to the page if it has already been created with 'index only.' Likewise, you cannot simply add the index if 'messages only' was chosen. You must re-load the thread by going to the bottom of the thread, choosing to read that particular thread again, choosing 'index and messages,' and then clicking on the 'read' button.

Top of the FAQ

2.5 -- Thread info (read): Thread info is a separate page with a table of all threads in that conference, the date of the first and last posts in each thread, and the total number of posts in each thread. It is useful as a quick way to see if any new messages have been posted to any threads since your last login, or if any new threads were created.

Top of the FAQ

2.6 -- Post a message (post): To post a message to the thread you are reading, simply click on the 'summary' field to enter the summary of your message, then click on the large text area below to type your message. Click on the 'post' button below the text area to submit your message. The page will then be reloaded with your new post.

There may also be an option to post to a new thread, but do not choose this option unless you wish to create a new thread. To post to that particular thread, be sure that the radio button next to 'Continue in the current thread' is selected. And it is not possible to post a message to an existing thread unless you are reading it. Also, when you are at the main screen and therefore not reading a thread, you will only be able to post a message to a new thread.

Top of the FAQ

2.7 -- Post to a new thread (new): From the main screen or from an existing thread, at the Post form, click on the radio button next to 'Begin a new thread named.' (When reading a thread, it will be below 'Continue in the current thread.') Enter the name of the thread you want to create in the field to the right. Then just enter your summary and message, and click on the 'post' button as you normally would.

Please note that clicking in the box to type the new thread name does not automatically switch the radio button. You must switch the button manually, otherwise your message will be posted to the thread you are reading rather than to the new one you wanted to create.

If you create a new thread from an existing thread, the new thread will contain a note that it was "continued from" another thread as well as a button to jump back to that thread. And your post on the original thread will contain a note saying it was continued to a new thread, with a button link to the new thread. So if you want to create a new thread without having the 'continued from ... ' message, simply create the new thread from the main screen. At the main screen, you are not reading a thread, so the new thread is not continued from an older one.

Top of the FAQ

2.8 -- Post as html instead of plain text (post): It is possible to post your message in html format. This allows you to include a hypertext link or picture, or simply spruce up your message with bold, larger fonts, or other editing. To do this, click on the list box which says 'text' at the right of the summary line (above the message box) and choose 'html.' While the system will ensure that all tags are closed, only users who are familiar with html should choose this option.

Top of the FAQ

2.9 -- Main screen, logout, new login and help buttons (read): At the top and bottom of each thread, and the bottom of all other screens, there are 4 buttons: main screen, logout, new login, and help (in that order).

Main screen: The main screen is the first page users see after logging into the system. For users, it allows you to read an existing thread, view the summary of all threads (thread info), begin a new thread, and edit your own user information. You need to return to the main screen for two reasons: 1) to edit your own information; and 2) to create a new thread which is not "continued from" an existing thread. For users with admin or superuser authorization, the main screen also contains additional buttons necessary to maintain the system.

Top of the FAQ

Logout: To log out, click on the 'logout' button. Logging out is important to ensure that another user (or hacker) cannot pretend to be you if you are not the only person who uses your computer. If you are unable to log out because your computer crashed, you were disconnected, or you just plain forgot, simply log back in real quick and then log out again.

Top of the FAQ


New login: The 'new login' button automatically logs you out and returns you to the login screen. It is useful if:
1. you just created your own username and want to login as your newly-added self
2. you have multiple usernames (which you shouldn't)
3. you are a superuser and want to make sure a user's password is correct
4. your computer is used by multiple users
Top of the FAQ

Help: The 'help' button works differently, depending on whether you have admin and/or superuser authorization or not. If you are a normal user, the 'help' button jumps to a page which contains all of the information you need to know for using WebThread. For those users with admin and/or superuser auths, the 'help' buttons links to a page which contains the instructions on how to use every feature available within WebThread.

Top of the FAQ

2.10 -- Unpost a message (unpost): To unpost one of your own messages, simply click on the 'unpost' button which is at the top-middle of all of your messages. When your message is unposted, your summary and message will be replaced with the following: 'message unposted by user at' some date and time.

Top of the FAQ

2.11 -- Links to move within a thread (read): At the top of each thread are up to 5 links:

first new in index link to index entry of first message posted to that thread since you last read it
first new message link to first message posted to that thread since you last read it
first message link to first message of thread
last message link to last message of thread
switch threads link to 'read a thread' option at bottom of thread

If there are no new messages, the 'first new in index' and 'first new message' links will be replaced with 'no unread messages.' When viewing index only, there will be no 'first new message', 'first message,' or 'last message' links. When viewing messages only, there will be no 'first new in index' or 'first message' links.

Top of the FAQ
3. NEW USERS


3.1 -- Auth definitions:
access -- login
read -- read threads
post -- post a message to an existing thread
new -- begin a new thread (i.e., post message to new thread)
unpost -- unpost your own messages
user -- modify your own user information (real name, password, and email)
admin -- declare threads active or inactive, delete threads, unpost messages, ticket registry
superuser -- modify all users' info and auths, default auths for new users, masking, ticket registry
adduser -- add new users to database with default auths

Top of the FAQ

3.2 -- Set the default auths for new users (superuser): From the main screen, click on the 'Modify global (conference-wide) authorizations' button. You will see a table with the various auths in the top row, 3 masking rows with a radio button in each square, and a 'new user default' row at the bottom with a check box in each square. The default auth settings are the usage permissions new users are given when added to the user database. Changing the default settings does not change the auths of users already in the user database.

To grant all new users an auth, just click on the 'default' box in that column so that there is a check in the box. After determining the default auths, click on the 'change' button at the bottom of the table. Be sure that 'access' is checked, otherwise the user will not be able to access the system. Typical default auths include: access, read, post, new, unpost, and user.

Top of the FAQ

3.3 -- Add a new user to the user database (adduser): From the main screen, click on the 'Add a new user' button. Fill out the necessary information on the form: username, password, re-enter password to verify, real name, and email address. Please note that each user must have a unique username, but more than one user can have the same password, name and email address. Then click on the 'add' button at the bottom. A new user is created with the default settings for auths.

If you are a superuser, you can edit the auths before clicking on the 'add' button, or immediately afterwards by clicking on the 'Edit this user's entry' button from the confirmation page. You can choose to add another user from the confirmation page as well.

Top of the FAQ

3.4 -- Require guests to add themselves to the user database before reading or posting (adduser, superuser): Create a user with username 'guest,' 'newuser,' or some other generic name, and a simple password (probably the same as the username). Grant this user the following auths only: access and adduser. This will allow the user only to login and add a new user.

Be sure to put a note asking the new user to click on the 'Add a new user' button after logging in, and then on the 'new login' button at the bottom right after adding herself to the user database so that she can log in as herself. And do not forget to put the username and password on the login screen so they know what they are.

Please note that if you use the 'masking' option to give all users a certain auth regardless of their individual settings, it will not be possible to create such a user which has only access and adduser authorization.

Top of the FAQ
4. INFORMATION AND AUTHS OF EXISTING USERS

4.1 -- Modify information of a user (username, password, auths, name, email): From the main screen, click on the 'Modify other users' information' button. At the bottom of the page is a list of all users in 3 list boxes: username, name, and email. They are each in alphabetical order, so the first name is not necessarily associated with the first username. There is also a text field for uid at the top left, next to the username list.

Choose the user you want by highlighting her information in any of the lists. Choose the user whose information you want to edit by either typing their uid in the uid field (if you know it) or highlighting the user's username, real name, or email address. If you chose the wrong user accidently, or chose more than one user in any of the categories, just click on the 'reset' button below to clear all of the highlights. After highlighting the user, click on the 'edit' button.

Username: To change the username, just click on the username box and enter the new username. Be sure that the username is unique (i.e., it is not being used by another user). If you try to choose a new username which is already being used, you will get an error. If this happens, hit the 'Back' button on your browser to go back to the form, and try a different username. Note that only a superuser can change a username -- not even that user has permission to do so when given the 'user' auth.

Password: It is not possible to look up a users' password because they are encypted. However, you can simply change the password to something new. Just enter the new password and re-enter it to verify that you entered it correctly. Oh, and don't forget to let the user know what the new password is.

Auths: To change the auths, just click on the various auths you want that user to have -- a check in the box indicates that the user has that auth. To revoke an auth, click on the box and the check will disappear.

Name or email: To change the name or email address, just click on the appropriate box and enter the new information.

When finished editing that user's information, enter your password (as a superuser) and click on the 'update' button. The page will be reloaded with the updated information. You can then click on the 'superuser' button to return to the 'Modify other users' information' screen, or one of the buttons at the bottom. If you do not want to change any information, simply do not click on 'update.'

Top of the FAQ

4.2 -- Delete users from the user database: You cannot actually delete a user from the user database, however you can simply deny them access to the system. To do this, first follow the directions in faq 4.1 (or 4.3) to choose the user(s), then click on the check box for the 'access' auth and the check will disappear. Technically, you do not have to revoke the other auths, such as post, unpost, new or user, but we recommend that you do anyway. Then just enter your password (as a superuser) and click on the 'update' button.

Please note that if you are using the masking feature and have checked the 'access' auth, it will not be possible to deny access to a user. We therefore recommend that you do not "give" the access auth when using masking. Rather, set the 'access' auth to "user," meaning that the user has access to the system only if their individual auth setting allows it.

Top of the FAQ

4.3 -- View and modify the auths of multiple users: Highlight the users whose auths you want to view or change. You can click on the user's information in any of the 3 lists, and clicking on the information of the same user in more than one list is not a problem. If you accidently highlist a user, just click on the 'clear' button to deselect everything across all 3 lists.

After highlighting the information of each user whose auths you want to view or edit, click on the 'change' button. You will get a table of all users you chose by username, with all auths. Just click on and off the auths for each user as you prefer. After you have made all necessary changes, click on the 'update' button and the page will be reloaded with the proper changes. You can then click on the 'superuser' button to return to the 'Modify other users' information' screen, or one of the buttons at the bottom. If you do not want to change any information, simply do not click on 'update.'

Top of the FAQ

4.4 -- Give or deny auths to all users regardless of their individual settings (masking): The masking feature allows you to temporarily override the authorization settings of users by either universally giving or denying access to a particular auth, regardless of whether the individual would typically have that authorization. The masking setting can vary independently for each of the auths. There are 3 masking settings:

give -- grant this auth to all users
deny -- do not grant this auth to any user, including the admin and superusers (except master)
user -- use individual auth settings for each user rather than universal setting (initial setting)

From the main screen, click on the 'Modify global (conference-wide) authorizations' button. You will see a table with the various authorizations in the top row, 3 masking rows with a radio button in each square, and a 'new user default' row at the bottom with a check box in each square. To universally "give" or "deny" a certain authorization to all users, just click on the radio button in the appropriate column for that particular authorization. Then click on the 'change' button and the page will be reloaded with the new settings.

Note that this will not affect the default authorization settings for new users, although they too will be given or denied access as well. This is because using the masking feature does not actually change an individual's authorization setting -- it just temporarily overrides it until you change it back to "user."

Just be careful not to deny 'access' universally, otherwise even you will not be able to log in except using the 'master' username and password. (This is why you need to remember the password for master since master is always given all auths to all conferences.) On that note, you also should not "give" the 'access' auth either or you will not be able to deny access to a user who no longer should have access to that conference.

Top of the FAQ
5. MANAGE THREADS

5.1 -- Create new threads: The only way to create a new thread is to post to it. You cannot simply create a blank thread, so just use the first post to explain the purpose of that particular thread. To create a new thread, it is best to do so from the main screen. Otherwise, the thread will have a "continued from" message at the top with a button link to the original thread, and a "continued to" message on the original thread with a button link to the new thread.

Top of the FAQ

5.2 -- Designate threads as active or inactive: From the main screen, click on the 'Manage threads' button. At the top of the page are two list boxes, one labeled 'currently active' and the other labeled 'currently inactive.' Active means that users can read and post to that thread; inactive means that they cannot.

It is likely that the inactive column will not be there at first. This is because the column does not appear if there are no inactive threads. Once a thread is made inactive, the column will magically appear.

To make an active thread inactive, simply highlight the thread by clicking on it, then click on the 'do it' button below the two list boxes in the middle of the page. WebThread will reload the page and you will notice that the thread is now in the inactive list box. To make an inactive thread active, highlight the thread, and then click on the same 'do it' button. The thread will then appear in the active list box rather than inactive.

The system will let you highlight more than one thread in both the active and inactive boxes at the same time. When you click on the 'do it' button, all highlighted threads in the active box become inactive, and all highlighted threads in the inactive box become active.

Top of the FAQ

5.3 -- Delete threads: To delete a thread, it must first be made inactive. Inactive threads are also listed in the 'delete threads' list box, which is at the center of the page directly below the active and inactive columns. (Just as with the inactive column, the delete threads column does not appear unless there are any inactive threads.)

To delete a thread, highlight the thread and the click on the 'delete' button below the delete column. There is no need to actually delete the thread unless you are running out of space on your webserver unless of course you really, really want to. Note that there is no undelete feature though.

Top of the FAQ

5.4 -- Delete posts: Individual posts are deleted directly from the thread. So just go to a particular thread, find the post you want to delete, and click on the 'unpost' button which is at the top-middle of each post. Be sure to click on the appropriate 'unpost' button, or you may accidentally delete the wrong post. After deleting the post, a message will appear stating that the particular message has been unposted, who unposted it, and at what time. Note that their is no re-post button.

Top of the FAQ

5.5 -- Ticket registry: The ticket registry shows a list of all tickets that have not expired. For security purposes, a user is given a ticket for each page rather than for the entire session. The ticket expires after the user either logs out or moves on to another page (at which time they get another ticket). Tickets are used to prevent the repeatedly sending your password across possibly-insecure networks.

A ticket will not be properly deleted if the user does not log out for some reason, or if they get an error message which requires them to log back in. When this happens, you must manually delete that ticket. While this is not a major security issue and having non-expired tickets does not affect WebThread's performance, it isn't exactly good either. So we recommend that every once in a while, be it once a day or once a week, depending on how many users you have, just go into the ticket registry and delete the old tickets.

To do this, click on the 'View the ticket registry' button on the main screen. You will see a table with the following information: uid, ticket id, age of ticket, and status of ticket. The age and status of the ticket are what is important. A ticket's age is the time since the user did something. So if the user logs in and leave herself on the main screen for two hours, the ticket will be two hours old. However, if she logged in 2 hours ago, but has spent that time reading and posting messages, the ticket will be only a few minutes old. There are 4 status options:

thisyour own ticket for this page; tells you it is not one you left sitting around
NONEnothing in status box; ticket is either being used by a user at that time, or was not properly deleted because user did not log out; can typically tell by age of ticket
invalidticket with a non-existent uid; should never appear since it indicates a pretty complex hacking attempt (but one that won't succeed) or a programming bug
deletedtickets deleted after clicking on 'Update registry list' button, formerly NONE

There are two buttons below the table:
'Update registry list' -- After destroying old tickets, you can update the registry list to see an updated list of the tickets. All tickets which were just deleted will now have 'deleted' in the status box. Next time you go to the ticket registry screen though, these tickets will not appear. This button simply lets you confirm that the tickets have been deleted, and to see an updated list of tickets which are still valid.

'Destroy tickets older than _ hours' -- Fill in the blank with a number (e.g., 2) and click on the button. This will delete all tickets more than 2 hours old. Two hours is a pretty reasonable age for a ticket to be deleted since it is not likely that someone is still using the system. While one hour is typically safe as well, you might log out a user who just has not bothered to log out yet.

After you have deleted old tickets, just click on one of the buttons at the bottom to return to the main screen or logout. Please note that a superuser can also access this function.

Top of the FAQ
Copyright © 1996, Emaze Software Corporation