ProducerKit 2.6.0

The plugin stops calling your work by somebody else's name.

A potter's process notes were stored as milling. A musician's release notes were stored as growing. You never saw those words — the screen has said "Preparation Notes" and "Release Notes" since 2.5.0 — but the database, the API and your spreadsheet exports all still said farm. This release corrects that everywhere, on update, with your data intact.

It is also the release where a farm and a bakery can share one site and a visitor can tell which is which.

Changed

Your fields are stored under names that fit your trade. Nineteen stored field names were corrected, along with the matching names in the API, the agent-facing schema, and the product CSV. If you have written a template, snippet or integration against a name like _pkit_em_ticket_url or _pkit_growing_notes, it is now _pkit_ticket_url and _pkit_production_notes. The spreadsheet column growing_notes is now production_notes, and older exports still import.

Loading sample data now says what it does. It publishes example content that visitors can see, which the button never mentioned.

Added

Say which business made this. When two producers share a site, products and events carry a byline — "Grown by Leftfield Urban Farm", "Baked by Slowbird Bread Co." The wording follows the trade of whoever published it, so a bakery's loaf is never "grown", and an event is always "Hosted by". Set the name you want shown on your own user profile. Nothing appears on a single-producer site.

Four things any event can have, named for your trade: who else is on it, when doors open, who can come, and where tickets are sold. A band's support act is a farm's shared booth is a workshop's co-teacher.

Sample data that matches your trade. A beekeeper gets Wildflower Honey at The Home Yard; a potter a Stoneware Mug at The Studio — rather than eight farm products whoever you are.

Fixed

Clicking "ProducerKit" opened an empty Sources list instead of the dashboard. The dashboard could only be reached by typing its address, which also meant the sample-data controls were effectively hidden.

Removing sample data deleted more than sample data. It also swept up leftover availability and RSVP records belonging to real products and events you had deleted yourself, and it stopped after 200 items per type.

Editor sidebar panels no longer call a React hook conditionally. Nine panels could break the editor sidebar depending on what a post had filled in.

---

Two things to know before updating.

Stored field names change automatically and your data comes with them — but custom code written against the old names needs updating. The full list is in the changelog.

If your products and events were published by more than one WordPress user, they will now carry a byline naming the producer. That is intended for two businesses sharing a site, but it triggers on any site with more than one author. Set each person's name on their profile, or turn bylines off with the pkit_show_producer_byline filter.

Full changelog: https://github.com/jwincek/producerkit/blob/v2.6.0/CHANGELOG.md