Full-Page Posting System Intro. Page
(basics, red regarding links, reply redirection, and generic posting options including escaping, & "forbidden words" translations).

After reading this page, you may also wish to take a look at the other two help pages:

After reading this page, I strongly recommend that you read:
JavaScript/VBS Posts and Full-Page Posts.

And after reading this page and the one that I've just listed, check out:
Using the Help Folders and other Advanced Techniques.

Please read all the sections in this page, in order ... I assure you that your time will be well spent!

Feel free to e-mail me at flagger14@hotmail.com with your comments, complaints, and suggestions regarding this documentation.

The original release of this system is available from: http://www.rs-freeware.org/fp.


1:  [Basic Info. (1 of 4):]  Understanding the topics page display

2:  [Basic Info. (2 of 4):]  WebBoard's overall folder structure: the UPLOAD, and HTML folders, inheritence, the board's subfolder, and the help subfolders.

3:  [Basic Info. (3 of 4):]  Four ways to "publish" (present) HTML and other forms of content: (a) full-page posts; (b) posts moved to the board's help folder; (c) posts moved to the main help folder; and (d) JavaScript/VBS posts that load PowerPoint presentations, zip files, pages on another web site, etc.

4:  [Basic Info. (4 of 4):]  WebBoard's images folder, and why it matters for WebBoard 6 (but not WebBoard 4)

5:  Red Regarding Links: what are they; why you'd want to use them; and how you specify them

6:  Reply redirection, why you'd want to use it, and how you specify it

7:  Red regarding links, and reply redirection, in the same post: how you specify it, and why you'd want to use it

8:  JavaScript/VBS Posts, escaping posts, "forbidden word" conversions, and other generic posting options, that stop WebBoard from "protecting" you

9:  What's next?


1:  [Basic Info. (1 of 4):]  Understanding the topics page display

For staff members (WebBoard Administrators, virtual board managers, and conference moderators) ... the topics page will have a link at the bottom that says: "Switch to user and staff views".

If you click on this link, you'll see something that looks like this:

The arrow is pointing to a message: it tells you that the message number and the conference number of each post are shown in square brackets after each post.  (Note the red square, around an example.)


There are two other important difference between the views.

If one of the links refers to a full-page post, then that post will open up as intended (perhaps in a new window) when you click on the "user view" links.

But if you click on the "staff view" links, this post will open up as a normal WebBoard message.  By using this second copy of the link, you can edit or delete the post.

Finally, you'll notice that there are "annotations" on the subject lines in the section display.  There's no reason why you need to know what they mean: they're the system's way of distinguishing between the the various types of posts.

Return to table of contents

2:  [Basic Info. (2 of 4):]  WebBoard's overall folder structure: the UPLOAD, and HTML folders, inheritence, the board's subfolder, and the help subfolders.

Whenever an attachment is uploaded, this attachment will be placed on WebBoard's Upload folder.  For example, suppose you upload a photo of yourself, called "me.jpg".  If no one else has uploaded a file by this name, this file will be placed on WebBoard's upload folder.

If you'd like to view this file from the Web, you need only right-click on the "more" link on your toolbar, and open it up in a new window (for WebBoard 4 "no frames" users, this link is found on the conferences menu).

Then overtype the word "options" with: upload/me.jpg.

Note that if someone else already has uploaded a file called "me.jpg", your copy of this file might be renamed to something like "me(1).jpg", "me(2).jpg", etc.

You can refer to any file on the upload folder within a post by coding something like this:


<img src="/upload/me.jpg">

Note that WebBoard 6 will not allow you to access files on the upload folder unless you try to access them from the very same board.

In other words, if the files were uploaded from a different board, WebBoard 6 will not load them.  I'll talk more about this point in section 4

Also: it's very important that you use double quotes around the file name, and that you don't put a space between the equals sign and the double quote ... at least if you ever intend to move the post into a "global help folder" page.  (I'll explain this shortly.)


As you may know, each board in WebBoard is configured by a series of HTML pages, or "templates".  These templates contain various replaceable "WebBoard tags", such as those which set the background color, text color, and link colors for each page.

These templates are contained in the (main) HTML folder.

Since WebBoard lets you customize each board, each board has a subfolder that's named via the board alias.  If you're a WebBoard administrator, you already know about board aliases.  And if your board's URL has a "tilde" (the ~ character, sometimes known as a "squiggle"), then the board alias appears after that character.

Why have this structure?

Suppose that your board is used exclusively by the accounting department.  Let's assume that the alias of this board is accounting.

You might want to put particular information about the accounting department (such as the New Years' party annoucement) on various pages associated with that board.

For example, every board has an "intro" page (this is known as the "Welcome" page in WebBoard 6).  That might be a good place for the New Years' Party announcement.

WebBoard works via a method known as inheritence.

When it looks for the "Welcome" page for your board, it will first look at the subfolder of the HTML folder for the Welcome page ... in other words, it will look in the accounting subfolder of the main HTML folder.

If it doesn't find the Welcome page on the accounting subfolder, it will look in the main HTML folder.


As it turns out, the "help" pages for WebBoard are stored on a special subfolder of the main HTML folder, called (suprise!) "help".

This is the main help (sub-)folder.

Interestingly enough, each board has its own help subfolder.

Help folder pages are referenced with a very special syntax.

To see this, try the following: right-click on the "more" link on your toolbar, and open it up in a new window (for WebBoard 4 "no frames" users, this link is found on the conferences menu).

Now overtype the "options" part with help?logintricks.

This is the help page that you know of as "login tricks".  Actually, this page is called logintricks.html, and it resides on the help subfolder of the main HTML folder.

It turns out that inheritence also applies to the help subfolder, and each board has its own help subfolder.

So if you had a file called logintricks.html on the help subfolder of the accounting board's folder which is on the main HTML folder, then this file would be loaded instead of the file by the same name on the help subfolder of the main HTML folder.

Let's see that in graphical terms:

What if someone tried to load this file, and they were on another board?  Unless their board had a help folder, which contained LoginTricks.html, they would see the version of LoginTricks.html that resided on the main help folder.  If they did have a version of that file on their board's help folder, then they would see that version, instead.  But under no circumstances, would they see the version of that file that resides on the accounting board's help folder!

Return to table of contents

3:  [Basic Info. (3 of 4):]  Four ways to "publish" (present) HTML and other forms of content: (a) full-page posts; (b) posts moved to the board's help folder; (c) posts moved to the main help folder; and (d) JavaScript/VBS posts that load PowerPoint presentations, zip files, pages on another web site, etc.

Now that you understand WebBoard's folder structure, I can explain how this system allows you present content:

Return to table of contents

4:  [Basic Info. (4 of 4):]  WebBoard's images folder, and why it matters for WebBoard 6 (but not WebBoard 4)

(WebBoard 4 users: the images folder plays no role in this system, so you don't have to worry about it.  WebBoard 6 users: you also don't need to care about the images folder unless you want users of other boards, or the general public, to view the content that you "publish".)

If you're running WebBoard 6, and you want people on other boards to be able to see the images on a web page, you'll have to post the HTML for this page into a WebBoard message, and then upload this page to the main help folder.  The same is true of a PowerPoint presentation, a zip file, or any other specialized application.

This is especially true if you want WebBoard to become a "web site," i.e.: you want to make your pages and files available to users who don't have to log in or register.

Under WebBoard 6, this kind of access to images and other files can only occur if these files are located on WebBoard's images folder.


WebBoard uses the images folder for its own purposes.  Normally, you aren't permitted to change the files on this folder (at least not from the Web).  However, this system does allow you to put files on this folder, as long as you're a staff member (and you should be a staff member if you're reading this help page -- i.e. a conference moderator, a virtual board manager, or a WebBoard administrator).

To see an example of an image on the main images folder, right-click on the more options link, and select the "open in new window" option.  Then overtype the word "options" with: wbimages/powered.gif.  This is the "Powered By WebBoard" GIF that you may see in various places on your board (such as the login page, if you have a board that uses "cookies").

In order to prevent accidental overwritting or deletion of WebBoard's own files, this system limits your ability to name these images: every image that you place on this folder will have your "board prefix," added to the beginning of its name, provided that the name doesn't already with the board prefix, or an underscore.  To see what your board prefix is, go to the "more options" menu, and choose the option called View the board ID#.

Return to table of contents

5:  Red Regarding Links: what are they; why you'd want to use them; and how you specify them

Let's start with an example (this example was taken from WebBoard 6 - the images next to the links may be unfamiliar to WebBoard 4 users);

In this case, message #473 is the regardED post.

It could be a post in which board members sign up for the Accounting department's New Year's party, or the annual budget proposal.

The important thing is that the other post is referenced within this post.

Note that if Message #473 is a full-page post, then there won't be two links: only the first will be present; and if users click on it, a new window will open up, with a full-featured web page.


How do you specify a "red regarding" link?

It's easy ... whenever you post a message, you get some extra options below the post.  Here's what you need to look at:

You do need to know the message number and the conference number for the regardED post.

How do you discover the message and conference numbers for the regardED post?  Take a look at section 1 for more information about that.


There are two kinds of "red regarding" links.

Inheritable red regarding links will "propagate" themselves through all replies.

In other words, all replies to the post will carry the red regarding link.

Do you want this?  Well, it depends on your application.

For example, you might not want "inheritence" if your post is done in a conference that only the board staff can access, and the only purpose of red regarding link is to alert other staffers to a renegade user's post.

However if the red regarding link points to (say) a budget proposal, you might wish all replies to reference the regardED post.

The decision is entirely yours.


Note that there's a checkbox which asks whether the regardED post is a "full-page" post.

If you check the box, then there will be only one link displayed.  When that link is clicked, the result will be the same, as if the original full-page post is accessed.  That might mean that the post will load in the messages frame, or in a new window.

Return to table of contents

6:  Reply redirection, why you'd want to use it, and how you specify it

Reply redirection means that when users reply to a post, their reply is treated as a reply to another post.

For example, suppose that customers are asked to view a post that's entitled "Advantages of/Questions about the New Release".

You already know that the new release of your software (or engine, or any other product) has pleased customers, far and wide ... but also that there are many questions about how to use your new product.

So, you'd like these posts to go into another discussion thread.

That's easy, with the reply redirection feature: you simply specify the message number and conference number of the the discussion that will take the replies.


How do you specify "reply redirection?"

You do need to know the message number and the conference number for the post that the replies are "redirected to".

How do you the message and conference numbers for that post?  Take a look at section 1 for more information about that.

Return to table of contents

7:  Red regarding links, and reply redirection, in the same post: how you specify it, and why you'd want to use it

You might want to use both of these capabilities, if the regardED post referenced something of interest to everyone (such as a new budget announcement), and you wanted users to comment, in another discussion thread.

When you do the post, you're given the chance to specify this:

How do you the message and conference numbers for the posts involved?  Take a look at section 1 for more information about that.

For more information about "red regarding" links, please view section 5.

For more information about "reply redirection", please view section 6.

Return to table of contents

8:  JavaScript/VBS Posts, escaping posts, "forbidden word" conversions, and other generic posting options, that stop WebBoard from "protecting" you

I need to emphasize the fact that WebBoard protects you against posts that might be problematic.

WebBoard protects you by disallowing certain words and/or phrases in posts.  For example, WebBoard will not allow anyone to post this sequence in a message:


<SCRIPT ...

Unfortunately, this level of protection, while laudable, may be a tad more than you desire ... since you're a conference moderator, and/or a virtual board manager, and/or a WebBoard administrator.  In my opinion, WebBoad "overprotects" you ... by preventing you from adding content to your own board, and/or enriching the experience of your users.

To be more specific, suppose that a PowerPoint presentation has been uploaded to your virtual board.  The Assistant to Vice President In Charge of Operations has uploaded the file New_Plan.ppt.

Now, you'd like everyone (including the CEO, or perhaps your customers) to be able to click on a message in the topics list, in order to load this PowerPoint presentation.

And because you've learned a lot about how WebBoard folders work (as described in section 2), you'll code the following in a post:


<SCRIPT LANGUAGE='JavaScript'>
window.open("upload/New_Plan.ppt", "newplan");
</SCRIPT>

Well, in case you were wondering ... WebBoard is here to save the day!  In particular, WebBoard won't let you post that, because WebBoard's designers assume that all such posts are designed to attack your board with spam, or other undesireable information.


I wrote this system, in part, to prevent WebBoard from "(over-) protecting" you in this way.

Let's take a closer look at the additional options that this system allows ... when you post a message:

The first option is selected by default whenever a staff member (such as yourself) posts a message.

"Forbidden word" conversions are designed to prevent WebBoard from "protecting" you against HTML tags such as <form>, <SCRIPT...>, <META ... >, and any number of other tags that you might want to use in full-page posts, or other posts that you might want to move to the board's help folder, or the main help folder.  (For more information about the folder structure of WebBoard, please see section 2).


The second checkbox lets you prevent WebBoard from automatically adding HTML to the text of a full-page post.

For example, WebBoard 4 is particularly "mindless" in this respect.  Suppose you've coded an image file reference like so:


http://mysite.com/images/me.jpg

If the "allow active images in messages" option is selected for this conference, Webboard will automatically make this image link "active", i.e. it will convert this code into:


<img src="http://mysite.com/images/me.jpg">

But that may not be what you desire, particularly if this text is within JavaScript, Visual Basic Script, or is used for some other special purpose.

A similar analysis applies to the "allow active links in messages" option for WebBoard conferences.  By selecting the first checkbox (see above), you free yourself from WebBoard's efforts to "protect" you in this manner.


The last checkbox should only be used if you're unsatisfied with the results from your post.  This system will automatically "escape" and "unescape" posts, as needed.

What's "escaping"?  Escaping refers to the translation of characters, in a way that WebBoard's likely to ignore, when attempting to "protect" your board from invalid posts.

Most characters besides digits or letters have an "escaped" equivalent: for example, a space is translated to %20.

To repeat, the system so clever about escaping and unescaping posts that I can imagine very few instances in which you'd need to "manually" control its behavior.

Return to table of contents

9:  What's next?

After reading this page, I strongly recommend that you read:
JavaScript/VBS Posts and Full-Page Posts
.

And after reading this page and the one that I've just listed, check out:
Using the Help Folders and other Advanced Techniques.

Feel free to e-mail me at flagger14@hotmail.com with your comments, complaints, and suggestions regarding this documentation.

The original release of this system is available from: http://www.rs-freeware.org/fp.

Return to table of contents