One of the many benefits of the upgrade to vBulletin 4 is that it gives us this shiny blog system. However because it is nice and shiny, for now we are keeping it all to ourselves.
It may be in the future we open up the system more to our user base, but for now, you will just have to put up with the ramblings of the Zen Cart development team.
Generally we hope to Blog about stuff that would not normally be relevant within the Forum context. Some stuff about PA-DSS,
Storeowner wants to send the customer an email with a unique code when the customer creates an account.The code pattern is "ABC00001", where ABC is fixed text, and 00001 is the customer number, with leading zeros up to exactly 5 digits.There is no need to build a database of already-issued codes, since the customer ID number is already unique per customer.The store is using v1.5.0 code.
The thinking and coding process:
First, since this must
TL;DR / Executive Summary:
Are you looking for a quick way to understand best practices when upgrading your Zen Cart site? The easiest way to view it is as "a rebuild while keeping all the existing data."
This article contains 3 sections:
1. What an upgrade is, and what it is not.
2. An overview of how to rebuild a site using the new version, instead of upgrading.
3. How to upgrade while keeping the store live, and not losing any sales/customer/product
When PHP 5.3 was released, some older features were retired (some removed, some "deprecated", etc).
And if your custom code or your addons/plugins are using those features, things will break and you'll encounter the dreaded "white screen of death".
What do you need to change?
Here's the list I generally follow, along with how I usually remedy it:
ereg('searchtext', 'a_string', $optionalVar) becomes preg_match('/searchtext/