Administrator Page for Form Creator Form

This script is called administrator-page.php

The Administrator Page for Form Creator Form script is one of a group of PHP scripts that handle both the administrative and end-user aspects of a general purpose HTML Form Creator that allows not just input boxes but multiple selection enabled select/option lists as well. In addition to the expectable editing scripts for both administrative and end-user functions, there's also a Search and Match script so that users can use the scripts to find other users with various individual or group commonalities, including proximity searches, i.e., find all the users within various distances. There are even private messaging scripts.

Administrative HTML Form Creator Scripts

First, we start up a session and include the config.php script to ensure that our connection to our database is made correctly. This file has the codes below in it:

$theemailaddress = "yoursite@yoursite.com"; //EDIT ME
$roothostname = "localhost";
$theusername = "yourusername"; //EDIT ME
$thepassword = "yourpassword"; //EDIT ME
$thedatabasename = "yourdb"; //EDIT ME
mysql_connect("".$roothostname."","".$theusername."","".$thepassword."") or die(mysql_error());
mysql_select_db("".$thedatabasename."") or die(mysql_error());

Next we present links to the three administrator pages in our HTML form creator CMS system. The first link is to html-form-creator.php. In this script, the administrator inputs both the form question and the input size allowed. For example, zipcode would be five characters long so that is what would be appropriate to enter. The input filter is fairly liberal—you can enter 1 to 50 alphanumerics and ! $ % - _ ( ) ? . , ' characters. The single quote will turn into middot characters(·) to prevent hacker exploits with ' characters.

The next link is to edit-options-in-html-form-creator-form.php. This script allows the administrator to Edit Options in the HTML Form Creator Form. You select which question row to add or edit or delete options on, then jump to the edit or delete or add page where you see only the options for that one question row. You select one of the options to edit or delete and then do so and submit the form. Or you add an option, which requires no selecting of options. Then submit the form.

The last link is to the script on this page: administrator-page.php.

Next we give detailed instructions about the use of the two main administrative scripts in our CMS for HTML form creation:

Please be aware that once you have users who have entered data into your form which goes to MySQL tables, the changing of the questions, fields and/or options will mess up database tables, user experience, everyone's records, etc. It is MUCH wiser to create an optional input table and options table with a different "db name" and put them in a different MySQL database, so nothing is wrecked and no one gets their records trashed. The new "db name" can have a different version of your form inputs and select/options which you may use with a separate population of users. If you try to use it on current users, confusion and chaos will reign. By "db name" we do not mean a MySQL database—it's just a table name prefix. Only one of your HTML form "databases" can be put in the same MySQL database, to avoid confusion, and because there is to be only ONE my_members table PER MySQL DATABASE where all users' registration data resides. We are using the term "db name" to refer to a name prefix for the "database" that is composed of four tables, the my_members table where all users' registration data resides, the table ending with _database, which holds user input, the table ending with _inputs, which holds the HTML form questions and input sizes, and the table ending in _options, which holds all select/options list data. So if you make any alternate HTML forms, place them each in different MySQL databases (using separate, different, config.php files) with separate members populations to avoid confusion.

The script below is called: administrator-page.php

<?php
session_start();
include('config.php');
?>
<html>
<head>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
<TITLE>Administrator Page for Form Creator Form</TITLE>
<meta name="description" content="Administrator Page for Form Creator Form">
<meta name="keywords" content="Administrator Page for Form Creator Form,form options,edit options,options,HTML Form Creator,Form Creator,php,javascript, dhtml, DHTML">
<script language="javascript">
mactest=(navigator.userAgent.indexOf("Mac")!=-1) //My browser sniffers
is_chrome = navigator.userAgent.toLowerCase().indexOf('chrome') > -1
Netscape=(navigator.appName.indexOf("Netscape") != -1)
msafari=(navigator.userAgent.indexOf("Safari")!= -1)
wsafari=0; if(!mactest&&msafari){wsafari=1;msafari=0}
is_opera = 0; if(window.opera){is_opera=1}
is_ie_mac = 0; is_ie=0;if(document.all){is_ie=1}
if(is_ie&&mactest){is_ie_mac=1}
</script>
<style type="text/css">
BODY {font:15px Verdana;margin-left:0; margin-right:0; margin-top:0;text-align:left}
p, li {font:15px Verdana; color:black;text-align:left}
</style>
</head>
<body>

<center><h1>Administrator Page for Form Creator Form</h1></center>

<center><div style='width:600px;padding:9px'>
<a HREF="edit-options-in-html-form-creator-form.php">Edit select list options</a><BR><BR>
<a HREF='html-form-creator.php'>Edit input fields</a><BR><BR>
<a HREF='administrator-page.php'>Administrator Page</a><BR><BR><hr><P>
Please be aware that once you have users who have entered data into your form which goes to MySQL tables, the changing of the questions, fields and/or options will mess up database tables, user experience, everyone's records, etc. It is MUCH wiser to create an optional input table and options table with a <B>different "db name"</b> and put them in a <B>different MySQL database</b>, so nothing is wrecked and no one gets their records trashed. The new "db name" can have a different version of your form inputs and select/options which you may use with a separate population of users. If you try to use it on current users, confusion and chaos will reign. By "db name" we do not mean a MySQL database—it's just a table name prefix. Only one of your HTML form "databases" can be put in the same MySQL database, to avoid confusion, and because there is to be only ONE my_members table PER MySQL DATABASE where all users' registration data resides. We are using the term "db name" to refer to a name prefix for the "database" that is composed of four tables, the my_members table where all users' registration data resides, the table ending with _database, which holds user input, the table ending with _inputs, which holds the HTML form questions and input sizes, and the table ending in _options, which holds all select/options list data. So if you make any alternate HTML forms, place them each in different MySQL databases (using separate, different, config.php files) with separate members populations to avoid confusion.</P>
</div></center>

</body>
</html>

Free Personal Status Boards (PSB™)

Administrator Page for Form Creator Form

Administrative HTML Form Creator Scripts

End-User HTML Form Creator Scripts