|
|
 |
Website Manager - CMS Content Management System
Requirements
Configuration
Installation
License and Disclaimer
Getting Started
Managing users
Saving Files
Zones
Changing your password
Requirements
This script requires Perl on either a UNIX or WINDOWS server. To log in and manage your web pages in WYSISWYG mode, you will need to use MicroSoft Internet Explorer on a Windows Machine. If you're using Netscape or an Apple Macintosh, you will see a regular text area. The web pages you edit or create will be viewable by all browsers. To utilize the zones feature (SSI) your server will need to support Server Side Includes.
Configuration
This Script requires no Configuration, however if you have trouble installing the Script, you can hard code some values in the _key.cgi file.
Installation - Linux/Unix/Mac Servers
[script] refers to the first portion of the name of the CGI Scripts you purchased.
- Setting the Path to Perl. Open all CGI Scripts (except [script]_key.cgi) in a Plain Text Editor and make sure the first line of the CGI Script is the Path Perl for your server. Most Users can skip this step being the default Path to Perl shipped in the CGI Script is very common.
NB: if you do not you a Plain Text editor such as Windows NotePad or Mac Textedit (in Plain Text Mode), your Text/HTML editor will add extraneous code to the CGI Script when you save it which will result in a server 500 Error.
- Upload all CGI Scripts to your cgi-bin or any cgi enabled
directory and CHMOD
all the CGI Scripts to 755. It is imperative that you upload (transfer) all CGI Scripts to your server in ASCII mode.
If you forget to CHMOD all CGI Scripts to 755, Step 3 will
yield a Server 500 Error.
If you do NOT upload (transfer) all CGI Scripts to your
server in ASCII mode, Step 3 will yield a Server 500 Error.
- Load your Browser, point it to the [script]_setup.cgi file and follow the on-screen instructions for installation. For example, in your browser, type :
http://www.yourdomainname.com/cgi-bin/[script]_setup.cgi
- Enter a Username and Password. This will be your Username and Password for the Administration Section. If the Setup Routine is successfully processed a link to the Administration Section will appear on the resulting page. Click the link to access the Administration Section with the Username and Password you just entered in the Setup Script.
Should you encounter any Permission problems with the Setup Routine follow the instructions returned by the Script.
Upon successful completion of the Setup Routine the [script]_setup.cgi_setup.cgi script attempts to delete itself. This ensures the Setup Routine can not be repeated by another Surfer who would effectively reset your Administration Section Username and Password. Manually delete the [script]_setup.cgi
CGI Script you uploaded if the Setup Routine could not automatically
delete it (Refresh your FTP directory listing to check).
Should you ever forget your Administration Section Username and Password you can repeat this Step to set a new Username and Password.
Common Installation Problems - Linux/Unix/Mac Servers
NB: Shared Secure Servers, VPS, SBOX and Free Servers.
- Server 500 Error. This most often occurs because Step 2 was not followed precisely. Make sure the CGI Scripts you are uploaded are CHMOD to 755, the folder the CGI Scripts reside in is also CHMOD to 755, and the CGI Scripts were transferred in ASCII Mode. Auto-Detect only detects the extensions you specify in your FTP client's Settings.
- I can initially load the Setup Script and punch in my Username and Password, but when I submit the Form, I receive 404 Error Page or an alternate Error Page stating "Page Cannot be found".
This suggests your Server is operated by a very nervous System Administrator employing strict security measures, you're using a Shared Secure Server which dynamically sets your domain name to something other than the a standard Top Level Domain (www.yourdomainname.com) or sbox is employed by your server.
In any case, open [script]_key.cgi in Plain Text Editor (not a WYSIWYG Text Editor, nor a Rich HTML Editor) and enter the URL to the folder you uploaded the CGI Scripts to in the $SecureServer Variable. If you uploaded the CGI Scripts to your cgi-bin, then you'd set the following:
$SecureServer = "http://www.yourdomainname.com/cgi-bin";
Do NOT enter the CGI Script name, do NOT enter a trailing slash. After setting the Variable refresh the Setup Routine's Page that asks you to enter your Username and Password. Unless you refresh the initial Setup Page, the Form's URL will not be updated to reflect your Variable value.
- I cannot find the correct path to my WebSpace or the required Data Directories and/or Password file cannot be created.
You need to find that Path. Ask your host, or Download a copy of our free E-Vars CGI Script and install it on your server. CHMOD it to 755 then load it in your Web Browser which will print your Server's environment variables and other useful information. Determine your Server's Document_ROOT or Absolute Server Path to the folder your home page (index.html) resides in. You may need to append "/www" or "/httpdocs" to your Document_ROOT or Absolute Server Path to complete the path to your Writable WebSpace.
Once you've determined your Absolute Server Path, open [script]_key.cgi in Plain Text Editor (not a WYSIWYG Text Editor, nor a Rich HTML Editor) and set the $DefaultData Variable. For example:
$DefaultData = "/var/username/www/htdocs";
Finally, on some Server's it's necessary to CHMOD the folder just above your WebSpace to 777 granting permission to the CGI Script to create the Required Directories at WebSpace Level. In the example above, the "htdocs" folder would need to have it's permissions set to 777.
- We offer a very reasonably priced Custom Installation Service. We'll Setup the CGI Script for you and send you the Log in details which you can update at your own leisure. If we cannot successfully Setup the CGI Script we will refund both the Installation fee and the purchase price of the CGI Script. To Order Custom Installation, please fill in our Secure Installation Order Form.
Installation - Windows Servers
[script] refers to the first portion of the name of the CGI Scripts you purchased.
- Your Windows Server may not execute CGI scripts even if Perl is Supported. Many Server Administrators do not modify the Registry to accommodate Scripts with a .cgi extension. In this case, contact us for a copy PL Version.
- Setting the Path to Perl. Your Server may or may not require the Path to Perl. It's highly likely you don't need it, and you can ignore this Step. However you may want to check with your Host if you can not load the Setup Script in your web Browser.
NB: if you do not you a Plain Text editor such as Windows NotePad or Mac Textedit (in Plain Text Mode), your Text/HTML editor will add extraneous code to the CGI Script when you save it which will result in a server 500 Error.
- Upload all CGI Scripts to your cgi-bin or any cgi enabled directory. It is imperative that you upload (transfer) all CGI Scripts to your server in ASCII mode.
If you do NOT upload (transfer) all CGI Scripts to your
server in ASCII mode, Step 3 will yield a Server 500 Error.
- Load your Browser, point it to the [script]_setup.cgi file and follow the on-screen instructions for installation. For example, in your browser, type :
http://www.yourdomainname.com/cgi-bin/[script]_setup.cgi
- Enter a Username and Password. This will be your Username and Password for the Administration Section. If the Setup Routine is successfully processed a link to the Administration Section will appear on the resulting page. Click the link to access the Administration Section with the Username and Password you just entered in the Setup Script.
Should you encounter any Permission problems during the Setup Routine, you need to contact your Host and request "Full Read/Write Permissions" be applied to at least one folder on your Server. Many Servers have at least one writable folder, often named "database". See Common Installation Problems below for more information.
Upon successful completion of the Setup Routine the [script]_setup.cgi_setup.cgi script attempts to delete itself. This ensures the Setup Routine can not be repeated by another Surfer who would effectively reset your Administration Section Username and Password. Manually delete the [script]_setup.cgi
CGI Script you uploaded if the Setup Routine could not automatically
delete it (Refresh your FTP directory listing to check).
Should you ever forget your Administration Section Username and Password you can repeat this Step to set a new Username and Password.
Common Installation Problems - Windows Servers
NB: Shared Secure Servers, VPS, SBOX and Free Servers.
- Server 500 Errors are usually misleading on Windows Servers. It seems to be the default error page for just about every error. Make sure you typed in the correct Website Address (URL) to the CGI Scripts on your server. Make sure the CGI Scripts were transferred in ASCII Mode. Auto-Detect only detects the extensions you specify in your FTP client's Settings.
- I can initially load the Setup Script and punch in my Username and Password, but when I submit the Form, I receive 404 Error Page or an alternate Error Page stating "Page Cannot be found".
This suggests your Server is operated by a very nervous System Administrator employing strict security measures, you're using a Shared Secure Server which dynamically sets your domain name to something other than the a standard Top Level Domain (www.yourdomainname.com) or sbox is employed by your server.
In any case, open [script]_key.cgi in Plain Text Editor (not a WYSIWYG Text Editor, nor a Rich HTML Editor) and enter the URL to the folder you uploaded the CGI Scripts to in the $SecureServer Variable. If you uploaded the CGI Scripts to your cgi-bin, then you'd set the following:
$SecureServer = "http://www.yourdomainname.com/cgi-bin";
Do NOT enter the CGI Script name, do NOT enter a trailing slash. After setting the Variable refresh the Setup Routine's Page that asks you to enter your Username and Password. Unless you refresh the initial Setup Page, the Form's URL will not be updated to reflect your Variable value.
- I cannot find the correct path to my WebSpace or the required Data Directories and/or Password file cannot be created.
You need to find that Path. Ask your host, or Download a copy of our free E-Vars CGI Script and install it on your server. You will need to rename the E-Vars CGI Script to "myserver.pl" if your Server only executes Scripts with .pl extensions. Upload it to your cgi-bin or any cgi executable folder then load it in your Web Browser which will print your Server's environment variables and other useful information. Determine your Server's Document_ROOT or Absolute Server Path to the folder your home page (index.html) resides in. You may need to append "\\www" or "\\httpdocs" to your Document_ROOT or Absolute Server Path to complete the path to your Writable WebSpace.
Once you've determined your Absolute Server Path, open [script]_key.cgi in Plain Text Editor (not a WYSIWYG Text Editor, nor a Rich HTML Editor) and set the $DefaultData Variable. Be sure to separate folder names with two backslashes, not one slash. For example:
$DefaultData = "C:\\html\\username\\htdocs";
- We offer a very reasonably priced Custom Installation Service. We'll Setup the CGI Script for you and send you the Log in details which you can update at your own leisure. If we cannot successfully Setup the CGI Script we will refund both the Installation fee and the purchase price of the CGI Script. To Order Custom Installation, please fill in our Secure Installation Order Form.
License and Disclaimer
The following constitutes an agreement between you (the end user/purchaser) and us, PerlScripts JavaScripts.com (a wholly owned subsidiary of InterActive Scripts). By purchasing and using our software, products or services you agree to and accept the licensing agreement stated on this page. All documentation, goods and services are provided "as is" and without warranty. We hereby disclaim all warranties relating to any documentation, goods and services, whether express or implied, including warranties of suitability. In no event shall we be liable for any direct, indirect or consequential damages resulting in loss of revenue or data, incurred by you or any of our products, information or services. We reserve the right to revise the terms and conditions stated on this page at any time without notice. You agree to be bound by such revisions, and you are encouraged to periodically revisit this page to review the then current terms and conditions.
We grant you the right to use one copy of the software, product or service purchased, for testing and familiarization purposes. We also grant you the right to implement, install and use one copy of the software, product or service purchased on a single web site domain for use by one entity once the evaluation copy is removed / deleted.
By purchasing a product you are also subscribing to our periodic newsletter which will notify you of new software releases, updates and special offers. In accordance with United States and International anti-spamming laws, an unsubscribe link that removes you from all future mailings will accompany each e-mail notification.
For taxation purposes, we must keep accurate transaction and installation records. At the time of software installation, you will be asked to enter information such as your web site's domain name and your product's serial number. This information is used to validate copies of our software.
We reserve all rights. Written permission must be obtained from us before you may copy, reproduce, publish, modify or alter in any way, any media, software, documents or products, in part or in whole, contained within our web site or traded by us. All media, software, documents and products are the property of PerlScriptsJavaScripts.com. We retain ownership and copyright of software products purchased from us and all copies of the software. As a licensee you may make one copy of the software product solely for backup purposes. Removal of any copyright messages, publicly visible or otherwise without prior written permission from us is expressly forbidden. Unauthorized reproduction of any of our software, documents or products is prohibited by Federal and International laws and subject to criminal prosecution.
Any use of software and accompanying documentation on our Web site is subject to the terms of a software license agreement between you and us. You must read this license agreement in it's entirety and agree to it's terms prior to installing or using the software. All ownership rights and rights not implied are reserved. We reserve the right to revoke these permissions and terminate this agreement at anytime or at it's own discretion without reasonable notice. We reserve the right temporarily or permanently discontinue any software product or the support associated the product at anytime or at it's own discretion without reasonable notice. You agree and accept that we shall not be liable to you or to any third party for any such cessation.
You agree that any issue or dispute that may arise between PerlScriptsJavaScripts.com and yourself in respect to this web site or it's goods or services will be resolved and governed by and within the courts and laws of Melbourne Australia. If your local laws do not allow for such an agreement, you must delete all copies of products supplied to you by us and you are hereby notified of the termination of this license.
Getting Started
Once you've installed Website Manager, the first thing you should do is decide where you want all Users files to be stored. By default, the following directory structure is used.
Member Files
/document_root/webman/wmfiles/username
Member Include Files
/document_root/webman/wmzones/username
Member Image Files
/document_root/webman/wmimages/username
Where "document_root" is the folder your website's home page resides in.
You can however restructure the folders to suit your preferences. The scripts will automatically create the folder paths defined, provided the 3rd last folder in your defined paths already exist.
To define folder paths, once logged in, click "Settings". Click the Gray colored links for more information on each option.
Next, click "Summary" then "Build Tree now". This will recursively fetch a complete list of folders from the path defined in the "Document Root" setting. This complete list of folders will only be accessible and visible to Top and Second Level Administrators.
Regular Users will only have access to folders they're granted access to in their User profiles. Whenever a new User is added, the User is granted access to their folders only. See Managing users for more details.
Managing Users
If you purchased a Multiple User license, Website Manager supports additional Users, each of whom have their own rights and privileges. To add new Users, click "Users" then simply type in an e-mail address, username and password (all required) then press the button labelled "Add new User". The page will refresh and you'll see a list similar to that in the following image.
Creating new Users spawns the following processes.
- A new folder, using the User's username, will be created inside the folder defined in the "User folder" setting. This folder is where the User can create folders and pages.
- A new folder, using the User's username, will be created inside the folder defined in the "Zone folder" setting. This folder is where the User can create Zone or Include files. Top and Second Level Administrators can also create shared content files which all Users will have access to. See Zones for more detailed information.
- A new folder, using the User's username, will be created inside the folder defined in the "Image Folder" setting. This folder is where the User, if permitted, can upload files to.
- By default, the new User will only have access to the three folders created for them. They will not have Upload or Deletion privileges.
Next, to edit the User's Rights and Privileges, click the Green colored link in the Active column of the User list. The "Document Root", "Zone folder" and "Image folder" settings, should all have paths defined that include the Users username. This ensures, they can only access areas which are at or below their own folders. If a User is trusted, you can grant higher access by back peddling those paths.
- Treat these files as web files
- These govern which file types are treated as WYSIWYG editable files. Add the keyword "default" without quotes and in lowercase to have the WYSIWYG editor display by default when creating new web pages or zones. These Settings will also appear when a User logs in to edit their own profile.
- Account Status
- An "Account Status" of "InActive" will prevent the User from logging into the system.
- Access Rights
- Access Rights can grant the User access to your entire website if incorrectly set. The default setting will grant the User access to only their own folders.
- This user may edit any page in any folder on the server
- This should only be selected for trusted Users.
Selecting this option will grant the User access to every folder and file on your website. It will even grant them access to folders and files on the rest of your server if your defined "Document Root" folder in the main Settings is above your web space.
- This user may edit any page in any folder in their Document root
- This is the default setting applied whenever a new User is created. Selecting this option will grant the User access to every folder and file from the "Document Root" defined folder in the User's Profile. This is the recommended setting for regular Users.
- This user may edit pages only in the following folders
- This should only be selected for trusted Users.
Selecting this option will enable the following two settings which enable you to define a comma separated list of specific folders the User may access. The User will have access only to the folders you explicitly enter in the "Folders" setting in their profile. The keyword "ALL" in uppercase can also be entered which will grant the User access to all folders and files on your website.
- Deletion Privilege
- If checked, grants the User the ability to delete any file or folder they have been granted access to.
- Upload Privilege
- If checked, grants the User the ability to upload files to any directory they have access to. If checked, the Upload icon will appear just above the Folder listing which appears on the "Web Pages" page. When clicked the User will be taken to the File Upload page which lists your restrictions as defined in the "File Upload Settings" sub-section of the main "Settings". These settings apply globally to all regular Users.
- Subordinate level admin
- This should only be selected for trusted Users.
Second Level Admin Users. If checked, grants the User access to all folders and files on the entire website, as well as access to all User profiles and the entire system, excluding the main "Settings" and "History" records.
The User profile fields will appear when a User logs in to edit their own profile. You can add extra fields to this area if you log in as Top Level Admin and click on "Settings". When on the Settings page, scroll down to "User profile Fields" and enter the form field names as you'd like them to appear on the Profile Edit Form. Use the following naming convention so that the filed names can be understood be regular users:
User real words.
Separate words with underscores _
Do not add the fields : username, pass, or email as they are already included in User profiles
Saving files
To save a file, click the last button in the Toolbar (the floppy disk). This will produce a drop down menu asking you to enter a name and directory path for the file.
When editing existing files the fields will be pre-populated. If you change the name of the file in the file field, it will create a new file and leave the original file unchanged. If you leave the file name unchanged, it will overwrite the existing file.
When creating new files, the directory field will be pre-populated with your Start up directory. This path can be changed so that the file is saved in the desired directory. You'll need to then enter a name for the file.
Zones
Zones are designated areas within a web page. They serve a double purpose. 1) You can create zones and then grant selected users access to those areas and 2) they act as Server Side Includes which means you can update multiple pages by editing one zone. See this page for a detailed explanation on SSI.
Shared Zones
As a Top Level Admin, you can select the folder the Zone will be stored in when creating Zone files. The "shared" folder is used to store files which are accessible, but not editable, by all Users. This folder can be used to store advertisements, news feeds, copyright links or messages to your Users which can then be updated across your entire website, where ever the Zone has been utilized, by editing the one Zone file.
Similarly, each User has their own private Zone folder in which they can create their own Zones for inclusion on any of their web pages. Again, if the user includes the Zone on any number of pages, they User simply needs to update the Zone file to update all pages which have that Zone included.
To create a Zone, you should first create a Zone by clicking on Create Zone in the Control Panel. When saving Zones (as a regular User), the directory path is set to the folder you have specified in the User's Settings. When saving Zones as an Administrator you specify which folder the Zone should be saved in by selecting a folder from the select menu that appears when the Save icon is clicked. In all cases, the name of the Zone file SHOULD NOT be changed once created (and inserted). To save the Zone, click on the last button in the Toolbar.
To create a Zone for a User
- Click on Create Zone in the Control Panel.
- Add the content for the Zone.
- Click the last button in the Toolbar to Save the new Zone.
- Select the directory belonging to the User from the select menu.
- Enter a file name (this can be anything and should include an extension that belongs in the User's list of WYSIWYG files so they can edit the file using the WYSIWYG editor)
- Click Save.
Once you've created the zone, you can then include that zone (using a special tag) in as many pages as you like.
To include the zone in a web page
- Create a new page (Create Page) or edit an existing Page.
- While working on Web Pages (as opposed to Zones), you'll see a drop down select menu with "Insert Zone" as the first option. This menu contains all existing accessible Zones.
- Make sure the Zone tags are visible. You do this by clicking on blue Zone icon near the end of the Toolbar. It alternates between Visible and Invisible mode.
- Next, place the cursor in the position on the page where the Zone should be inserted, then select the desired zone from the drop down select menu.
The last step above will insert an SSI tag that looks something like :
<!--#include virtual="/wmzones/header.zone" -->
Server Side Includes
Zones are better known to webmasters as Server Side Includes. As the name implies, a file is included within another file. This means that any of your web pages that have the same Zone or SSI tags are all updated when the file the tag is pointing to is updated. Ideal for navigational menus, header, footer, copyright messages or any information that remains constant across multiple pages and is regularly updated. Correcting a broken link or spelling error on 200 pages is not an enjoyable task.
N.B. If using the WYSIWYG editors at all, your Zones should be either complete Tables or use no Tables at all. That is, you cannot split a Table tag down the middle and use half in one (header) Zone and the other half in another (footer) Zone. This is because the WYSIWYG editor will close your Table tags for you and upset the desired flow of a page.
A note on file extensions
On Unix, Mac, BSDOS or Linux flavoured servers, when creating web pages the use Zones or Include files, the extension often needs to be either .shtml or .shtm. The Zone file itself can use any file extension. An Apache directive can also be used to set the server to recognize .html and .htm files as files that should be parsed by the server so that SSI tags are processed rather than printed. To do this, create a file named .htaccess (or if you already have a file named .htaccess in your document root, edit that file). The directives you need to include in the .htaccess file are :
AddType text/html .shtml .shtm .htm .html
AddHandler server-parsed .shtml .shtm .htm .html
Upload the file named .htaccess to your document root. Your server should now parse .shtml, .shtm as well as .html and .htm files.
On Windows servers, when creating web pages the use Zones or Include files, the extension often needs to be either .stm or .shtm. The Zone file itself can use any file extension.
Changing your password
Enables you to update or change the Top level administration log in details. Enter your current log in details, enter your new log in details and press the button labelled "Change Pass".
|
|
|
