Dependency Minification vs WooCommerce Product Dependencies

This plugin takes all scripts and stylesheets that have been added via wp_enqueue_script and wp_enqueue_style and automatically concatenates and minifies them into logical groups. For example, scripts in the footer get grouped together and styles with the same media (e.g. print) get minified together. Minification is done via WP-Cron in order to prevent race conditions and to ensure that the minification process does not slow down page responses. This is a reincarnation and rewrite of the Optimize Scripts plugin, which this plugin now supersedes. Features: Minified sources are stored in the WP Options table so no special filesystem access is required. Endpoint for minified requests is at /_minified, which can be configured. Admin page for taking inventory of minified scripts and stylesheets, with methods for expiring or purging the cached data. Dependencies which must not be minified may be excluded via the dependency_minification_excluded filter. Dependencies hosted on other domains are by default excluded, but this behavior can be changed by filtering the default_exclude_remote_dependencies option via the dependency_minification_options filter, or on a case-by-case basis via the filter previously mentioned. By default excludes external scripts from being concatenated and minified, but they can be opted in via the dependency_minification_excluded filter. The length of time that a minified source is cached defaults to 1 month, but can be configured via the cache_control_max_age_cache option. If a minified source is not available yet, the page source will note that the dependency minification process is pending. Any errors that occur during minification will be shown on the frontend in comments if the show_error_messages option is enabled; such errors are enabled by default if WP_DEBUG. If the minification process errors out, the original unminified sources are served and the error is cached for 1 hour (by default, configured via cache_control_max_age_error) to prevent back-to-back crons from continually attempting to minify in perpetuity. Cached minified sources are served with Last-Modified and ETag responses headers and requests will honor If-None-Match and If-Modified-Since to return 304 Not Modified responses (configurable via the allow_not_modified_responses option). Data attached to scripts (e.g. via wp_localize_script) is also concatenated together and attached to the newly-minified script. WP-Cron is utilized to initiate the minification process in order to prevent race conditions, and to ensure that page responses aren’t slowed down. Stale minified scripts and stylesheets remain until replaced by refreshed ones; this ensures that full-page caches which reference stale minified sources won’t result in any 404s. Can serve compressed responses with gzip or deflate. Transforms relatives paths in stylesheets (e.g. background-images) to absolute ones, so that they don’t 404. Development of this plugin is done on GitHub. Pull requests welcome. Please see issues reported there before going to the plugin forum. If you are using Nginx with the default Varying Vagrant Vagrants config, you’ll want to remove css|js from this rule in nginx-wp-common.conf (or remove the rule altogether): # Handle all static assets by serving the file directly. Add directives # to send expires headers and turn off 404 error logging. location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ { expires 24h; log_not_found off; }

Looking for a way to restrict product access in WooCommerce? Don’t want to set up a full-fledged memberships site? This tiny plugin allows you to restrict access to any WooCommerce product, depending on the ownership or purchase of other, required products. Features: Conditional product access based on the ownership and/or purchase of other required products. Support for “ownership”, “purchase” and “ownership/purchase” dependency types. Developers can checkout and contribute to the source code on the plugin’s GitHub Repository. Important: Requires WooCommerce 2.2+. WooCommerce 3.0+ or higher recommended. Like this plugin? You’ll love our official WooCommerce Extensions: WooCommerce Product Bundles WooCommerce Composite Products WooCommerce Conditional Shipping and Payments WooCommerce Product Recommendations All Products for WooCommerce Subscriptions Documentation Dependencies are evaluated when customers attempt to add a product to their cart. If validation fails, the product cannot be added to the cart and a notice is displayed. In order to evaluate “Ownership”-type dependencies, customers are prompted to log in. Creating Dependencies To add dependencies to a product: Go to the Product Data > Dependencies tab. Use the Product Dependencies field to search for and add some products and/or variations. Choose a Dependency Type. Update to save your changes. The “Ownership” dependency type is evaluated by checking if the customer has purchased a required product in a previous order. The “Purchase” dependency type requires the customer to have a required product in the cart in order to purchase the dependent one. Ownership vs Purchase The plugin allows you to select between 3 different dependency types: Ownership: Access is granted only to customers that already own any of the products added to the Product Dependencies field. Purchase: The product can be purchased only in combination with any of the items added to the Product Dependencies field. Ownership is not taken into account. Either: Access is granted with ownership or purchase of any item added to the Product Dependencies field.