Ceon URI Mapping v4.x

[panservolvo]

I'm guessing that the issue stems from an incorrect path in your configure.php files.. which is to say that I don't think the issue stems from this module, but is ILLUMINATED when you turn this module on..

I don't think my config file is the problem?

// Define the webserver and path parameters
  // 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://madasahatter.no');
  define('HTTPS_SERVER', 'https://madasahatter.no');

  // Use secure webserver for checkout procedure?
  define('ENABLE_SSL', '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_CATALOG', '/');
  define('DIR_WS_HTTPS_CATALOG', '/');

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

[panservolvo]

Admin config file:

/**
 * WE RECOMMEND THAT YOU USE SSL PROTECTION FOR YOUR ENTIRE ADMIN:
 * To do that, make sure you use a "https:" URL for BOTH the HTTP_SERVER and HTTPS_SERVER entries:
 */
  define('HTTP_SERVER', 'https://madasahatter.no');
  define('HTTPS_SERVER', 'https://madasahatter.no');
  define('HTTP_CATALOG_SERVER', 'http://madasahatter.no');
  define('HTTPS_CATALOG_SERVER', 'https://madasahatter.no');

  // secure webserver for admin?  Valid choices are 'true' or 'false' (including quotes).
  define('ENABLE_SSL_ADMIN', 'true');

  // secure webserver for storefront?  Valid choices are 'true' or 'false' (including quotes).
  define('ENABLE_SSL_CATALOG', 'true');

  define('DIR_WS_ADMIN', preg_replace('#^' . str_replace('-', '\-', zen_parse_url(HTTP_SERVER, '/path')) . '#', '', dirname($_SERVER['SCRIPT_NAME'])) . '/');
  define('DIR_WS_CATALOG', '/');
  define('DIR_WS_HTTPS_ADMIN', preg_replace('#^' . str_replace('-', '\-', zen_parse_url(HTTPS_SERVER, '/path')) . '#', '', dirname($_SERVER['SCRIPT_NAME'])) . '/');
  define('DIR_WS_HTTPS_CATALOG', '/');

// 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_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)
  define('DIR_FS_ADMIN', preg_replace('#/includes/$#', '/', realpath(dirname(__FILE__) . '/../') . '/'));
  //the following path is a COMPLETE path to your Zen Cart files. eg: /var/www/vhost/accountname/public_html/store/
  define('DIR_FS_CATALOG', '/home/madasaha/public_html/');

  //the following path is a COMPLETE path to the /logs/ folder  eg: /var/www/vhost/accountname/public_html/store/logs ... and no trailing slash
  define('DIR_FS_LOGS', '/home/madasaha/public_html/logs');

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

[SignTorch]

looking at it in webmaster tools in msie and chrome, there is something wrong, causing almost all <head> content to appear in the <body> section, even though in view source it appears largely correct

so I'm guessing there's a syntax error or something causing that, and that the <base> tag being in the <body> might explain why msie doesn't seem to be using the designated <base> path with the relative image urls

EDIT - the <!doctype> isn't on the first line either - not sure if that matters

[SignTorch]

well <!doctype doesn't have to be on the first line

but I see something else in the javascript, single quotes are escaped inside double-quoted strings

onmouseover="showtrail(\'bmz_cache...

[panservolvo]

well <!doctype doesn't have to be on the first line

but I see something else in the javascript, single quotes are escaped inside double-quoted strings

onmouseover="showtrail(\'bmz_cache...

Where do you see this?
Good point on the header/body part also. I'll look into that later today

[lhungil]

looking at it in webmaster tools in msie and chrome, there is something wrong, causing almost all <head> content to appear in the <body> section, even though in view source it appears largely correct

so I'm guessing there's a syntax error or something causing that, and that the <base> tag being in the <body> might explain why msie doesn't seem to be using the designated <base> path with the relative image urls

EDIT - the <!doctype> isn't on the first line either - not sure if that matters

Most likely there is an issue with "/includes/templates/zenn/common/html_header.php". Possibly the upload was corrupted... But a more likely cause is: the file was opened with a text editor, edited, and not saved using UTF-8 without BOM (the without BOM is very important). If this issue is present in the theme files, one will want to review the character encoding used in all of the theme files ("/includes/templates/zenn/*"), in the define pages ("/includes/languages/<your_languages>/html_includes/*"), and any core Zen Cart files which have been modified.

One will need to use a text editor supporting UTF-8 without BOM (such as NotePad++ or one bundled with an IDE) to edit and save files with the correct character encoding.

This does not look like an issue with CEON URI Mapping. I did notice the theme is a commercial theme purchased from themeforest... If the OP needs additional help fixing the theme, I would recommend they contact the author of the theme for commercial support.

[DivaVocals]

Most likely there is an issue with "/includes/templates/zenn/common/html_header.php". Possibly the upload was corrupted... But a more likely cause is: the file was opened with a text editor, edited, and not saved using UTF-8 without BOM (the without BOM is very important). If this issue is present in the theme files, one will want to review the character encoding used in all of the theme files ("/includes/templates/zenn/*"), in the define pages ("/includes/languages/<your_languages>/html_includes/*"), and any core Zen Cart files which have been modified.

One will need to use a text editor supporting UTF-8 without BOM (such as NotePad++ or one bundled with an IDE) to edit and save files with the correct character encoding.

This does not look like an issue with CEON URI Mapping. I did notice the theme is a commercial theme purchased from themeforest... If the OP needs additional help fixing the theme, I would recommend they contact the author of the theme for commercial support.

and yet another reason why I DESPISE nearly anything coming from Theme Forest.. but this does go back to my original post.. the issue the OP has is not caused by this module, but it is certainly ILLUMINATED when this module is activated..

[panservolvo]

There must have been a file/several files with encoding errors or something like that. After I copied in a backup from last year the error is gone
Thanks for helping out guys!

[panservolvo]

Bonus information; the error was caused by the CEON back in stock notification module. I changed all the file encodings to utf-8 without dom and it fixed the problem

[DivaVocals]

Bonus information; the error was caused by the CEON back in stock notification module. I changed all the file encodings to utf-8 without dom and it fixed the problem

Which was likely caused by either a bad download or a contributor AFTER Conor who may have introduced the issue.. (otherwise many may more folks would have the same issue)