304357 Private project for Savindra

We need a simple php-based system that can interact with: 1.) our vehicle database (the same text flatfile db from our mobile project) and 2.) a new dealer database (which is different from the one in the previous project). The purpose of this system would be to create simple web sites for auto dealers "on the fly", by accessing information from those databases. An example of the end result that we are looking for (e.g., a typical site generated by this system) would look a little bit like this: [login to view URL] Two Databases: ----------------------- So ... for the "inventory" section, the script would be pulling results from our vehicle database, just like the mobile script. It would be returning records with a match in the dealerID field (column 11). To build the content of the other pages, the script would simply use information contained in the dealer database. Let's call this second database "dealerArray". I would recommend that this dealerArray be a simple mySQL database. It would contain information such as the dealer address, phone number, email, etc. For this mySQL database, we would need a simple "admin" access that would allow us to add / edit / delete dealer records. I am imagining a simple form that would allow the input of the fields for a record: dealer code, dealer name, address, phone, email. Also, two other fields on this database: - An "upload" field for an image file that will be used for the header (i.e., if the dealer code was "ABC", the file would be written as "[login to view URL]" in a specific location, which would be the URL for the header image). - An "upload" field for a "lot photo" image file that will be used at the top of the homepage body. - A textarea field for the text that will be used in the homepage body. This field should be able to "pass through" HTML ... that is, if text is written as "<h1>text</h1>", it should come out in the homepage as a "headline" type text. Basic functionality: --------------------------- The dealer ID can be fed to the script through the URL if needed, such as for example: /[login to view URL] ... where "ABC" is the dealer ID. The different elements of the page can be built "on the fly" using the info in the dealerArray database. So, as an example, the footer at the bottom of each page can be generated by writing the dealer address and phone number from the dealerArray file. The form on the "contact" page can have the email address from the dealerArray database could be inserted automatically into it (as a hidden field). You get the idea. For all pages, the script would have to load/generate the correct header (the image file that has been uploaded for that dealer in the dealerArray database). For all pages, the script would also have to generate a footer, similar to the one on the example link above. It could do this easily by simply calling up that dealer's address and phone info from the dealerArray database. For all pages, the script would have to generate a navigation bar, similar to the one on the [login to view URL] link above. As with the header and footer, the navigation bar can be the same on all pages. The script simply needs to be able to write the dealer ID into the links so that the right page will be called up (i.e., [login to view URL]). (If you wish to do this in a different way that doesn't pass the dealer ID through the URL, that's fine too). All pages should have a page title consisting of the dealer name and address, from the dealerArray database. The pages required would be as follows: Homepage: ---------------- The homepage would have the "lot photo" image file that was uploaded for that dealer in the dealerArray database, and below this, the corresponding text that was written in the textarea field of that dealerArray record. That's all (along with the header, footer, navigation bar, etc. of course). Inventory page: ---------------------- This page would consist of a simple search box (as on [login to view URL] example above). Below that would be the listings, pulled up from the vehicle database by the script. Each record in the vehicle database has a dealer code (column 11) ... the script would simply have to return, for example, listings with a match for "ABC" in column 11. This is very similar to what we did with the [login to view URL] Mobile script, in fact you may be able to reuse some code : ) Record page: ------------------- As on the mobile script, each individual listing should be a link, of course, and that should lead to a record page that shows the listing with multiple photos viewable, similar to the example link). Clicking on any photo should result in this URL: "[login to view URL]*" with "*" being the vehicle's recordID (column 8) in the database. This link should open as a simple lightbox-type window (see the header of [login to view URL] for the pre-existing implementation ... you just need to copy that ... it is very quick and easy). There should be a simple contact form on the record page, which has the same form action and the same hidden and shown fields as the contact form which can be seen at the bottom of [login to view URL] Directions Page: ------------------------ This page should contain a prewritten phrase, such as "stop by and say hello, we are easy to find at *" where * is the dealer's address, which will be available in the dealerArray database. Below this, there should be a Google Maps map of the dealership, generated using the address. Below the map, there should be a link that says "click here for directions", which leads to a Google Maps directions page with the address passed through to it -- just like we did on the mobile project. Contact Page: --------------------- There should also be a contact form page, consisting of the normal header/footer wrap, etc., with a simple bit of static text (e.g., "contact us today" followed by a simple contact form. The script would need to write the dealer's email address from the little dealership database into the form, as a hidden element. Admin Pages: -------------------- Remember how, in the mobile project, I asked you to take a pre-existing PHP script on our site (the dealer zip code locator), copy it, and incorporate it into the mobile script? Here we would need to do the same with a different script. We have a script on our site which allows a user to log in and add/edit/delete records. You can see it here: [login to view URL] To experience its functionality, login as user "nisqually", password "516sell". If you look on our server, you can see that this script is very simple. It consists of four simple "template" files (found on our server in /cgi-bin/data/ folder), the cgi script itself (/cgi-bin/[login to view URL]) and a simple user file (/cgi-bin/[login to view URL]). For the admin section of this project, we simply need for our script to open a copy of this [login to view URL] login script whose template pages have been modified to provide the header and footer and navigation menu of the dealership site. That's it. Does that make sense? It would mean copying the script and making sure that the script's template pages can have the same header/navigation menu/footer "wrap" as the other pages above. So, the links on the navigation bar should be: Home | Inventory | Directions | Contact Us | Admin That's it. With this system working properly, my company staff should be able to generate a new dealer website by simply creating a new record in the mySQL database admin page, entering in all the dealer info (phone, address, email, etc.), writing the "homepage textarea" text, and uploading image files for the header and "lot photo". Does that make sense? I appreciate your taking the time to read it. I know that I've written a lot here, but it's mostly because I am trying to be extra clear and detailed to make sure things sound logical. I figured that it might interest you because in many ways this project has a lot in common with the mobile site project and could maybe even reuse some of its code. Anyway, if you'd be interested, just let me know what you would predict in terms of cost and time required, and maybe we can get something going on. It would be good to work with you again. Thanks again, and I look forward to hearing from you ...