That is looking good

I am going to dive in I think, and make the changes to FreeTrade, I will post my 
modified version back again.

I am going to set it up so you can choose from one of 3 layouts for a store. There 
will be a global products database, but filtered for each store.

Where you have different index.php files, I will use this to show the different 
shopping centres. But have all the different stores all inside one of the three index 
files.

eg. 3x Shopping Centres (3x index.php files)
    40x Stores per shopping centre.

All running off one Database.

Roger

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Lab2
Sent: 16 March 2001 07:49
To: FreeTrade
Subject: Re: [FreeTrade] Extend one Instillation to handlemultiple
websites


Yes...to some degree...

In anticipation/preparation for running different shopfronts off a single
database I've done this. In fact I'm using it on a current site
prototyping/testing new additions on a test version. This allows me to
customize the test store, show the client, etc and once all's working as
needed I move the adjustments to the main store.

The basic adjustments involved firstly adding a duplicate/new set of modules
for the new storefront. Then add a new renamed copy of the main index.php
file, e.g. teststore.php, which has this adjustment to the module path:

    define("EXTERNAL_PATH", dirname($SCRIPT_NAME) . "/");
    define("MODULE_PATH", (APPLICATION_ROOT . "teststore-modules"));

    /*
    ** get global settings
    */
    include(MODULE_PATH . "/include/global_settings"); ....etc, etc...

Then I added a global store ID in global settings, e.g.

    //Set shop ID to be included in invoice, etc.
    define("STORE_ID", "Teststore");

Next, I added a StoreID field to tables I thought I needed to track which
store made the entry. e.g.

    invoice
    invoice_sku
    session_sku
    user
    user_sku
    (I may need to do more but for now this is enough to show in
dump_invoice which store made the sale, etc.)

These changes then need to be reflected in any database queries which is the
longest part of the job. Then update dump_invoice.php to reflect the new
info.

This is not complete, for example you'd need to do a lot more if you wanted
different product ranges in each store, but that's a job for later!

The advantage for prototyping is that the client can easily see how new
additions would work in the same environment as the active store.

Hope it helps, I'd suggest it's worth setting it up if only for the reason
above.

Good luck,

Nick

----------------------
Lab2 Design-Unit
URL: www.lab2.com.au
e-mail: [EMAIL PROTECTED]
----------------------¢Ë�±Êâmçëyëkiר�X¬·
+�)àv�,r��¢éì¹»®&Þ~·�¶¶�z�ß�+-Â�ä�x¢¢d¢µèm¶�ÿÃ
+0¢¹"�h�Ç(�÷ëyëki׿>º�é¬��ð¢¹"�h�Ç(

Reply via email to