upgrade put off long enough

[stitchnkitty]

Ok I got that we can not mess with the original site - great thought!
And Smart!

still stuck on the files comparison section thought -kobra is there a place I can read about my database question in my last post?

I know that has to be a loaded Q? cuz it is so complex but just the general concept would be good.

I will reread the tutorial and be back with my next 'upgrade for dummies' question LOL!

Thanks!!

[DrByte]

The concept of the database is also elusive - The database is a table that contains the important information of the products of each site? Yes?

Maybe. It really depends on what *you* think a "table" is, and that may just be a nomenclature thing.

The database is a collection of tables. Tables are like spreadsheets, storing data in rows and columns, related to whatever the structure of that table is for. For customers, it means email addresses, passwords, etc. For address books, it means all the address info for each customer. For orders, all the order details. For products, the details of each aspect of each product. And so on.
I guess you could look at a database as a multi-sheet spreadsheet, but way more optimized and efficient in how it automatically handles indexing and storage/retrieval.
A database is not stored in any files that are directly accessible to you as a storeowner. Instead, you access it via phpMyAdmin or similar tools, and query (request) data from the database according to what you wish to read from it.
In the case of taking a backup, you're exporting the entire database content into one great big file that can be used for offline storage, or restoring if needed. That's the only way *you* will ever see the database as "a file".

(Aside: It *does* store everything in "files", but they're machine-code files, and meaningless to you unless you're a SQL and Server guru with super-advanced abilities to understand 0s and 1s with your eyes closed.)

When you say that you are installing the zencart into the database as opposed to attaching the database to the zencart?

TomAYto vs TomAHto?

When installing Zen Cart, you tell Zen Cart which database to store its data in. If you think of that as "attaching", I guess you're saying the same thing.
The only way Zen Cart is ever "attached" to a database is by the database details you give it, and those are stored in the configure.php files.

But you never tell a *database* which Zen Cart site to use. It doesn't work that way: It works the other way around.

So really no site may have more than one database and a database can not be shared by more than 1 site.

Well ... that's a technicality.

Generally speaking, a Zen Cart store only uses one database at a time.
Some (ie: most "good") hosting accounts allow multiple databases without additional fees. Some do not.

In the case of servers where only *one* database is allowed but multiple Zen Cart stores are setup in the same hosting account for different domains/sites, Zen Cart supports the use of "table prefixes" to differentiate between stores sharing that database.
It identifies the tables which it uses *within* that database by the DB_PREFIX setting. So, you could have "store1_" as a prefix to all the table-names for that store, and "zen_" as a prefix to the tables for another store, and so on. That's why the table-prefixes exist.

Some hosting companies have auto-installers that quickly dump a ZC site onto someone's account. Instead of setting up multiple databases, those usually engage the DB_PREFIX as "zen_" by default so they can keep the tables for the store separate from the tables they auto-install for a blog or a forum or a gallery or whatever.

How's that? Clear as mud?

[Ukulele]

Hi, thanks for the replies, still as baffled as ever.
So if its just a case of updating the files that have changed, then why cant you just upload the latest version to the 'demo' second testing bit.
Move the changes you made to customise the css which are all in renamed bit as instructed in the zen instructions on customisation.

Then test it (how I dont know, as havent a clue on how to direct to the demo bit and not the live shop) so will check on google (as I have been asking about but must be a huge secret as nobody seems to want to let go of the magic secret).

If I understand it correctly, the shop data, photos etc are all in the data base or in the images folders, which can be swaped over.

Checking all the files and uploading ones that have changed just seems a long way round, as just installing the latest version and adding the bits you changed in css bit seems to make more sense?

Or am I missing something important?

All I need is a working shop, and dont fancy making a mess of it.

[kobra]

Or am I missing something important?

Yes I believe so...

how I dont know, as havent a clue on how to direct to the demo bit and not the live shop

You are over thinking this I believe

Assuming that your live shop is at http:// the demo can/will be at http: //demo/

A COMPLETE second shop with it's own database

Just that simple

upload the latest version to the 'demo' second testing bit.
Move the changes you made to customise the css which are all in renamed bit as instructed in the zen instructions on customisation


Checking all the files and uploading ones that have changed just seems a long way round, as just installing the latest version and adding the bits you changed in css bit seems to make more sense?

It is not the long way it is the only way to insure that your upgrade is complete - - read on...

This is where one must COMPARE your customized file against the change log

IF and ONLY IF - you have customized a file that has a new/changed version, you MUST use the NEW VERSION and incorporate your customizations into this NEW file

Most will have only about 10-30 customized files to check, and of these maybe only a few will have new versions of the file

the shop data, photos etc are all in the data base or in the images folders, which can be swaped over.

Not sure of your interpretation of "swapped over" - - it should be duplicated in the /demo location

BOTTOMLINE - -

1. Use and install the new version with a new DB(all new version files)
2. Copy your images over
3. Make a list of your customized files
4. Check change log against this list
5. Note any of your files that have a new version
6. Incorporate your customizations into any of these files that have a new version
7. Copy all your custom template files to their respective locations
8. TEST - - TEST - - and you are done

Make your list of custom files - - -These are the ONLY ones that you might have to compare

[Ukulele]

Super thank you, that makes a lot more sense than all the other texts I have read, I only have about 6 files that were customised (like it says in the guide to name them /xxxx instead of /custom)

So feel a lot happier about having a go now.

We all have to learn somewhere and this makes sense of it all now.

Thank you again.

[stitchnkitty]

Dr Bytes - no actually that was extremely helpful and quite clear!!
TY so very much!

I have been working on the upgrade and actually it is quite a learning experience. Especially since my first install over a year ago was a bit trying. All the experts helped so very much and only a bit sunk in at that time. i mostly cookedbooked it! DU download corrupted a few of my files! I am on DSL now!

So this may take alot longer that most others but it will come!!

www.stitchnframeonline.com

www.stitchnframeonline.com/De##########cart

TY

[stitchnkitty]

The main intent of all of this is most have an operating shop
Doing the upgrade on a second install allows one to insure that all things are correct and functioning as expected without affecting their operating shop.

Which is a smart concept!

I have my shop almost done but I have not tested or finished uploading the images as of yet.BUT!

my second shop is located in public_html/windflowergrove

so I set up my demo for this shop as public_html/windflowerfrdemo so in order to get to my test shop for this one you need to:
www.stitchnframeonline.com/windflowergrdemo.

In My mind at the time of launching this site I was newbie thinking that all I needed to do was change the original site folder name to something else and the change the 'demo' folder to windflowergrove that of the original subsite.

Somehow I am seeing there may be problems with this concept???

[stitchnkitty]

Also this site is not acting as the primary site did and is causing a bit of trouble

www.stitchnframeonline.com/windflowergrdemo

the upper pic in the properties for that pic is:

http://www.stitchnframeonline.com/windflowergrdemo/
windflowergrdemo/includes/templates/stitch/images/wg3.jpg

which is weird since there is nothing on filezilla or the cpanel to indicate that there is a folder windflowergrdemo within a folder windflowergrdemo to come up with this path.

ideas?

[kobra]

Your view source base ref is

<base href="http://www.stitchnframeonline.com/windflowergrdemo/windflowergrdemo/" />

Mis entered something in your configure.php file

[stitchnkitty]

Just when I thought I had the logic from this!


// HTTP_SERVER is your Main webserver: eg-http://www.your_domain.com
// HTTPS_SERVER is your Secure webserver: eg-https://www.your_domain.com
define('HTTP_SERVER', 'http://www.stitchnframeonline.com/windflowergrdemo');
define('HTTPS_SERVER', 'https://www.stitchnframeonline.com/windflowergrdemo');

// Use secure webserver for checkout procedure?
define('ENABLE_SSL', 'false');

// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
// these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
define('DIR_WS_CATALOG', '/windflowergrdemo/');
define('DIR_WS_HTTPS_CATALOG', '/windflowergrdemo/');

define('DIR_WS_IMAGES', 'images/');
define('DIR_WS_INCLUDES', 'includes/');
define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');
define('DIR_WS_DOWNLOAD_PUBLIC', DIR_WS_CATALOG . 'pub/');
define('DIR_WS_TEMPLATES', DIR_WS_INCLUDES . 'templates/');

define('DIR_WS_PHPBB', '/');

// * DIR_FS_* = Filesystem directories (local/physical)
//the following path is a COMPLETE path to your Zen Cart files. eg: /var/www/vhost/accountname/public_html/store/
define('DIR_FS_CATALOG', '/home6/stitchnf/public_html/windflowergrdemo/');

define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');
define('DIR_WS_UPLOADS', DIR_WS_IMAGES . 'uploads/');
define('DIR_FS_UPLOADS', DIR_FS_CATALOG . DIR_WS_UPLOADS);
define('DIR_FS_EMAIL_TEMPLATES', DIR_FS_CATALOG . 'email/');

// define our database connection
define('DB_TYPE', 'mysql');
define('DB_PREFIX', '');
define('DB_SERVER', 'localhost');
define('DB_SERVER_USERNAME', 'xxxx');
define('DB_SERVER_PASSWORD', 'xxxxx');
define('DB_DATABASE', 'xxxxxx');
define('USE_PCONNECT', 'false');
define('STORE_SESSIONS', 'db');
// for STORE_SESSIONS, use 'db' for best support, or '' for file-based storage

// The next 2 "defines" are for SQL cache support.
// For SQL_CACHE_METHOD, you can select from: none, database, or file
// If you choose "file", then you need to set the DIR_FS_SQL_CACHE to a directory where your apache
// or webserver user has write privileges (chmod 666 or 777). We recommend using the "cache" folder inside the Zen Cart folder
// ie: /path/to/your/webspace/public_html/zen/cache -- leave no trailing slash
define('SQL_CACHE_METHOD', 'none');
define('DIR_FS_SQL_CACHE', '/aaaaa/ccccccc/public_html/windflowergrdemo/cache');

// EOF