Hello, this plugin has not been updated for a very long time (almost a year). When is a version update scheduled ? It’s going to cause problems with security software if this takes a little longer.
]]>Is this dead? Export doesn’t work on fully updated site
]]>Hi!
i used Cart2Cart to import orders from Shopify to WooCommerce but it all got messed up and it uses your plugin and that might not even be related to my question but just informing if it is.
But when i search for a order in the WooCommerce app no orders are found because of the changed order numbers that start att 34500.
Is this a know problem?
]]>Before purchase we need to know if this plugin is compatible with Mailchimp for Woocommerce plugin?
]]>We switched to the new block based checkout in woocommerce, ref https://woo.com/checkout-blocks/
But now the sequential order numbering does not work anymore. Now it uses the ID for new orders. And we get below warnings on checkout page.
I have tried switching back and forth between the new block-based checkout and the old one. Works fine with sequential order numbering in old checkout but not the new one.
Warning: Object of class Automattic\WooCommerce\Admin\Overrides\Order could not be converted to int in /wp-content/plugins/woocommerce-sequential-order-numbers/woocommerce-sequential-order-numbers.php on line 316
Warning: Object of class Automattic\WooCommerce\Admin\Overrides\Order could not be converted to int in /wp-content/plugins/woocommerce-sequential-order-numbers/woocommerce-sequential-order-numbers.php on line 318
]]>Does this plugin use the WooCommerce Legacy REST API?
I have WooCommerce log files linked to only to “Orders” making this plugin a logical reason for these files being generated.
Examples
2024-02-22T00:00:58+00:00 INFO Version: 2, Route: /orders, User agent: Other
2024-02-22T00:00:59+00:00 INFO Version: 2, Route: /products/33276, User agent: Other
2024-02-22T00:01:00+00:00 INFO Version: 2, Route: /products/33276, User agent: Other
2024-02-22T00:01:00+00:00 INFO Version: 2, Route: /orders, User agent: Other
Thanks in advance
]]>Hi, for some reason the plugin wasn’t working before with the custom numbering but after we recently updated the plugin to the newest version, the new numbering sequence kicked in again.
If we de-activate the plugin, would we lose the current numbering sequence or will WooCommerce just keep incrementing +1 itself based on the most recent order?
2nd question. Our orders jumped to 600,000 from 450,000 when the plugin was updated yesterday. If we set the order numbers back to 450,000, in the future will WooCommerce detect that 600,xxx was used before and then skip those order numbers?
If I create an order manually in the admin area, when the emails that woocommerce sends go out to admin and the customer, debugging shows that the order number isn’t available yet, so the emails show the order ID.
The sequential order number is created/applied when I look at the order in the list of orders.
The sequential order number is created/applied/displayed in orders that are created through the normal checkout process.
This has only started happening since the last plugin update.
How can we fix this?
]]>Since your latest plugin upgrade, all subscription renewal orders are automatically being changed to completed instead of processing. The products are physical and we’ve plugin conflict tested the whole site to confirm that the issue really is with your plugin.
When we roll back the plugin version to 1.9.7 the issue is gone. WooCommerce’s Happiness Engineer have confirmed that this issue only occurs on your free version, not on the paid Pro version.
]]>Adding a manual order using “ad new” in woocommerce give a completely different sequence of numbers.
It should be one sequence for all orders. How to get this working properly?
Good morning, with reference to last week’s post by @websonica, I can add that the pattern we observed is related to the fact that in the post_meta table, concerning an order, two records are added with the same post_id, the same meta_key, which takes the value ‘_order_number’, and two sequential values of meta_value. It’s possible that some orders may have been deleted in the past, but this change in behavior is relatively recent.
Thanks.
]]>Hello, we are experiencing an issue with the order numbering. Specifically, we have noticed gaps between consecutive orders. When looking into the database and performing an inner join between the “posts” and “postmeta” tables, we found two “meta_key” entries with the value “_order_number,” both containing two consecutive numbers. Can you please help us resolve this?
]]>When i am install your plugin it will be showing this error. Fatal error: Uncaught Error: Call to a member function get_data() on bool in
i am checking code and find out, there is a problem with get_data() function. and it’s default function so May i suggest default woocomerce function always be working do not close default functionality. Now can you please help me out of my code which i am shared below
i am using this code,
$getOrderproductmname = wc_get_order($dhl_order_id);
$getOrderproductdata = $getOrderproductmname->get_data();
and i have facing error like this, Fatal error: Uncaught Error: Call to a member function get_data() on bool in
So how can i solve this problem can you please help me!!!
]]>Hi guys,
I want to migrate to HPOS in the near future to speed up our WooCommerce installation.
According to the?/wordpress/wp-admin/plugins.php?plugin_status=incompatible_with_feature&feature_id=custom_order_tables?page, your plugin doesn’t support?HPOS. When do you plan to support it?
]]>This plugin is not yet compatible with PHP 8.1. Are there any plans to fix this in the near future?
]]>Hi. I’ve been using the plugin since the beginning of running the store. Unfortunately, since January, the plugin has started to number orders only in even numbers. The plugin skips odd numbers. Please help me urgently to solve this problem.
]]>Hi, I have a problem on the store that after updating WooCommerce to the latest version, orders are only numbered evenly. How can I fix it? Thank you for your help.
]]>Hi guys!
Can I create prefix for order numbering depenging from order language?
E.g. I have 3 languages – DE, FR, IT and all products have a translation in Woocommerce with Polylang.
When ordering DE products I want to use order numbering with mask- 1xxxx
For FR – 2xxxx
For IT – 3xxxx
All order numbers will start from unuque digit depending from language code (maybe ID of language)
]]>Hi guys
I tried this & many other sequential order id plugins but dont seem to work. Issue is we had some issues during migration that made order numbers extra long for example #9004111222073999
We want to reset the next order id to go back to 5 o t 6 characters. Is this possible with your plugin?
John
]]>The prefix has disappeared and the order number has changed. For Random 6 orders, the prefix disappeared and completely different order numbers started to be generated by Woocommerce or the Sequential Order Number plugin. Then it went back to “regular” numbering. What could be causing the problem?
Thanks,
]]>Hey I’m creating an order programmatically wc_create_order(); and i need to use the Sequential Order Numbers as _order_number and not the post_id. Is that possible?
]]>I need the order number in email be the same as appears in admin panel, how can Achieve this?
this is the system report:
### WordPress Environment ###
WordPress address (URL): https://uniformesydotacionesjrb.com
Site address (URL): https://uniformesydotacionesjrb.com
WC Version: 6.6.1
REST API Version: ? 6.6.1
WC Blocks Version: ? 7.6.2
Action Scheduler Version: ? 3.4.0
Log Directory Writable: ?
WP Version: 6.0
WP Multisite: –
WP Memory Limit: 256 MB
WP Debug Mode: –
WP Cron: ?
Language: es_ES
External object cache: ?
### Server Environment ###
Server Info: LiteSpeed
PHP Version: 8.0.19
PHP Post Max Size: 64 MB
PHP Time Limit: 360
PHP Max Input Vars: 1000
cURL Version: 7.68.0
OpenSSL/1.1.1f
SUHOSIN Installed: –
MySQL Version: 10.6.7-MariaDB-1:10.6.7+maria~focal
Max Upload Size: 64 MB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?
### Database ###
WC Database Version: 6.6.1
WC Database Prefix: wp_
Tama?o total de la base de datos: 16.31MB
Tama?o de los datos de la base de datos: 9.53MB
Tama?o del índice de la base de datos: 6.78MB
wp_woocommerce_sessions: Datos: 0.05MB + índice: 0.02MB + Motor InnoDB
wp_woocommerce_api_keys: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_woocommerce_attribute_taxonomies: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_woocommerce_downloadable_product_permissions: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB
wp_woocommerce_order_items: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_woocommerce_order_itemmeta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_woocommerce_tax_rates: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB
wp_woocommerce_tax_rate_locations: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_woocommerce_shipping_zones: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_woocommerce_shipping_zone_locations: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_woocommerce_shipping_zone_methods: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_woocommerce_payment_tokens: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_woocommerce_payment_tokenmeta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_woocommerce_log: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_actionscheduler_actions: Datos: 0.41MB + índice: 0.59MB + Motor InnoDB
wp_actionscheduler_claims: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_actionscheduler_groups: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_actionscheduler_logs: Datos: 0.31MB + índice: 0.25MB + Motor InnoDB
wp_commentmeta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_comments: Datos: 0.02MB + índice: 0.09MB + Motor InnoDB
wp_fsmpt_email_logs: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_gla_budget_recommendations: Datos: 0.22MB + índice: 0.14MB + Motor InnoDB
wp_gla_merchant_issues: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_gla_shipping_rates: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_gla_shipping_times: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_links: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_litespeed_url: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_litespeed_url_file: Datos: 0.02MB + índice: 0.08MB + Motor InnoDB
wp_mailpoet_custom_fields: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_dynamic_segment_filters: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_feature_flags: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_forms: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_mailpoet_log: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_mailpoet_mapping_to_external_entities: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_newsletters: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_newsletter_links: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_mailpoet_newsletter_option: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_newsletter_option_fields: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_newsletter_posts: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_newsletter_segment: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_newsletter_templates: Datos: 2.52MB + índice: 0.00MB + Motor InnoDB
wp_mailpoet_scheduled_tasks: Datos: 0.06MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_scheduled_task_subscribers: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_segments: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_sending_queues: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_settings: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_statistics_bounces: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_mailpoet_statistics_clicks: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_mailpoet_statistics_forms: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_statistics_newsletters: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_statistics_opens: Datos: 0.02MB + índice: 0.08MB + Motor InnoDB
wp_mailpoet_statistics_unsubscribes: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_mailpoet_statistics_woocommerce_purchases: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB
wp_mailpoet_stats_notifications: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_subscribers: Datos: 0.02MB + índice: 0.13MB + Motor InnoDB
wp_mailpoet_subscriber_custom_field: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_subscriber_ips: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_subscriber_segment: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_user_agents: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_user_flags: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_options: Datos: 2.44MB + índice: 0.20MB + Motor InnoDB
wp_postmeta: Datos: 1.52MB + índice: 3.03MB + Motor InnoDB
wp_posts: Datos: 0.22MB + índice: 0.16MB + Motor InnoDB
wp_termmeta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_terms: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_term_relationships: Datos: 0.05MB + índice: 0.05MB + Motor InnoDB
wp_term_taxonomy: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_usermeta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_users: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_wc_admin_notes: Datos: 0.06MB + índice: 0.00MB + Motor InnoDB
wp_wc_admin_note_actions: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wc_category_lookup: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wc_customer_lookup: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_wc_download_log: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_wc_order_coupon_lookup: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_wc_order_product_lookup: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB
wp_wc_order_stats: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_wc_order_tax_lookup: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_wc_point_of_sale_sale_reports: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wp_wc_pos_grid_tiles: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wc_product_attributes_lookup: Datos: 0.06MB + índice: 0.05MB + Motor InnoDB
wp_wc_product_download_directories: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wc_product_meta_lookup: Datos: 0.09MB + índice: 0.13MB + Motor InnoDB
wp_wc_rate_limits: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wc_reserved_stock: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wc_tax_rate_classes: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wc_webhooks: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wpforms_tasks_meta: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wpmailsmtp_debug_events: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wpmailsmtp_tasks_meta: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
### Post Type Counts ###
attachment: 2
mailpoet_page: 1
page: 7
pos_grid: 1
pos_outlet: 1
pos_receipt: 1
pos_register: 2
pos_session: 15
pos_temp_order: 2
product: 69
product_variation: 612
revision: 11
shop_order: 8
wp_global_styles: 1
### Security ###
Secure connection (HTTPS): ?
Hide errors from visitors: ?
### Active Plugins (22) ###
All-in-One WP Migration Unlimited Extension: por ServMask – 2.36
All-in-One WP Migration: por ServMask – 7.61
Google Listings and Ads: por WooCommerce – 1.13.5
Jetpack: por Automattic – 11.0
Salient WPBakery Page Builder: por Michael M - WPBakery.com | Modified by ThemeNectar – 6.7.1
LiteSpeed Cache: por LiteSpeed Technologies – 4.6
MailPoet 3 (New): por MailPoet – 3.90.1
Salient Core: por ThemeNectar – 1.9.4
Salient Demo Importer: por ThemeNectar – 1.4
Salient Home Slider: por ThemeNectar – 1.4.1
Salient Nectar Slider: por ThemeNectar – 1.7.2
Salient Portfolio: por ThemeNectar – 1.7.1
Salient Shortcodes: por ThemeNectar – 1.5
Salient Social: por ThemeNectar – 1.2.2
Salient Widgets: por ThemeNectar – 1.3
Preview E-mails for WooCommerce: por Digamber Pradhan – 2.0.2
WooCommerce Stripe Gateway: por WooCommerce – 6.4.1
Point of Sale for WooCommerce: por Actuality Extensions – 5.5.4
WooCommerce Sequential Order Numbers: por SkyVerge – 1.9.6
WooCommerce: por Automattic – 6.6.1
WP Mail SMTP: por WPForms – 3.4.0
WPForms Lite: por WPForms – 1.7.4.2
### Inactive Plugins (4) ###
Akismet Anti-Spam: por Automattic – 4.2.4
Bayna - Deposits & Partial Payments for WooCommerce: por Codeixer – 1.2.3
Google Analytics for WordPress by MonsterInsights: por MonsterInsights – 8.6.0
Hello Dolly: por Matt Mullenweg – 1.7.2
### Dropin Plugins (1) ###
object-cache.php: object-cache.php
### Settings ###
API Enabled: –
Force SSL: –
Currency: COP ($)
Currency Position: left_space
Thousand Separator: .
Decimal Separator: ,
Number of Decimals: 0
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)
Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)
Connected to WooCommerce.com: ?
Enforce Approved Product Download Directories: –
### WC Pages ###
Base de la tienda: #7 - /tienda/
Carrito: ? La visibilidad de la página debe ser pública
Finalizar compra: #9 - /finalizar-compra/
Mi cuenta: #10 - /mi-cuenta/
Términos y condiciones: ? Página sin definir
### Theme ###
Name: Salient
Version: 14.0.5
Author URL: https://themeforest.net/user/themenectar
Child Theme: ? – Si estás modificando WooCommerce en un tema padre que no has creado personalmente
te recomendamos utilizar un tema hijo. Ver: Cómo crear un tema hijo
WooCommerce Support: ?
### Templates ###
Overrides: salient/woocommerce/cart/mini-cart.php
salient/woocommerce/checkout/form-checkout.php
salient/woocommerce/checkout/review-order.php
salient/woocommerce/checkout/terms.php
salient/woocommerce/content-product.php
salient/woocommerce/content-single-product.php
salient/woocommerce/loop/add-to-cart.php
salient/woocommerce/loop/loop-start.php
salient/woocommerce/myaccount/form-login.php
salient/woocommerce/single-product/product-image.php
salient/woocommerce/single-product/rating.php
salient/woocommerce/single-product/tabs/description.php
salient/woocommerce/single-product/tabs/tabs.php
salient/woocommerce/single-product/title.php
salient/woocommerce/single-product-reviews.php
### Admin ###
Enabled Features: activity-panels
analytics
coupons
customer-effort-score-tracks
experimental-products-task
experimental-import-products-task
experimental-fashion-sample-products
homescreen
marketing
mobile-app-banner
navigation
onboarding
onboarding-tasks
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
shipping-label-banner
subscriptions
store-alerts
transient-notices
wc-pay-promotion
wc-pay-welcome-page
wc-pay-subscriptions-page
Disabled Features: minified-js
settings
Daily Cron: ? Next scheduled: 2022-06-23 00:06:20 -05:00
Options: ?
Notes: 59
Onboarding: completed
### Action Scheduler ###
Completo: 1.576
Oldest: 2022-06-17 17:24:02 +0000
Newest: 2022-06-22 21:18:13 +0000
Pendiente: 10
Oldest: 2022-06-23 00:06:12 +0000
Newest: 2022-06-27 19:01:42 +0000
### Status report information ###
Generated at: 2022-06-22 16:36:24 -05:00
]]>
I am currently using the sequential order number plugin on a site I developed. Everything has been working great until recently. I have a snippet in my code that looks like this:
$order = wc_get_order($arrayItem[0]) // $arrayItem[0] is my Order ID
$order->add_order_note($noteContents);
$order->update_status(‘completed’);
$order->save();
Again, I had no issues with this code until recently, but now whenever I try to update a status programatically (using update_status() ), the order NUMBER changes for whichever order had its status updated. I tried also using the “new WC_Order” method to get my order object to see if this would make a difference, but it did not.
There must be a way to achieve updating the status programatically without affecting the order number, but I could use some help narrowing down the solution. Any help is much appreciated and please let me know if any further information might be needed to resolve my issue.
Thank you!
]]>When viewing the orders for an event the order number is showing as “0”. When clicking the link to the order it takes me to /wp-admin/post.php?post=wc-13809-04202207&action=edit
which ends up redirecting back to the Posts lists (/wp-admin/edit.php)
When I deactivate this plugin then the order numbers populate correctly.
Plugin deactivated: https://ibb.co/3yvwB89
Plugin activated: https://ibb.co/3cSyfMN
WP Version: 5.9.3
Woocommerce Version: 6.3.1 (this has been an issue since 5.9.x)
WooCommerce Sequential Order Numbers Pro: 1.18.0
I have a situation that started recently, and by elimination of causes, WooCommerce Sequential Order Numbers is the cause.
So far it happened a few times and without any specific conditions.
New order gets inserted in the base with a hashtag in front (and in the base, it should only be a number, not with a hashtag). And in the orders (in WooCommerce) the order is shown with 2 # in front of the order number.
It should not be happening, WooCommerce does not produce the # in the base, so it has to be the plugin.
]]>Despite previous answer saying the plugin is kept up to date (no update for 2 years, even to confirm compatibility and keep people’s mind’s at rest – really?) it would appear to not be compatible now.
Constant PHP message since updating WooCommerce:
The is_ajax function is deprecated since version 6.1.0. Replace with wp_doing_ajax.
Which seems to originate from this plugin. As this is appears to be a plugin ‘validated’ by WooCommerce themselves, how has it not been updated? Is the Pro version also outdated?
Will look to implement another solution now, but please do keep on top of developments with WooCommerce if you develop plugins for it. After 2 years you should really have confirmed it’s still compatible or not by updating version numbers. COuld you give a time frame for fixing this?
Or if you have any other input please let me know.
]]>After update Woocommerce to latest version i got error (log file):
[31-Oct-2021 22:57:24 UTC] PHP Fatal error: Uncaught Error: Call to undefined function is_ajax() in /DISK3/www/5461/www/wp-content/plugins/woocommerce-sequential-order-numbers/woocommerce-sequential-order-numbers.php:466
Stack trace:
#0 /DISK3/www/5461/www/wp-content/plugins/woocommerce-sequential-order-numbers/woocommerce-sequential-order-numbers.php(92): WC_Seq_Order_Number->minimum_wc_version_met()
#1 /DISK3/www/5461/www/wp-includes/class-wp-hook.php(303): WC_Seq_Order_Number->initialize()
#2 /DISK3/www/5461/www/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters()
#3 /DISK3/www/5461/www/wp-includes/plugin.php(470): WP_Hook->do_action()
#4 /DISK3/www/5461/www/wp-settings.php(441): do_action()
#5 /DISK3/www/5461/www/wp-config.php(98): require_once('/DISK3/www/5461...')
#6 /DISK3/www/5461/www/wp-load.php(50): require_once('/DISK3/www/5461...')
#7 /DISK3/www/5461/www/wp-admin/admin.php(34): require_once('/DISK3/www/5461...')
#8 /DISK3/www/5461/www/wp-admin/ in /DISK3/www/5461/www/wp-content/plugins/woocommerce-sequential-order-numbers/woocommerce-sequential-order-numbers.php on line 466
– This plugin is only one with is not official compatible with latest version of Woocommerce. So i gues there is some problem.
]]>Search by order number does not work with latest woocommerce and latest wordpress
/edit: solved.
I would like to know if this plugin is still actively maintained and when it will be updated for compatibility with the latest wordpress and woocommerce version
]]>Hi,
I want to use this plugin whenever I perform a website restore and want to advance order number sequence, let’s say jump them ahead by 50 order numbers. So I can prevent order numbers from being re-used.
EXAMPLE SCENARIO: I have 50 orders yesterday (#51 to #100) and another 50 orders today (#101 to #150). I did a website restore and it went back to Order #100 as latest. I want to skip and advance to Order #151 so that orders #101 to #150 won’t be used again twice and avoid duplicate orders numbers.
How does this tool actually work? Does it create it’s own order numbers? Or does it also advance Post ids? If it creates its own, what happens to the native-generated order numbers? Are those still in the database somewhere? Which order number goes into shipstation (our Shipping Partner)? What current or future plugins are looking at the natively-generated order number that may still sit somewhere in the database vs the dummies created by the plugin?
I also saw on WooCommerce Sequential Order Numbers Pro’s Documentation that it currently doesn’t support Apple Pay via Stripe Plugin. We are about to implement Google Pay and Apple Pay to our store using the WooCommerce Payments Plugin which apparently partnered with stripe. Will that cause an issue?
]]>