Getting started
Requirements
The WordPress, WooCommerce and PHP versions Gridline needs, who can use it, and the products it edits.
- WordPress 6.5 or later (tested up to 7.1)
- WooCommerce 8.2 or later (tested up to 11.1), active; WordPress won't activate Gridline without it
- PHP 7.4 or later
- A current browser with JavaScript on. The grid runs in your browser.
Who can use it
Anyone who can edit products: shop managers and administrators by default. The Bulk Editor appears under Products for them only. Each save also checks that the person may edit that particular product, so a role limited by another plugin can't change products it isn't allowed to.
What it edits
- Simple products, with every column.
- Variable products, with the fields that belong to the product itself: name, SKU, status, stock management, categories and tags. Prices and stock status come from the variations, so those cells are greyed out, and the product's price range is shown under its name. Variations are edited on the product screen, or in the grid with Gridline Pro.
- Grouped and external products, with the fields they have. Grouped and external products don't keep stock, so their stock cells are greyed out.
Drafts, pending and private products are listed with published ones. Trashed products aren't.
Works with
- High-Performance Order Storage (HPOS). Gridline doesn't touch orders, and declares itself compatible.
- Other plugins that react to product saves, such as search indexes, feeds and stock sync. Gridline saves each product through WooCommerce once, as the product screen does, so their hooks run as usual.
- Large catalogues. The grid loads one page at a time (10 to 200 products, your choice), and search and filters run on the server.
Nothing else to set up
Gridline adds no database tables, scheduled tasks or external requests. It stores only each user's Screen Options (columns shown and products per page), as WordPress does for its own lists.