Introduction
The site template represents an effort to utilise a purpose built MVC framework to achieve all of Triangle's internal web site needs.
The framework allows for a multi-site, multi-package arrangement; which is fully scalable.
Packages
All sub packages can be included into any site, by a simple means of linking to them, each package in essence is its own sub-site with internal navigation, constants and database tables.
Each package must have the following:
- index.php as its controller to include all the required files.
- header.php includes all the top navigation for this package.
- constants.php includes all the package constants and database definitions.
Logo Specs
- Width 300
- Height 76
- Font Gill Sans
Require PEAR Packages
- pear install -a DB_DataObject
- pear install -a HTML_Page2
- pear install -a HTML_QuickForm
- pear install -a HTML_Template_Sigma
- pear install -a Mail
- pear install -a Pager
- pear install -a Text_CAPTCHA
- pear install -a Translation2
Options
- USE_DB - If present the Database connection will be made, i.e. define('USE_DB', 'Database');
- USE_USE_HEADER_LINKS - If present the links in the top right will display i.e. define('USE_HEADER_LINKS', true);
- USE_LOGIN - If present login will be enabled - also require USE_DB i.e. define('USE_LOGIN', database_users); also defines what table to use for login purposes.
- USE_TRANSLATION - If present uses the translation engine, requires a table called translations.
- USE_SEARCH - Whether to show the search form
Process On Payment On Site Template
This outlines the requirements for using the PayPal IPN on the Site Template.
- User completes the join / purchase form.
- On completion and validation the data is saved into the database with a paid_id = N
- The users HASH is passed through PayPal in the custom variable.
- The user processes the payment and is taken back to the Return screen to see a thank you, nothing dynamic happens on this screen.
- PayPal posts to an IPN page which needs to be secured against intrusion. The IPN data is validated and if true updates the user paid status to Y and allows login.
- Once in the site the user can proceed with membership activities or download the application if they paid for Triangle software.
- To test the PayPal use the Sandbox configuration here PayPal Sandbox
- All the post data is then stored in the DB for later checks.
- The user is emailed at this point to say that payment has been authorised and that login / download are not active.
ToDo
- Set up the mail lists need a general one and one for each application I think.
- More information and screen shots on the products pages.
- Home page - want generic link to join Newsletter
- Home page - want generic link to login to Triangle Admin for clients.
- Support options - mail list, Yahoo Forum (Change to Google, install Vanilla ?), Link to hosted support tickets.
- Portfolio area - add in more elements - Featured portfolio should be Beep and IamSafe. Add in the gallery page again and put all the sites in there.
- Need to get the translation options working on the site template.
- Breadcrumbs need optimising and finishing off - Method in Static_site_template controls these.
- Complete the BIO pages.
- Site map generation through Google site maps.
- Footer element
- News from database
- Products can PHP Shop be added to this?
- Spell and grammar check
- Need to template more of the elements within this site.
- Go through PayPal stuff and see how they can pay via CC, also integrate PayPal via the SOAP method in the PHP PayPal SDK.
- Add Top element in the support FAQs
- Check all the links on the essential files regularly within support.
|
|
