QUOTE (Kaleb008 @ Aug 15 2007, 04:48 PM)
Matthew,
After going trought most of the steps to install this new contribution I get the following error once I turn on STS.
LayersMenu Error: setImgdir: /Program Files/Apache Group/Apache2/htdocs/shop/images/ is not a directory
My paths all seem correct in configure.php, and dm_header.php, any input would be appreciated
I assume your catalog folder is called 'shop' and
you are using oscommerce ms 2.2ms2-060817.normally when this happens all you need to do is tweek the defined DM_SETDIRROOT or the other variables, say images directory or DIR_WS_HTTP_CATALOG in the configure.php. Often this is caused by a missing forward slahs or a typo.
first make sure the images folder exists. this shouldnt have come up as the configure file should be written correctly through install.
put in the c: before the first forward slash in config and see what happens.
your config should look something like this:
/* --------------------------------------------------------------------------------------------------------------------- */
define('CATALOG_DIR_NAME', 'catalog'); // The folder in which osc has been installed.
/* --------------------------------------------------------------------------------------------------------------------- */
if (dirname($_SERVER['PHP_SELF']) == '/catalog'){
/* --------------------------------------------------------------------------------------------------------------------- */
define('DIR_WS_HTTP_CATALOG', '/catalog/' );
define('DIR_WS_HTTPS_CATALOG', '/catalog/' );
define('DIR_WS_IMAGES', 'images/' );
define('DIR_WS_INCLUDES', 'includes/' );
define('STYLESHEET', 'stylesheet.css' );
define('dmSTYLESHEET', 'bonkers_dynamenu.css' );
define('DM_SETDIRROOT', './' );
/* --------------------------------------------------------------------------------------------------------------------- */
}else{
/* --------------------------------------------------------------------------------------------------------------------- */
define('DIR_WS_HTTP_CATALOG', '/catalog' );
define('DIR_WS_HTTPS_CATALOG', '/catalog' );
define('DIR_WS_IMAGES', '/catalog/images/' );
// define('DIR_WS_INCLUDES', 'catalog/includes/' );
define('STYLESHEET', 'catalog/stylesheet.css' );
define('dmSTYLESHEET', 'catalog/bonkers_dynamenu.css' );
define('DM_SETDIRROOT', 'C:/Program Files/Apache Group/Apache2/htdocs/catalog' );
/* --------------------------------------------------------------------------------------------------------------------- */
}// end if-else
/* --------------------------------------------------------------------------------------------------------------------- */
define('DM_INCLUDES_FUNCTIONS', 'includes/functions/');
define('HTTP_SERVER', 'http://localhost'); // eg,
http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', ''); // eg,
https://localhost - should not be empty for productive servers
define('ENABLE_SSL', false); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', 'localhost');
define('HTTPS_COOKIE_DOMAIN', '');
define('HTTP_COOKIE_PATH', '/catalog/');
define('HTTPS_COOKIE_PATH', '');
// define('DIR_WS_HTTP_CATALOG', '/catalog/');
// define('DIR_WS_HTTPS_CATALOG', '');
// define('DIR_WS_IMAGES', 'images/');
define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
// 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_DOWNLOAD_PUBLIC', 'pub/');
define('DIR_FS_CATALOG', 'C:/Program Files/Apache Group/Apache2/htdocs/catalog/');
define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');
You could solve the confusion in those files by dynamically calling for the catalog folder name which is already defined in the core osCommerce code. OsCommerce is designed in such a way that once a variable is defined such as the catalog in configure.php, you can call for it in any file without having to manually add the catalog name every time you edit those files. Call for the defined catalog and then it will grab the correct one every time.