wc-plugin-framework
wc-plugin-framework copied to clipboard
The official SkyVerge WooCommerce plugin framework
@see https://wordpress.org/support/topic/the-plugin-slows-down-the-site-by-littering-the-wp_options-table/ the create_job ( https://github.com/godaddy-wordpress/wc-plugin-framework/blob/1c2fb1a31228f754ef7427f15ac034d3d8cb6de0/woocommerce/utilities/class-sv-wp-background-job-handler.php#L391 ) and get_job ( https://github.com/godaddy-wordpress/wc-plugin-framework/blob/1c2fb1a31228f754ef7427f15ac034d3d8cb6de0/woocommerce/utilities/class-sv-wp-background-job-handler.php#L391 0 are really bad for performance as they do not have integer primary keys and use LIKE queries in...
**The issue:** We have a site using the [WooCommerce Square](https://wordpress.org/plugins/woocommerce-square/#description) plugin for a payment gateway that utilize the [WooCommerce Plugin Framework](https://github.com/skyverge/wc-plugin-framework). There appears to be an issue where the plugin...
The Google Pay JavaScript file is missing the `environment` configuration. All requests are being being against the test environment and doesn't let a merchant choose to move to production for...
Our tagging nomenclature for this repository was copied from wc-plugins, which adds a prefix to the version number. This isn't needed for a single repository though, so let's update our...
Right now our plugin loader checks for the required PHP, WordPress, and WooCommerce versions before loading the plugin itself: https://github.com/skyverge/wc-plugin-framework/blob/release-v5/woocommerce/woocommerce-framework-plugin-loader-sample.php#L119-L121 We could try and move the WP & WC version...
UPDATE: I got it to work. the only problem is the "Expiration (MM/YY)" text. It just doesn't work. My guess is that somewhere down the line, during parsing, the SLASH...
POC only, DO NOT MERGE # Objective Provide a new way for gateways to pass transaction data around throughout the payment, capture, and refund processes that's more reliable and testable,...
Right now our `SV_WP_Job_Batch_Handler` utility relies on the background/async job handler by simply processing chunks of a background job in batches. This works very well for plugins that support both...
Since we don't leverage the WP core `get|update_option` methods any longer, we don't necessarily need the unique job identifier in the option name. This causes issues on some hosts that...
In our utilities classes, we commonly run into a couple issues: 1. Object caching overrides that improperly handle options (don't purge cache when an option is updated, so job progress...