Dear Yankee99,
Sorry for the late answer and thank you for all your information. Unfortunately, I can't see any obvious causes of your issue. In particular, I see none of the known problems causing such issues. However, I don't know some of the plugins, so they might cause the issue.
I suppose you don't have a test/development installation where the issue occurs, only your live site?
The easiest way to track down the issue would be if you could temporarily enable debug logging in your WordPress installation and insert two lines of code into our plugin to print out a backtrace to a log file showing which functions / plugins called the number generation function of our plugin. All of this should not have any user-visible effect, but it will print out some vital information to a log file in your server.
If you don't want to enable debugging and fiddle with our plugin code, that's okay, too. We'll just have to figure another way to determine what or who is responsible that a number is skipped with every order.
To do it, there are the following two steps neccessary:
1. Enabling debug logging in WordPress: In the file wp-config.php change the line:
define('WP_DEBUG', false);to
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
2. In our plugin in the file wp-content/plugins/woocommerce-advanced-ordernumbers/ordernumbers_woocommerce_basic.php find the function
generateNumber (should be line 496) and insert two error_log calls right before the the "return $number;" in line 511:
error_log( "Creating new $type for order with ID $default, format=$fmt, resulting number=$number");
error_log('Backtrace = ' . print_r(debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS), true));
return $number;
In particular, change the function
function generateNumber($default, $order, $type='ordernumber') {
if ($this->numbers_activated($type)) {
$fmt = get_option ($type.'_format', "#");
$ctrsettings = array(
"${type}_format" => '',
"${type}_counter" => '',
"${type}_global" => get_option ($type.'_global', 'no'),
"${type}_padding" => 1,
"${type}_step" => 1,
"${type}_start" => 1,
);
$customvars = get_option ('ordernumber_variables', array());
$number = $this->helper->createNumber ($fmt, $type, $order, $customvars, $ctrsettings);
$this->update_order_meta($order, $this->ordernumber_meta.$type, $number );
return $number;
} else {
return $default;
}
}to
function generateNumber($default, $order, $type='ordernumber') {
if ($this->numbers_activated($type)) {
$fmt = get_option ($type.'_format', "#");
$ctrsettings = array(
"${type}_format" => '',
"${type}_counter" => '',
"${type}_global" => get_option ($type.'_global', 'no'),
"${type}_padding" => 1,
"${type}_step" => 1,
"${type}_start" => 1,
);
$customvars = get_option ('ordernumber_variables', array());
$number = $this->helper->createNumber ($fmt, $type, $order, $customvars, $ctrsettings);
$this->update_order_meta($order, $this->ordernumber_meta.$type, $number );
error_log( "Creating new $type for order with ID $default, format=$fmt, resulting number=$number");
error_log('Backtrace = ' . print_r(debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS), true));
return $number;
} else {
return $default;
}
}
The debug messages from the error_log call will not simply be written to the file wp-content/debug.log on your server.
3. Wait for one or two orders to come in skipping numbers. The file wp-content/debug.log will contain the information about which plugins and functions called the ordernumber generation. Could you please send me the file or its contents (via e-mail to office@open-tools.net), so I can see which plugin causes the issue.
4. Disable debug logging by reverting the changes done in step 1. and 2.
Best regards,
Reinhold
PS: If you are not comfortable modifying your installation's files, but are comfortable giving a complete stranger access (ftp and/or ssh access to your installation to modify the wp-config.php!), I can offer to make the adjustments myself.
VM Ordernumber Plugin 
Advanced Order Numbers for Magento 
Basic / Advanced Order Numbers for WooCommerce 
CB Usergroups Field Plugin 
