145122 oscommerce - vehicle database

This project needs to be done within 7 days. Please bid only if you have read the description below and are really able to complete the task in time. Ask any additional questions in PMB. So basically - Need a vehicle database system where the customers will pay for viewing the vehicle data. Need php programming and some javascript/ajax, design is not needed. A modified oscommerce engine is currently installed on the site, need several tweaks to be done. The site is not live yet, ftp access is allowed. The products table will contain vehicles instead of products. The vehicles are not to be purchased online, customer only can view the vehicle info, so shopping cart is not needed. The checkout page must be modified to purchase credits instead of standard oscommerce checkout process - see details below. What we need: 1. Attributes system. Need to manage multi-template attribute system. Need a control page where the admin will be able to create, edit and delete the templates. The templates are intended for different vehicle types - car, truck, SUV or whatever. There is a set of attributes in each template, admin needs controls to add/edit/delete attributes There is a fixed set of values for each attribute, admin needs controls to add/edit/delete values There is a css class name assigned for each value of each attribute (used for frontend display - just a pickup of static predefined classes). There is an ajax-based oscommerce product attribute manager already installed, need to somewhat tweak it. Each product in assigned to a particular attribute template (selected on the product edit page) The attribute list and choices for the product (select boxes, only one value to be selected for each attribute per product) are displayed on the product edit page and stored in the database. (you may use existing products_attributes table or whatever) The list of attributes and their values is displayed on the customer's product info page, the particular css class is applied to each attribute line (that's the per value class defined in the template) Note - the attributes and values must be linked to a vehicle by id - not be name/text, so modifications to existing attributes/values will affect all existing vehicles. 2. Credit system The customer must be able to purchase credits on the existing [login to view URL] page. No need for shopping cart. The admin must have a control to create/edit/delete credit packages - package title, credit amount, and package price. The packages are to be stored in a database table. Need a page for customer to pick up the credit package and go right to checkout page, need to tweak [login to view URL] and includes/classes/[login to view URL] to just set the order total to the selected package's price instead of shopping cart / product list handling. On successful purchase the credits are added to the customer's account (need a new field in 'customers' table). On viewing the product info page - the script checks whether customer is logged in ($customer_id session var) and has enough credits to view the page - otherwise redirect to login / payment page. The customer is charged only for the first view of particular car - the customer's credits are decremented and the tracking record is created in the database. If the tracking record for this customer/vehicle pair already exists - the customer is allowed to view the product info again with no charge. 3. The system must be possible to handle unlimited number of images per product. Currently there are 1 main image and 4 alternate images. The alternate images are stored in products table, fields products_image_xl_1, products_image_xl_2 etc Need to add a separate table for images which will store unlimited images per product. The admin's product edit page and customer's product info page must be tweaked appropriately. P.S. Please don't try to fool me - i'm a developer. Thanks Jim