Generated doctoc

Claudio Sanches 2019-04-16 16:30:52 -03:00
parent 09e099b9eb
commit 0f7815f1cf
6 changed files with 59 additions and 0 deletions

@ -1,3 +1,14 @@
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
## Table of Contents
- [Themes can define image sizes](#themes-can-define-image-sizes)
- [Customize image sizes in the customizer](#customize-image-sizes-in-the-customizer)
- [Changing image sizes via hooks](#changing-image-sizes-via-hooks)
- [Changing what image sizes are used in WooCommerce via hooks](#changing-what-image-sizes-are-used-in-woocommerce-via-hooks)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
[Note: This document is now maintained in the WooCommerce documents](https://docs.woocommerce.com/document/image-sizes-theme-developers/).
To display images in your catalog, WooCommerce registers a few new image sizes which define the actual image dimensions to be used. These sizes include:

@ -1,3 +1,12 @@
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
## Table of Contents
- [Basic usage:](#basic-usage)
- [Usage with settings:](#usage-with-settings)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
If you are using custom WooCommerce template overrides in your theme you need to declare WooCommerce support using the `add_theme_support` function. WooCommerce template overrides are only enabled on themes that declare WooCommerce support. If you do not declare WooCommerce support in your theme, WooCommerce will assume the theme is not designed for WooCommerce compatibility and will use shortcode-based unsupported theme rendering to display the shop.
Declaring WooCommerce support is straightforward and involves adding one function in your theme's functions.php file.

@ -1,3 +1,14 @@
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
## Table of Contents
- [Viewing generated structured data](#viewing-generated-structured-data)
- [Customizing structured data using WooCommerce filters](#customizing-structured-data-using-woocommerce-filters)
- [Adding extra data](#adding-extra-data)
- [Generating product data in other places, e.g. archives](#generating-product-data-in-other-places-eg-archives)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
WooCommerce outputs structured data for products automatically. [According to Google](https://developers.google.com/search/docs/data-types/product), in the context of your store, this markup is suitable for single product pages.
*Note: Prior to 3.5.6, limited data was sometimes output to archives/categories. This is no longer the case; according to Google guidelines only visible data should be marked up, and archives that link out to individual pages should not be marked out. [Issue ref](https://github.com/woocommerce/woocommerce/issues/22896), [Docs](https://developers.google.com/search/docs/guides/sd-policies#multiple-elements-on-a-page).*

@ -1,3 +1,17 @@
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
## Table of Contents
- [How it works](#how-it-works)
- [Background jobs and BasicAuth](#background-jobs-and-basicauth)
- [Viewing background regeneration logs](#viewing-background-regeneration-logs)
- [Cancelling a background regeneration job](#cancelling-a-background-regeneration-job)
- [CDN plugins](#cdn-plugins)
- [How to disable background regeneration](#how-to-disable-background-regeneration)
- [Using Jetpack Photon instead](#using-jetpack-photon-instead)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
WooCommerce 3.3 introduced thumbnail regeneration functionality. In the past when image size settings were changed you would need to install an external plugin and then have it regenerate all WordPress image thumbnails before the changes would be visible.
The new image regeneration functionality, combined with the introduction of WooCommerce image settings in the customizer, now ensure that as you make changes to your store image settings you can preview the changes in real-time within the customizer.

@ -1,3 +1,16 @@
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
## Table of Contents
- [Introduction](#introduction)
- [Using WC_Queue](#using-wc_queue)
- [Adding jobs to the queue](#adding-jobs-to-the-queue)
- [Extending WC_Queue with your own queue system](#extending-wc_queue-with-your-own-queue-system)
- [Custom queue class example](#custom-queue-class-example)
- [Making WooCommerce use your custom queue class](#making-woocommerce-use-your-custom-queue-class)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
## Introduction
With WooCommerce 3.5+ there is a new Worker Queue system, WC_Queue. This new system allows for scheduling and running background jobs using the [Action Scheduler library](https://github.com/Prospress/action-scheduler), however, it is easily overridable to hook in a Worker Queue system of your own likings like Amazon SQS or any other queue system out there.

@ -29,6 +29,7 @@
- [wc-customer-search inputs](#wc-customer-search-inputs)
- [Checking POSTed data](#checking-posted-data)
- [Order version property](#order-version-property)
- [Order address indexes](#order-address-indexes)
- [Template changes](#template-changes)
- [Deprecated functions](#deprecated-functions)
- [Deprecated filters](#deprecated-filters)