RMDatabase is not a commercial product and is still not to the level that I would envision it to go. It does still lack in its language abilities and eventually I hope to have it completely multi-lingual capable. Because it is technically a "free" package (to LDS Mission Network affiliated sites), I cannot guarantee support. I do try and help where I can, but sometimes it is just not possible. I will not be responsible for any data loss or damage that comes from usage of these scripts. By using them you agree to indemnify me from any liability that may arise from their use. I recommend routine backups of your data directory (which is always a good practice anyway).

I know some will ask why the effort on a new RMDatabase version. Dan Wilson's Site-in-a-Box (SIB) is making great strides and is a great alternative to those wanting to get a site up and running with minimal effort. There have also been efforts to create a centralized database that runs on mission.net that webmasters can utilize for their own sites. The advantage here is when webmasters decide to abandon their sites, the data is not lost. This is a worthwhile effort and I don't want to take away from it, but we are not there yet and I wanted to have a tool that can still be utilized on mission.net or any other ISP without requiring any external packages or database servers to run. Version 4 contains many enhancements and is a feature-rich product that I think mission alumni page webmasters will really like.

RMdB 4.x is a result of comments and requests received from users of version 3.x from years of use. The following list represents just some of the enhancements in version 4:

1. Integrated Administrator functionality - version 4.x uses a cookie to store the administrator password in the admin's browser. The password can stay active indefinately (until the admin click's the logout link) or the admin can have the password be active for only his/her session (until the browser is shut down). This means that once the administrator is logged in, there are no password requirements on any function.
   
   Essentially, there is only one point of entry to the page. There are still physically two scripts (rmdb4 and rmadm4) but from the browser perspective, everything is combined. All pages displayed have admin functions integrated into them and only manifest themselves if an admin currently viewing the page.
   
   
2. Template Controlled Pages - version 4.x uses templates to determine how pages are displayed. This gives the admin greater control and flexibility in use of colors and graphics. Data from the database is displayed as a module on some pages (that can be put where ever the admin wants) and on the profile detail and edit pages the admin can customize the layout down to the field level.
   
   
3. Database Export Capabilities - with version 4.x, you can easily export all or portions of your database at any time. You can select groups of records (all records, by president, or by mission) and check the fields you want to include. The process creates a comma-seperated value (.CSV) file which you can bring into Excel or any other utility that recognizes that format.
   
   
4. Security Event Logging - version 4.x logs events such as invalid admin login attempts, invalid user passwords entered on profile updates, and password requests. The admin can view this log and then mark IP addresses to be included in the BADIPs file. Once an IP address is in the BAD file, all interactive functionality is denied to that address in the future.
   
   
5. Modified Search Functionality - version 4.x changes the way searches are done from the way they were done in the past. Now, there is essentially one search function that takes all the search parameters used and focuses in on the records that meet all the criteria. Now, instead of searching for a person by first letter of last name, you type as many letters of the last name as you want and the script will give you all matches. Combine that by selecting a mission president, time period, or current address and search results are displayed much faster (especially on larger databases).
   
   
6. Custom Settings Maintenance - version 4.x gives the admin the ability to maintain more switches and parameters through the browser than version 3.x. Some of these parameters are explained below:
   
   
   • Module Widths
   • Module Colors
   • E-Mail message files (you can now edit them through your browser as well)
   • Column Configurations (for lists - for sorting, columns to include, etc)
   • Toggle Lists and Search options to be included (or excluded) on the main database screen
   • Automatically convert case on Name(s) and addresses (you can select to turn this off, or force upper, lower, or mixed case).
   • Validate e-mail address and web address formats (if a user inputs an invalid e-mail address or web address, it is blanked out). Admin can toggle this on or off.
   • Toggle option to force all e-mail and URLs entered to be converted to lower-case.
   
   
   
   

Here is a description of the files included in this distribution: (The code between the filename and the description indicates the upload type needed - if you are FTPing these files to your ISP - [A]=ASCII upload [B]=Binary upload [N]=not needed)

This path represents the structure for mission.net users. If you are installing on your own ISP, the setup script will attempt to do the same setup but your mission_html directory may be called public_html on your ISP account.

		Home directory
			rmdb4
				data
					pres.db
					lang.db
					custom.db
					lost.db
					badips.db
					new_usrs.txt
					rqst_pw.txt
					rmdb4.log
				templates
					home
					default
					error
					column
					view
					edit
			mission_html
				index.html
				count.html
				other HTML files and directories
				cgi-bin
					rmadm4.cgi
					rmdb4.lib
					rmcgi.lib
					rmdb4.ini
					other cgi scripts
				rmdb4
					css
						rmdb4.css
					images
						bad_mail.gif
						del_rec.gif
						head_bot.gif
						head_top.gif
						ldsmn-88x31-m.gif
						mailbutn.gif
						sidebar.gif
						spacer.gif
						err_banner.jpg

RMdB 4.x introduces a new level of administrator control through the use of stylesheet (css) and template files. This is an advanced level of customization offered. You must be cautious when editing these files. If you don't understand HTML and CSS very well then I would suggest staying with the default files provided.

STYLESHEETS (CSS)

Upon installation, the rmdb4.css file is copied into the "rmdb4/css" directory off the HTML directory that was found on your account. This will be the only file in this directory. You may edit this file, add more classes, but be sure and not delete the classes that are there. The scripts utilize these classes when creating modules both for administrator options as well as regular user options. Again, you may modify the parameters on existing classes, just don't change the class names. Another good tip - be sure and save a copy of the original css file - just in case.

TEMPLATES

RMdB 4.x uses six template files for all of its functionality. Each template file is nothing more than a regular HTML file with special tags that the perl scripts run "search and replace" functionality on. In some cases, these tags also pass parameters to the perl engine that perform extra tasks or retrieve specific information from the database. These tags will be explained in detail below.

The six template files that are used are explained here. Each filename is fixed (you cannot define your own templates) and is used for a specific function:

All RMdB template tags use the following format (within the quotation marks):

"[<tag_name>:<param>]"

where <tag_name> is the name of the tag and <param> is the parameter string that is passed. NOTE: some tags do not require parameters.

Not all tags are available on every template. A list of the tags available as well as the templates they are available on and the function that they perform is explained in the table below.

Now finally, please be respectful of my copyright notice. I know to some, it may be considered a nuisance and I didn't require it on earlier versions - in fact, I even allowed the admin to customize the copyright line as they saw fit. I appreciated those that kept me (Moonlight Design) listed even when they were not required to do so. The "footer" class within the stylesheet controls the display of the copyright. You can adjust it how you see fit but I do ask that it be large enough to be readable.

This rewrite project has taken me about 50 hours to complete over a period (off and on) of 6 months. All I ask in return is credit for my efforts. I don't have any problems with people tweaking the code for use on their mission sites (although with the use of templates and stylesheets, this should be minimized), but selling, distributing, or profiting from the code is strictly prohibited. I am not charging anyone for this code, It is only logical that noone else charges for it. Also - as mentioned in the scripts, RMdB 4.x is not to be given or utilized by anyone not associated with LDS Mission Network.

Eric Huber (dba Moonlight Design)
Home: (801) 299-0851
Work: (801) 297-1654
moonlight@hubernet.com