Fixes product pages that return not found. Coming from 1.x: enter the API URL you receive from WT\nunder WT \u2192 Settings; your API key stays valid. Old \/wine\/ links are not redirected; beer needs its\nown page.<\/p>","2.0.0":"
2.0.0 talks to a new catalog service at a new address: enter the API URL you receive from WT under\nWT \u2192 Settings. Your existing API key stays valid and is kept through the update. The listing stays\nempty until the URL is in. Old \/wine\/ links are not redirected; beer needs its own page.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3681343,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3681343,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3681343,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3681343,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0","1.2.0","1.3.0","1.4.0","1.4.1","2.0.0","2.0.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3681343,"resolution":"1","location":"assets","locale":"","width":1280,"height":800},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3681343,"resolution":"2","location":"assets","locale":"","width":1280,"height":1664},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3681343,"resolution":"3","location":"assets","locale":"","width":780,"height":1688},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3681343,"resolution":"4","location":"assets","locale":"","width":1280,"height":960},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3681343,"resolution":"5","location":"assets","locale":"","width":1280,"height":560}},"screenshots":{"1":"The wine listing with the filter panel open and France ticked: 361 French wines, each filter\nvalue showing how many products are behind it. Country and colour names come from WT in the\nlanguage attached to the key, which is Dutch here.","2":"A product page: name, the producer's own name for it, country, region and appellation, the\nVivino rating with its number of ratings, an ORGANIC badge, the bottle picture, the\nvinification and tasting notes and the food pairing, and the specifications grouped into\nCharacteristics and Bottle. No price anywhere.","3":"The same wine listing on a phone: the \"Filters (2)\" bar open above the results, with the\nCountry and Colour sections expanded and France and Red ticked.","4":"WT \u2192 Settings: the API URL and key, the purchase-history filter for the wine and the beer\nlisting side by side, and the status panel showing the index, the SEO integration, the two\nlisting pages and the number of blocked products.","5":"WT \u2192 Blocked products: a search for \"Maucoil\" returning two products, one of them already\nblocked and marked as such."}},"plugin_section":[],"plugin_tags":[10553,5632,2777,229459,5631],"plugin_category":[],"plugin_contributors":[279179],"plugin_business_model":[],"class_list":["post-127421","plugin","type-plugin","status-publish","hentry","plugin_tags-b2b","plugin_tags-beer","plugin_tags-catalog","plugin_tags-product-listing","plugin_tags-wine","plugin_contributors-wijntransport","plugin_committers-wijntransport"],"banners":{"banner":"https:\/\/ps.w.org\/wijntransport\/assets\/banner-772x250.png?rev=3681343","banner_2x":"https:\/\/ps.w.org\/wijntransport\/assets\/banner-1544x500.png?rev=3681343","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/wijntransport\/assets\/icon-128x128.png?rev=3681343","icon_2x":"https:\/\/ps.w.org\/wijntransport\/assets\/icon-256x256.png?rev=3681343","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/wijntransport\/assets\/screenshot-1.png?rev=3681343","caption":"The wine listing with the filter panel open and France ticked: 361 French wines, each filter\nvalue showing how many products are behind it. Country and colour names come from WT in the\nlanguage attached to the key, which is Dutch here."},{"src":"https:\/\/ps.w.org\/wijntransport\/assets\/screenshot-2.png?rev=3681343","caption":"A product page: name, the producer's own name for it, country, region and appellation, the\nVivino rating with its number of ratings, an ORGANIC badge, the bottle picture, the\nvinification and tasting notes and the food pairing, and the specifications grouped into\nCharacteristics and Bottle. No price anywhere."},{"src":"https:\/\/ps.w.org\/wijntransport\/assets\/screenshot-3.png?rev=3681343","caption":"The same wine listing on a phone: the \"Filters (2)\" bar open above the results, with the\nCountry and Colour sections expanded and France and Red ticked."},{"src":"https:\/\/ps.w.org\/wijntransport\/assets\/screenshot-4.png?rev=3681343","caption":"WT \u2192 Settings: the API URL and key, the purchase-history filter for the wine and the beer\nlisting side by side, and the status panel showing the index, the SEO integration, the two\nlisting pages and the number of blocked products."},{"src":"https:\/\/ps.w.org\/wijntransport\/assets\/screenshot-5.png?rev=3681343","caption":"WT \u2192 Blocked products: a search for \"Maucoil\" returning two products, one of them already\nblocked and marked as such."}],"raw_content":"\n
WT (Wijntransport B.V.) supplies wine and beer to restaurants, hotels, shops and wholesalers. This\nplugin puts that assortment on your own WordPress website: a wine listing, a beer listing and a\npage per product, filled straight from WT's catalog every time a visitor looks at them. Nothing is\ncopied into your site and kept there, so a product that changes at WT changes on your website too.<\/p>\n\n
Who it is for.<\/strong> WT customers who have a WordPress website. You need an API URL and an API key\nfrom WT; without them the plugin has nothing to show. Ask your WT contact for both. There is no\nfree or public catalog behind this plugin.<\/p>\n\n What a visitor gets.<\/strong> A listing of your assortment with a picture, a name, the alcohol\npercentage, the colour, the bottle size and the case quantity for every product. Down the side (or\nbehind a \"Filters\" button on a phone) are filters for country, colour, bottle size and producer,\neach showing how many products are behind it, plus a search box. Ticking a filter narrows the list\nand the other filters' counts immediately. The filters need JavaScript in the visitor's browser;\nthe search box is an ordinary form and works without it. Clicking a product opens its own page\nwith the producer's own name for it, the region it comes from, its rating, badges such as ORGANIC\nor NEW, the tasting note, the food pairing, and the specifications split into \"Characteristics\"\nand \"Bottle\".<\/p>\n\n No prices, anywhere.<\/strong> WT's prices are per customer and are not part of what this plugin shows.\nNo price is displayed, and none is stored on your site.<\/p>\n\n What you control.<\/strong> Two things, both under WT<\/strong> in the WordPress admin menu:<\/p>\n\n This plugin depends on one external service: the WT catalog API<\/strong>. It is the source of every\nproduct, picture, filter and piece of text the plugin displays. Your site has no catalog of its\nown.<\/p>\n\n Where it connects.<\/strong> To the address you enter yourself under WT \u2192 Settings (\"API URL\"). The\nplugin ships no address of its own; you receive the URL and the key together from WT.<\/p>\n\n What is sent, and when.<\/strong> Every request carries your API key, so the service knows which\ncustomer's assortment to answer with. A request is made when a visitor opens a listing or a\nproduct page and the plugin has no fresh copy of it, and once a day to rebuild the product index.\nAlong with the key the plugin sends only what the visitor asked for: the page number, the search\nterm they typed, the filters they ticked (country, colour, bottle size, producer), which drink the\npage is for, your purchase-history setting, and the identifier of the product being viewed. No\npersonal data of your visitors is sent<\/strong> \u2014 no name, e-mail address, IP address, cookie or user\naccount is forwarded, and the plugin sets no cookies of its own.<\/p>\n\n What is stored on your site.<\/strong> One settings row holding your API URL, your API key, your two\npurchase-history choices and your block list; a small index of the catalog (identifier, base\nnumber, link, name, vintage, drink, thumbnail) used to build product addresses and the XML\nsitemap; and short-lived cached copies of listing and product responses. No price is ever\nrequested for display, shown or stored.<\/strong> Deleting the plugin from Plugins \u2192 Installed Plugins\nremoves all of it, including your API key.<\/p>\n\n Terms and privacy.<\/strong> The catalog is a service of WT for its own customers, and its use is\ngoverned by your customer agreement with WT. Nothing about your website's visitors is sent to it \u2014\nsee above \u2014 so no visitor-facing privacy policy applies to the plugin's requests. Company site:\nhttps:\/\/wt.group\/<\/p>\n\n The wine listing<\/strong> (screenshot 1) is an ordinary WordPress page to which you gave the page\ntemplate \"[WT] Wine listing\". The plugin fills it: search box, the filter panel, the result count,\nthe grid of products and the pager. Every filter choice is in the page's own address, so a\nfiltered list can be bookmarked, shared and linked to. Filter labels \u2014 country names, colour names\n\u2014 come from WT in the language attached to your key, which is why they may read Dutch on an\nEnglish site.<\/p>\n\n The beer listing<\/strong> is the same page, with the page template \"[WT] Beer listing\" instead. It\nshows beer only, has its own purchase-history setting and its own search. You only need it if you\nsell beer.<\/p>\n\n The product page<\/strong> (screenshot 2) lives under whichever listing the visitor came from \u2014\n \/wines\/product\/1015-chat-maucoil-chateauneuf-du-pape-rouge-bio\/. You do not create these pages;\nthe plugin answers those addresses itself. Text blocks that WT has not filled in are left out\nrather than shown empty, and the specification rows differ per drink: closure type, vintage and\ncolour are wine rows, degrees Plato is a beer row.<\/p>\n\n On a phone<\/strong> (screenshot 3) the filter panel folds into a \"Filters\" button above the results,\nwith the number of active filters on it. Opening it shows the same filter sections; each opens on\na tap.<\/p>\n\n WT \u2192 Settings<\/strong> (screenshot 4) is where the API URL and the API key go, and where you choose the\npurchase-history filter per listing. Underneath is a status panel: which URL is in use and whether\na key is saved, how many products are in the index and when it was last built, which SEO plugin is\nproviding meta tags and the sitemap, which pages are acting as your wine and beer listings, and\nhow many products you have blocked. Two buttons sit below it: Rebuild product index now<\/strong>, which\nfetches the whole catalog again, and Flush cache<\/strong>, which throws away the pages the plugin is\nremembering. Saving a key checks it against the catalog before storing it, and tells you if it was\nrefused; a refused key never replaces the saved one.<\/p>\n\n WT \u2192 Blocked products<\/strong> (screenshot 5) is a search box. Type a product name or a base number,\nand every match comes back with its base number, name, drink and vintages. \"Block\" hides that\nproduct from the listing, from its own product page and from the sitemap \u2014 every vintage of it,\nbecause blocking works on the base number. The \"Blocked\" tab lists what you have hidden, and\nunblocks it again.<\/p>\n\n\n Read this before you update; 2.0.0 is not a drop-in replacement.<\/p>\n\n WT \u2192 Blocked products. Search for it by name, or type its base number, and press \"Block\". Blocking\nworks on the base number, so every vintage of that product<\/strong> is hidden at once \u2014 from the\nlisting, from its own product page (which then returns \"not found\") and from the XML sitemap. The\n\"Blocked\" tab lists everything you have hidden and unblocks it again. You can also block a base\nnumber the plugin has not indexed yet, using the \"Block by base number\" box; a number the catalog\ndoes not know is refused rather than blocked.<\/p><\/dd>\n Check the page's template under Page Attributes. \"[WT] Wine listing\" shows wine only and \"[WT]\nBeer listing\" shows beer only \u2014 a page with the wrong one shows the wrong drink. If a\ncorrectly-templated beer page is empty, look at WT \u2192 Settings: if \"Beer listing shows\u2026\" is set to\na purchase-history window and you have not bought beer in that window, there is nothing to show.\nSet it to \"All products\" to check.<\/p><\/dd>\n Two settings can do that, and they add up:<\/p>\n\n If neither explains it, press \"Rebuild product index now\" and check the status panel for an error.<\/p><\/dd>\n Yes \u2014 with CSS in your theme or in Appearance \u2192 Customise \u2192 Additional CSS. The plugin's markup\nuses stable class names that will not change without a major version:<\/p>\n\n Class names beginning The product index is rebuilt once a day, and listing pages are remembered for a few minutes at a\ntime. Press Rebuild product index now<\/strong> on the settings screen to pull the catalog again\nimmediately, and Flush cache<\/strong> to drop the remembered pages. Both are safe to press at any time.<\/p><\/dd>\n Yes. If Yoast SEO or Rank Math is active, the plugin hands it the title, description, canonical\naddress, Open Graph tags and the products for its XML sitemap, so your products appear in the\nsitemap you already have. With neither installed, WordPress's own sitemap and meta tags are used\ninstead. Nothing needs configuring either way; the settings screen's SEO<\/strong> row names which\nplugin is doing which job.<\/p><\/dd>\n The plugin's own text \u2014 buttons, headings, filter section names, the admin screens \u2014 is available\nin Dutch, German and English, and follows your site's language setting. The product text<\/strong> and\nthe filter values<\/strong> (country and colour names) come from WT in the language attached to your API\nkey, and are not translated by the plugin. So an English-language site with a Dutch-language key\nshows English buttons and Dutch country names. If that is wrong for you, ask WT to change the\nlanguage on your key.<\/p><\/dd>\n No. If product pages ever start returning \"not found\", the plugin repairs this on the next visit.\nSettings \u2192 Permalinks \u2192 \"Save Changes\" does the same by hand.<\/p><\/dd>\n Either way the listing says so on the page rather than showing an empty list and passing that off\nas your assortment. The HTTP status differs on purpose:<\/p>\n\n Everything the plugin wrote: the settings row (including your API key), the block list, the\nproduct index, every cached page and the daily scheduled task. That happens on delete<\/strong>, from\nPlugins \u2192 Installed Plugins.<\/p>\n\n Deactivating loses no data, but it cancels the daily index rebuild, and while the plugin is off a\n \/product\/\u2026 address shows the listing page instead of the product. Activating it again restores\nboth, with your settings, block list and index exactly as you left them.<\/p><\/dd>\n\n<\/dl>\n\n\n Release Date: September 2026<\/p>\n\n Release Date: September 2026<\/p>\n\n A full rewrite against WT's new catalog service.<\/p>\n\n Breaking changes.<\/strong> This release does not work with a 1.x installation as it stands. 2.0.0 talks\nto a new catalog service at a new address: enter the API URL<\/strong> you receive from WT under WT \u2192\nSettings before anything is shown. Your existing API key stays valid<\/strong> and is kept through the\nupdate. Product addresses have changed<\/strong> from Release Date: April 12, 2021<\/p>\n\n Release Date: December 15, 2020<\/p>\n\n Release Date: October 15, 2020<\/p>\n\n Release Date: September 17, 2020<\/p>\n\n Release Date: September 16, 2020<\/p>\n\n Release Date: August 20, 2020<\/p>\n\n\n
External services<\/h4>\n\n
The screens, one by one<\/h4>\n\n
\n
Upgrading from version 1.x<\/h4>\n\n
\n
\/<your-listing-page>\/wine\/<name>\/<\/code>. 2.0.0 uses\n \/\/product\/-\/. Old addresses are not redirected<\/strong> \u2014\nthey return \"not found\". If you have linked to individual wines from menus, posts or\nnewsletters, those links need updating. Search engines pick the new addresses up from the\nsitemap.<\/li>\n\n
How do I hide a product?<\/h3><\/dt>\n
Why does my beer page show wine, or nothing at all?<\/h3><\/dt>\n
Why does the listing show fewer products than WT's catalog?<\/h3><\/dt>\n
\n
Can I change the look?<\/h3><\/dt>\n
\n
.wt-listing<\/code>, .wt-listing--wine<\/code>, .wt-listing--beer<\/code>, .cc-search-box<\/code>, .wt-empty<\/code>,\n .wt-error<\/li>\n.cc-sidebar<\/code>, .cc-sidebar__section<\/code>, .cc-sidebar__title<\/code>, .cc-sidebar__reset<\/code>,\n .cc-filter-bar, .cc-filter-bar__button<\/code>, .cc__filter-item<\/code>, .cc__filter-text<\/code>,\n .cc__filter-count<\/li>\n.cc-product<\/code>, .cc-product__image<\/code>, .cc-product__title<\/code>, .cc-product__info<\/code>,\n .cc-stats, .cc-pagination<\/code><\/li>\n.wt-single<\/code>, .wt-product__head<\/code>, .wt-product__origin<\/code>, .wt-product__marks<\/code>,\n .wt-product__body, .wt-product__col--prose<\/code>, .wt-product__col--specs<\/code>, .wt-specs<\/code>,\n .wt-specs__group, .wt-rating<\/code>, .wt-badge<\/code>, .wt-breadcrumb<\/code><\/li>\n<\/ul>\n\njs-<\/code> drive the plugin's own JavaScript. Do not style or remove them.<\/p><\/dd>\nWhy is a product missing that WT added today?<\/h3><\/dt>\n
Does it work with Yoast SEO or Rank Math?<\/h3><\/dt>\n
Which languages does it speak?<\/h3><\/dt>\n
Do I need to do anything about permalinks?<\/h3><\/dt>\n
What happens if the catalog is unreachable, or my key is refused?<\/h3><\/dt>\n
\n
What is removed when I delete the plugin?<\/h3><\/dt>\n
2.0.1<\/h4>\n\n
\n
2.0.0<\/h4>\n\n
\/<listing>\/wine\/<name>\/<\/code> to\n \/\/product\/-\/, and the old addresses are not redirected<\/strong> \u2014 links\nto individual wines from elsewhere on your site need updating. The wine listing now shows wine\nonly<\/strong>, so a site that also sells beer needs a second page using the new \"[WT] Beer listing\"\ntemplate. The minimum requirements rise to WordPress 6.7 and PHP 7.4<\/strong>.<\/p>\n\n\n
wp-config.php<\/code> with\n define( 'WIJNTRANSPORT_API_URL', '\u2026' );.<\/li>\n1.4.1<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n