ajax error during checkout

[earth-friendly]

I am in the process of upgrading from 1.5.3 to 1.5.4. I started with a clean install of 1.5.4, and then added a number of mods that I had been using previously. I got the latest version available of each mod.
My server uses php version 5.4.45 and MySQL 5.5.45-cll.
I am currently running the upgraded version on my test site, which is a subdomain of my regular site.
www.test.xxxxx.com
I have the beta version of COWOA installed, although I don't know if that is related to my issue.
I put something in my cart, login, and begin the checkout process.
I get to the checkout_shipping page, then click "continue checkout" to get to the checkout_payment page.
I choose "Cash on Delivery", and click "continue checkout".
The screen briefly flashes with an ajax error, and then goes to the "checkout_confirmation" page. I was able to do a screenshot, to see what the error is.
The error is: An unknown response null::null:: was received while processing an ajax call. The action you requested could not be completed.

My concern is that I don't want this error showing up on my live site, when I switch over.
Is there any way for me to debug this error, and figure out why it is showing up? Also, is there any explanation of how ajax is used in the checkout process? I'm not familiar with it.
I temporarily turned off ssl in the configure.php file, and then the error does not show up.
I was getting some other ajax errors before, related to having a subdomain, but I was able to fix them by always using www.test.xxxxx.com, instead of test.xxxxx.com, both in the configure.php files, and in a rewrite rule in the .htaccess file.
It might be the case that this problem is caused by the subdomain, but I don't want to take the chance that it will persist on the live site.
Thanks in advance for any help with this!

[kobra]

I am currently running the upgraded version on my test site, which is a subdomain of my regular site

I temporarily turned off ssl in the configure.php file, and then the error does not show up.

The subdomain is not serviced by the SSL Certificate that you may have and most likely why when you have ssl on in the subdomain you are seeing the error

Check your install /logs folder for any debug files

[carlwhat]

debugging ajax can be confusing...

i would look at developer tools for your browser and then the console tab...

good luck.

[earth-friendly]

The subdomain is not serviced by the SSL Certificate that you may have and most likely why when you have ssl on in the subdomain you are seeing the error

Check your install /logs folder for any debug files

Hi Kobra. Thanks for your comments and suggestions!
My webhost company generated a self-signed SSL certificate for my subdomain, test.XXXXX.com, a while ago, so that I would be able to test the checkout and admin portions of my website before doing an upgrade. I have added an exception for it to my browser, so that things do work pretty well. But it's possible that the error is related to the subdomain and ssl.

I have checked the logs directory, and no debug files are being generated for this error.

[earth-friendly]

debugging ajax can be confusing...

i would look at developer tools for your browser and then the console tab...

good luck.

Hi Carlwhat. Thanks for your suggestions!
I followed what you suggested, and in Firefox, I went to Developer Tools -> Console tab.
I generated the error, and this is the contents of the Console tab:

Object { readyState: 0, getResponseHeader: .ajax/v.getResponseHeader(), getAllResponseHeaders: .ajax/v.getAllResponseHeaders(), setRequestHeader: .ajax/v.setRequestHeader(), overrideMimeType: .ajax/v.overrideMimeType(), statusCode: .ajax/v.statusCode(), abort: .ajax/v.abort(), state: .Deferred/d.state(), always: .Deferred/d.always(), then: .Deferred/d.then(), 11 more… }

I clicked on the js sub-tab, and I see:

uncaught exception: out of memory

I clicked on security, and I see the following warning, which presumably is because of the self-signed SSL certificate:

This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.

I've never dealt with ajax before, and I'm not sure what to look for, or how to debug this error. Any suggestions? Or should I just hope that it goes away when I switch to my real domain?

Thanks again for any help with this!

[lat9]

There have been a couple of reports of the ajax-handling throwing that message. @earth-friendly: How have you got your subdomain site configured? If you could post the contents of your /includes/configure.php, perhaps that will shed some light.

When posting that file, use the CODE tags (the # in the right-hand side of the toolbar that's displayed when you're writing your post) and make sure to xxx-out your database credentials and (possibly) the site's URL).

[earth-friendly]

Hi lat9.

Here is my configure.php file (with all the real info renamed):

define('HTTP_SERVER', 'http://www.test.mydomain.com');
define('HTTPS_SERVER', 'https://www.test.mydomain.com');
define('ENABLE_SSL', 'true');

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/');
define('DIR_WS_PHPBB', '/');

define('DIR_FS_CATALOG', '/home/mydir/MyTest/');
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('DB_TYPE', 'mysql');
define('DB_PREFIX', '');
define('DB_CHARSET', 'utf8');
define('DB_SERVER', 'localhost');
define('DB_SERVER_USERNAME', 'dbname');
define('DB_SERVER_PASSWORD', 'dbpass');
define('DB_DATABASE', 'zendb');
define('USE_PCONNECT', 'false');
define('STORE_SESSIONS', 'db');

define('SQL_CACHE_METHOD', 'none');
define('DIR_FS_SQL_CACHE', '/home/mydir/MyTest/cache');

And I also have a rewrite rule in my .htaccess file, to always include the "www". Before I made sure to include the "www", in both the .htaccess file and the configure.php, I got additional ajax errors when I tried to use the admin.
Here is the .htaccess rule:

RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]

[kobra]

If you are running v1.5.4 then you are missing some important information
How did you upgrade??
Info in red missing

  define('HTTP_SERVER', 'http://domain.com');
  define('HTTPS_SERVER', 'https://domain.com');

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

  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', '/home/user/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/user/public_html/logs');

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

[earth-friendly]

Hi kobra. Thanks very much for pointing that out.
I have added the following to both of my configure.php files:

define('DIR_FS_LOGS', DIR_FS_CATALOG . 'logs');

I think that is correct, because DIR_FS_CATALOG has a trailing slash, and the comments say that DIR_FS_LOGS should not have a trailing slash.

In answer to your question about how did I upgrade:
I started with a clean version of 1.5.4.
I added in my template files (I did some merging between the default template files, but not in all cases.)
I added a number of addons that I had been using before.
I copied over my previous configure.php files.
I uploaded the new files to my fileserver, and pointed my development website to this location.
I ran the upgrade scripts.
The trickiest part was dealing with my existing template files. I had gotten them from a previous company that was hosting my website. They had included a bunch of addons into their zencart version, so some of this was embedded in the template files. But, I had worked hard on the template files, getting everything styled the way I wanted it, so I didn't start over with a clean set of template files, and I didn't have access to a clean set of the same template files. So I did the best I could to remove all the addons from the template files initially, to start cleanly before adding any of the addons.

Anyway, that is the long, painful process I went through. Does it sound reasonable, or did I miss something? I'm guessing that at some point, DIR_FS_LOGS was added to the configure.php files, and I never got those into my configure.php files until now.

[kobra]

I copied over my previous configure.php files.

This explains why you did not have up to date configure's

I have added the following to both of my configure.php files:

define('DIR_FS_LOGS', DIR_FS_CATALOG . 'logs');

This should be a full path to the logs directory

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