bsmither

Well, probably not by using PHP. To do so would require loading all records, sorting in memory, then slicing the result into pages. CubeCart has the database restrict its output to "slices". So, we need to figure out how to code the call to DB->select() to pass in the desired custom ordering, which is a bit tricky.

We can use PHP's natsort() function when wanting to sort an array using values such as you describe. (It will take me a while to develop code changes as I am not really set up yet to experiment.)

Ok, I see one category, one product. My next question is, do you have the store's address set at Australia?

At your site, which category should I be looking at to see the $20.00 shipping for that category?

Please try clearing CubeCart's cache (admin, Maintenance, Rebuild tab, Clear Cache). CubeCart reads the xml files, overwrites relevant keys found in the database, and caches the whole lot.

No. The file ini-custome.inc.php is used by CubeCart if it is present. A blank page could be a 500 Internal Server Error that trips caused by something in the .htaccess file or a sec_mod rule.

In the database table CubeCart_config, find the record 'config'. The value is base64 encoded. The utility phpMyAdmin will be able to decode it and show the results. Find the 'enableSSL' and change 'Yes' to 'No'. Then have phpMyAdmin base64 encode it back and save it. Your settings should now allow your site to operate in plain http.

Is it true that forcing your browser accept an invalid cert still won't let you get in to the admin?

When I visit your site, I get the same warning about the cert being self-signed. So, I forced my browser to re-fetch the page's resources, and that allowed me to get a fresh copy of your site's certificate. I see that it is a "Let's Encrypt" cert and it is a correct cert. However, some parts of the page are being requested are not using https. Instead, it seems the web server is often not sending the correct cert. The file /js/plugins.php took several tries to fetch it, until finally the web server sent the correct cert along with it. I have no experience debugging web server security cert issues, but hopefully my description of my experience with your site may prove useful in discussing the situation with your hosting provider.

In my opinion, the reason why a hosting provider gives you a SSL cert that is self-signed (and possibly using the hosts' domain name) is to provide you a means of testing any secure comms that need testing. In this fashion, you will need to instruct your browser to accept this otherwise mis-configured certificate. Click the Advanced button, then click the Add Exception button. On the pop-up, you should uncheck "Permanently store this exception", but click "Confirm security exception". Make your tests. When ready to go live, have your hosting provider assist you in installing your own legitimate certificate.

CC617 will put one back if it can't be found. The friendly seo path feature will not work without the code in the .htaccess file.

Migrated. Ok, so I think there may be something about the new environment. Your hosting provider should be able to suss out something.

You may need to get your hosting provider involved. If this just started, t may be the case that your hosting provider did something.

I see nothing wrong with this file - other than CC617 has a more up to date version.

Nope. Nothing here. That might mean something in the .htaccess file doesn't like a category URL. That's not likely, though, unless you have a bunch of redirect statements. The other likely reason is a problem has developed with a skin template. Sometimes, catching a Smarty error can be real tricky.

Create the error_log. See if anything interesting shows.

Separate.

CubeCart has no "schema verifier" (other than indexes at this point). Using that external utility, compare these columns and add/change any differences: `product_id` int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT 'Product ID', `status` tinyint(1) unsigned NOT NULL DEFAULT '1' COMMENT 'Status', `product_code` varchar(60) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'Product Code', `quantity` int(11) NOT NULL DEFAULT '1' COMMENT 'Quantity', `description` text COLLATE utf8_unicode_ci COMMENT 'Description', `description_short` text NULL COLLATE utf8_unicode_ci COMMENT 'Short Description', `price` decimal(16,2) NOT NULL DEFAULT '0.00' COMMENT 'Retail Price', `sale_price` decimal(16,2) DEFAULT '0.00' COMMENT 'Sale Price', `cost_price` decimal(16,2) NOT NULL DEFAULT '0.00' COMMENT 'Cost Price', `name` varchar(250) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'Product Name', `cat_id` int(10) unsigned DEFAULT '0' COMMENT 'Main Category ID', `popularity` int(10) unsigned DEFAULT '0' COMMENT 'Popularity', `stock_level` int(11) DEFAULT '0' COMMENT 'Main Stock Level', `stock_warning` int(10) unsigned NOT NULL DEFAULT '0' COMMENT 'Main Stock Warning level', `use_stock_level` tinyint(1) unsigned NOT NULL DEFAULT '1' COMMENT 'Use Stock Control', `digital` int(4) unsigned NOT NULL DEFAULT '0' COMMENT 'Is Digital?', `digital_path` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'Digital Path', `product_weight` decimal(10,3) DEFAULT NULL COMMENT 'Product Weight', `tax_type` int(10) unsigned DEFAULT NULL COMMENT 'Tax Type', `tax_inclusive` tinyint(1) unsigned DEFAULT '0' COMMENT 'Price inclusive of tax', `featured` tinyint(1) unsigned NOT NULL DEFAULT '1' COMMENT 'Featured product', `latest` tinyint(1) unsigned NOT NULL DEFAULT '1' COMMENT 'Included on Homepage', `seo_meta_title` text COLLATE utf8_unicode_ci NOT NULL COMMENT 'SEO Meta Title', `seo_meta_description` text COLLATE utf8_unicode_ci NOT NULL COMMENT 'SEO Meta Description', `seo_meta_keywords` text COLLATE utf8_unicode_ci NOT NULL COMMENT 'SEO Meta Keywords', `upc` varchar(20) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'UPC Code', `ean` varchar(20) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'EAN Code', `jan` varchar(20) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'JAN Code', `isbn` varchar(20) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'ISBN Code', `brand` varchar(20) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'Brand', `google_category` varchar(250) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'Google Cat', `gtin` varchar(20) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'GTIN Code', `mpn` varchar(20) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'MPN Code', `date_added` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT 'Date Added', `updated` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT 'Last Updated', `manufacturer` int(10) unsigned DEFAULT NULL COMMENT 'Manufacturer ID', `condition` varchar(25) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'Condition', `available` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `minimum_quantity` INT( 10) NOT NULL DEFAULT '0', PRIMARY KEY (`product_id`), KEY `status` (`status`), KEY `popularity` (`popularity`), FULLTEXT KEY `fulltext` (`product_code`,`description`,`name`)

The 'date_added' column was introduced in CC410. So, is this store an upgrade from a CC3/4 installation?

CC617 inventory table has 37 columns. Who knows what else has been missed. If this is a very fresh store, consider blowing away the database and re-installing.

Let's just make sure that 'date_added' is, in fact, a column in the CubeCart_inventory table for this store.

Using an external utility, view CubeCart_history table Note if any version has been skipped. The 'date_added' column is present in CC611 (which is as far back as my current situation allows to explore).

Unknown column 'date_added'. It seems the upgrade process failed to modify the CubeCart_inventory table when the step to have added the 'date_added' column would have happened. The 'date_added' column was added to make a distinction between when an item was added vs 'last_modified' (which, in previous versions of CubeCart, 'last_modified' put an item in Latest Products when it certainly wasn't a latest product).

In admin, Store Settings, Features tab, verify that for "Number of 'Latest Products' to display' there is a numeric value (using only digits) greater than zero. The error in the log suggests that the database query is returning something true-like, but it is not an array, and cannot be used as an argument for the foreach() statement. The first place to test is the number of records to return from config. You can also enable CubeCart's debug mode and provide your IP address in the adjacent field (www.whatismyip.com). Then, when viewing the Latest Products, the debug section will show any queries that the database engine had a problem with.

What you re saying is that the Cart Order Number starts with 1603XX- ?