Define Pages Settings

[kaylala]

I recently upgraded my Zen Cart, and in the process I changed the structure of my website from having my online catalog only on the https url to now having it installed on both http and https. This information may or may not be a moot point, but here is my question:

How can you change the Define Pages settings to make changes to both the secure and non-secure sides of my online catalog?

Currently, changes made in my admin Define Pages Editor only show up on httpS://www.myurl.com

Any thoughts?

thanks,
Graham

[kuroi]

The answer, indeed the feasibility, of this is going to depend upon how your SSL cert works. Are you with one of those hosts that has it set up so that you need to have a copy of the pages that will be accessed under SSL in a separate location?

[kaylala]

Yes, I have two folders within my home folder: public_html and secure_html. I have a full copy of my online catalog in both.

[kuroi]

I don't know of an automated way to keep the two sets of code in sync, and Zen Cart can only edit one of the file at a time, you would then need to copy it to the other code set.

In practise you probably only actually need to change one of them, as a page will usually only be called under SSL or not. But I suspect that would involve remembering which for each page and then logging in to your Admin under the equivalent circumstances - a real hassle.

Personally I hate this type of hosting setup and would bite the bullet and switch to one that implements SSL on a single code set. The saving on ongoing hassle and overhead would far outweigh the one-off effort of moving.

[kaylala]

ah okay... I will keep that in mind. thanks!

[poolprorich]

Hello,
why could you not edit the configuration files from:
catolog side::

// Define the webserver and path parameters
  // HTTP_SERVER is your Main webserver: eg, http://www.yourdomain.com
  // HTTPS_SERVER is your Secure webserver: eg, https://www.yourdomain.com
  define('HTTP_SERVER', 'http://www.yourdomain.com');
  define('HTTPS_SERVER', 'https://www.yourdomain.com');

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

To this:

// Define the webserver and path parameters
  // HTTP_SERVER is your Main webserver: eg, http://www.yourdomain.com
  // HTTPS_SERVER is your Secure webserver: eg, https://www.yourdomain.com/ssl
  define('HTTP_SERVER', 'http://www.yourdomain.com');
  define('HTTPS_SERVER', 'https://www.yourdomain.com/ssl');

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

And ADMIN side from:

define('HTTP_SERVER', 'http://www.yourdomain.com');

  define('HTTPS_SERVER', 'https://www.yourdomain.com/ssl');

  define('HTTP_CATALOG_SERVER', 'http://www.yourdomain.com');

  define('HTTPS_CATALOG_SERVER', 'https://www.yourdomain.com/ssl');



  // Use secure webserver for catalog module and/or admin areas?

  define('ENABLE_SSL_CATALOG', 'true');

  define('ENABLE_SSL_ADMIN', 'true');



// 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_ADMIN', '/admin/');

  define('DIR_WS_CATALOG', '/');

  define('DIR_WS_HTTPS_ADMIN', '/ssl/admin/');

  define('DIR_WS_HTTPS_CATALOG', '/ssl/');



  define('DIR_WS_IMAGES', 'images/');

  define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

  define('DIR_WS_CATALOG_IMAGES', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'images/');

  define('DIR_WS_CATALOG_TEMPLATE', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'includes/templates/');

  define('DIR_WS_INCLUDES', 'includes/');

  define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

  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_CATALOG_LANGUAGES', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'includes/languages/');



// * 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_ADMIN', '/home/yourdomain/public_html/admin/');

  define('DIR_FS_CATALOG', '/home/yourdomain/public_html/');



  define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');

  define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');

  define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');

  define('DIR_FS_CATALOG_TEMPLATES', DIR_FS_CATALOG . 'includes/templates/');

  define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');

  define('DIR_FS_EMAIL_TEMPLATES', DIR_FS_CATALOG . 'email/');

  define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');



// define our database connection

To this:

define('HTTP_SERVER', 'http://www.yourdomain.com');

  define('HTTPS_SERVER', 'https://www.yourdomain.com/ssl');

  define('HTTP_CATALOG_SERVER', 'http://www.yourdomain.com');

  define('HTTPS_CATALOG_SERVER', 'https://www.yourdomain.com/ssl');



  // Use secure webserver for catalog module and/or admin areas?

  define('ENABLE_SSL_CATALOG', 'true');

  define('ENABLE_SSL_ADMIN', 'true');



// 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_ADMIN', '/admin/');

  define('DIR_WS_CATALOG', '/');

  define('DIR_WS_HTTPS_ADMIN', '/admin/ssl/');

  define('DIR_WS_HTTPS_CATALOG', '/ssl/');



  define('DIR_WS_IMAGES', 'images/');

  define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

  define('DIR_WS_CATALOG_IMAGES', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'images/');

  define('DIR_WS_CATALOG_TEMPLATE', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'includes/templates/');

  define('DIR_WS_INCLUDES', 'includes/');

  define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

  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_CATALOG_LANGUAGES', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'includes/languages/');



// * 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_ADMIN', '/home/yourdomain/public_html/admin/');

  define('DIR_FS_CATALOG', '/home/yourdomain/public_html/');



  define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');

  define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');

  define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');

  define('DIR_FS_CATALOG_TEMPLATES', DIR_FS_CATALOG . 'includes/templates/');

  define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');

  define('DIR_FS_EMAIL_TEMPLATES', DIR_FS_CATALOG . 'email/');

  define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');



// define our database connection

Dose this sound corect
it looks like it would work properly

Rich

[kuroi]

Dose this sound corect
it looks like it would work properly

Actually I don't think that this would work.

It would apply only to a very specific server configuration where the secure_html folder has been mapped to public_html/ssl (which may defeat the objective of keeping SSL-covered files our of the public files area) and is then broken by the define('DIR_WS_HTTPS_ADMIN', '/admin/ssl/'); statement which assumes instead that it has been mapped to public_html/admin/ssl.

In any case, it wouldn't deal with the need to keep duplicate copies of the code in public_html and secure_html, or the requirement to be able to log in to the Admin in both SSL and non-SSL modes to make changes to define pages in both code sets (which upon reflection the Zen Cart will probably not allow).

[poolprorich]

Hello,

That sounds corect but if i remember some hosts do have a copy of all files on both folders under public_html, what i dont understand is that i thought u cn view nonssl pages under ssl and if thats the case why have 2 setups in the first place.

Rich

[kuroi]

You're right. It would be possible to put the whole site under SSL, but there's a performance hit for the validation and encryption. Not so obvious for the relatively light pages usually covered by SSL, but could be problem for the heavier listings pages which would normally be nonSSL.