MerryVIP, I shall re-send the source code as well as the setup package to you today night, that's about 10 hrs from now. I am in the office at present, and don't have it here.
Also the code database is supposed to store code snippets at a single place. If you surf sites such as www.vbcode.com, you find many small pieces of code which are useful. The code database was designed to provide a means of storing these pieces all in one location where you could search a code snippet and use it in your code.
The application is in its infant stage and doesn't do much than storing the snippets and displaying them in a Tree View structure for easy reference.
As for the database part, I do not know the architecture of the MySQL database system, but we can design an Access database which will later be transported to MySQL. Either through code or through some tool if present.
The documentation at the PHP site says it provides for a way to store your site details in a database from where they are retrieved every time. This way if you have to change some vital aspects of the site tomorrow, you don't end up modifying hundreds of pages. For e.g. the background colour used for the left-hand menu pane, or the font used to show the plain text. If we store such details in the database, every time the PHP scripts will pick them up from the database and use them. So, tomorrow if we need to change the font for the regular text, all we need to do is change a single field in the database.
Scoutt, PHP essentially is a freeware version of ASP, although uses a different technology. It has its own server extensions, I think you must already be aware of it. The point is just like ASP pages require an extension of .ASP so the web server can execute them, the PHP pages require the extension .PHP or .PHP4 etc depending upon the PHP configuration at the server. There may not be any other requirements for running PHP. And csammis has already informed that the PHP pages need to have the extension .PHP
You can try uploading a couple of test pages on the site tomorrow when it's up, and see the results.
It looks like the FTP is going to be difficult with two people trying to develop the site together from two different places. What I mean is Scoutt will write the PHP scripts and MerryVIP will write the HTML pages, and the two have to work together. If Scoutt sends the PHP pages to MerryVIP, there is no way to test them until they are uploaded to the server.
Scoutt, do you think you can test your pages on your machine? Can you download the same version of Apache Webserver and MySQL that csammis's machine is running ? This way you can test the scripts before sending them to MerryVIP for uploading. This will save us a lot of trouble since there are problems in direct access to the server.
About the emailing, Scoutt, if you cannot configure the email list to have multiple destinations at present, there won't be a big problem. In that case, we need to centralize the email retrieval process at one location, i.e. assign a person to read all the emails received from the visitors and then take the necessary action accordingly, like forwarding technical matters to the respective members etc.
MerryVIP, can you take the responsibility of setting up the Guestbook and the Hit Counter? As soon as the site goes online tomorrow morning, you can upload these two parts there. About the Guestbook, we can have two approaches. Implement an ordinary guestbook or directly go for the feedback form we have talked about. If you think the feedback form is complicated, let's have the guestbook as in most other sites. The only thing is the site password required to read the guestbook entries. Either we have to let all see the guestbook entries or distribute the password amongst us so we can read the guestbook at our leisure.
Once the guestbook is implemented, we can ask members to directly post their comments there, and any time we make modifications, we can ask them to re-visit the site. Also we can ourselves start posting feedbacks right there.
.
