{"id":351589,"date":"2026-08-13T01:17:17","date_gmt":"2026-08-13T01:17:17","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/burnpedia-pin-scheduler-for-pinterest\/"},"modified":"2026-09-18T22:33:53","modified_gmt":"2026-09-18T22:33:53","slug":"burnpedia-pin-scheduler-for-pinterest","status":"publish","type":"plugin","link":"https:\/\/br.wordpress.org\/plugins\/burnpedia-pin-scheduler-for-pinterest\/","author":23546237,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.31","stable_tag":"1.0.31","tested":"7.1.1","requires":"6.5","requires_php":"7.4","requires_plugins":null,"header_name":"Burnpedia Pin Scheduler for Pinterest","header_author":"Burnpedia","header_description":"Turn every post you publish into a scheduled Pin. Connect a free Burnpedia account, choose a board, and your Pinterest queue fills itself.","assets_banners_color":"269289","last_updated":"2026-09-18 22:33:53","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/burnpedia.app\/developers","header_author_uri":"https:\/\/burnpedia.app","rating":0,"author_block_rating":0,"active_installs":0,"downloads":875,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.1":{"tag":"1.0.1","author":"lalokupfer","date":"2026-08-13 01:16:58","revision":3644113},"1.0.10":{"tag":"1.0.10","author":"lalokupfer","date":"2026-08-24 16:23:43","revision":3663912},"1.0.11":{"tag":"1.0.11","author":"lalokupfer","date":"2026-08-25 18:25:35","revision":3665842},"1.0.12":{"tag":"1.0.12","author":"lalokupfer","date":"2026-08-28 19:07:33","revision":3670840},"1.0.13":{"tag":"1.0.13","author":"lalokupfer","date":"2026-08-29 20:35:03","revision":3671869},"1.0.14":{"tag":"1.0.14","author":"lalokupfer","date":"2026-09-04 09:11:27","revision":3680936},"1.0.15":{"tag":"1.0.15","author":"lalokupfer","date":"2026-09-04 17:28:03","revision":3681598},"1.0.16":{"tag":"1.0.16","author":"lalokupfer","date":"2026-09-05 18:36:50","revision":3682742},"1.0.17":{"tag":"1.0.17","author":"lalokupfer","date":"2026-09-05 21:44:02","revision":3682830},"1.0.18":{"tag":"1.0.18","author":"lalokupfer","date":"2026-09-06 06:43:17","revision":3683059},"1.0.19":{"tag":"1.0.19","author":"lalokupfer","date":"2026-09-06 11:01:53","revision":3683340},"1.0.2":{"tag":"1.0.2","author":"lalokupfer","date":"2026-08-18 07:17:52","revision":3652174},"1.0.20":{"tag":"1.0.20","author":"lalokupfer","date":"2026-09-06 11:43:33","revision":3683375},"1.0.21":{"tag":"1.0.21","author":"lalokupfer","date":"2026-09-06 12:06:12","revision":3683410},"1.0.22":{"tag":"1.0.22","author":"lalokupfer","date":"2026-09-06 20:26:18","revision":3683933},"1.0.24":{"tag":"1.0.24","author":"lalokupfer","date":"2026-09-09 16:54:26","revision":3688706},"1.0.25":{"tag":"1.0.25","author":"lalokupfer","date":"2026-09-12 07:14:21","revision":3692409},"1.0.26":{"tag":"1.0.26","author":"lalokupfer","date":"2026-09-12 07:39:21","revision":3692436},"1.0.27":{"tag":"1.0.27","author":"lalokupfer","date":"2026-09-12 15:03:23","revision":3692841},"1.0.28":{"tag":"1.0.28","author":"lalokupfer","date":"2026-09-13 06:47:10","revision":3693395},"1.0.29":{"tag":"1.0.29","author":"lalokupfer","date":"2026-09-13 12:10:37","revision":3693629},"1.0.3":{"tag":"1.0.3","author":"lalokupfer","date":"2026-08-18 08:20:20","revision":3652269},"1.0.30":{"tag":"1.0.30","author":"lalokupfer","date":"2026-09-13 13:28:07","revision":3693718},"1.0.31":{"tag":"1.0.31","author":"lalokupfer","date":"2026-09-18 22:33:53","revision":3702824},"1.0.4":{"tag":"1.0.4","author":"lalokupfer","date":"2026-08-18 15:50:58","revision":3653209},"1.0.5":{"tag":"1.0.5","author":"lalokupfer","date":"2026-08-20 21:37:34","revision":3657824},"1.0.7":{"tag":"1.0.7","author":"lalokupfer","date":"2026-08-23 20:06:42","revision":3662279},"1.0.8":{"tag":"1.0.8","author":"lalokupfer","date":"2026-08-24 08:19:33","revision":3662897},"1.0.9":{"tag":"1.0.9","author":"lalokupfer","date":"2026-08-24 15:18:52","revision":3663770}},"upgrade_notice":{"1.0.31":"<p>Adds the free Pinterest check-up: see which posts have no big Pinterest image, are not optimized for Pinterest, or were never pinned \u2014 with optional AI to fix a post you choose.<\/p>","1.0.30":"<p>Stops a dropped connection from creating the same Pin twice (and charging an AI cover twice) when a Pin is retried.<\/p>","1.0.29":"<p>Adds &quot;Try an AI cover&quot; to the post editor: preview an AI cover for a post that already has a photo, and pin it only if you like it.<\/p>","1.0.28":"<p>Fixes &quot;Pin older posts&quot; offering posts from excluded categories when automatic pinning is off, and stops a slow AI image from creating a second Pin.<\/p>","1.0.24":"<p>Adds a &quot;Copy diagnostics&quot; button to the Activity tab, so asking for help takes one paste instead of four replies. Your API key is never included and nothing is transmitted.<\/p>","1.0.23":"<p>Listing and documentation only - seven new FAQ entries and a clearer description of what the plugin already does. No functional change.<\/p>","1.0.22":"<p>Once your site has been publishing Pins for a fortnight and they are being seen on Pinterest, the Pins tab asks - once - how it is going. Two links: tell us something is wrong, or leave a review. Nothing is offered in return, and &quot;No thanks&quot; means it never comes back.<\/p>","1.0.15":"<p>Up to six Pins per post, each from a different photograph and a day apart - without raising the number of Pins a day you already chose. AI covers put your headline on the generated photograph in one request, so a failure can no longer charge you for a picture that never became a Pin.<\/p>","1.0.14":"<p>Posts with no picture are no longer skipped - Burnpedia designs a cover from the title, free, at the size Pinterest likes.<\/p>","1.0.13":"<p>Tells you how many published posts still have no Pin, and why each one is or is not ready. Plus a &quot;Run it now&quot; button for when your Pins are stuck behind a scheduler that is not running.<\/p>","1.0.10":"<p>Shows what your Pins actually did - impressions, saves and clicks to your site - on the results tab and beside each post.<\/p>","1.0.9":"<p>Adds a &quot;Pins from this site&quot; tab - what actually went out, when, to which board, and a link to each live Pin - and optional AI images for posts that have none.<\/p>","1.0.8":"<p>Tells you when WordPress is not running its scheduler - the commonest reason a published post produces no Pin - and gives you the line that fixes it.<\/p>","1.0.4":"<p>The Activity tab now shows what is about to happen, not only what already did.<\/p>","1.0.3":"<p>Adds &quot;Send a test Pin&quot;: one button that checks the whole path and tells you exactly which step is broken.<\/p>","1.0.2":"<p>A first-run checklist and a clear warning when automatic pinning is off, so a post that produced no Pin now tells you why.<\/p>","1.0.1":"<p>Stricter capability checks on the plugin&#039;s admin REST routes.<\/p>","1.0.0":"<p>First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3644112,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3644112,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3644112,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3644112,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.1","1.0.10","1.0.11","1.0.12","1.0.13","1.0.14","1.0.15","1.0.16","1.0.17","1.0.18","1.0.19","1.0.2","1.0.20","1.0.21","1.0.22","1.0.24","1.0.25","1.0.26","1.0.27","1.0.28","1.0.29","1.0.3","1.0.30","1.0.31","1.0.4","1.0.5","1.0.7","1.0.8","1.0.9"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3702823,"resolution":"1","location":"assets","locale":"","width":2640,"height":1880},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3702823,"resolution":"2","location":"assets","locale":"","width":2284,"height":1238},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3702823,"resolution":"3","location":"assets","locale":"","width":2640,"height":1880},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3702823,"resolution":"4","location":"assets","locale":"","width":2640,"height":1880},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3702823,"resolution":"5","location":"assets","locale":"","width":2640,"height":1880},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3702823,"resolution":"6","location":"assets","locale":"","width":2640,"height":1880},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3702823,"resolution":"7","location":"assets","locale":"","width":560,"height":2096},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3702823,"resolution":"8","location":"assets","locale":"","width":2640,"height":1880}},"screenshots":{"1":"The Pinterest check-up: which posts have no big Pinterest image, which are not optimized for Pinterest, and which you have never pinned \u2014 each with a link to open and fix it.","2":"\"Make it with AI\" on one post: a Pin title, a description and a cover preview. Nothing is pinned until you choose it.","3":"The settings screen: connection status, plan, and today's Pin allowance.","4":"Automation settings \u2014 when to pin, which posts, which board.","5":"Pin older posts: queue the archive you published before installing, spread over safe posting times.","6":"Pins from this site: impressions, saves and clicks for this website's Pins, without leaving WordPress.","7":"The Pinterest box in the post editor, with per-post title, description and board.","8":"The Activity log: what was pinned, what was skipped, and why."}},"plugin_section":[],"plugin_tags":[2016,312,279984,275436,154278],"plugin_category":[56],"plugin_contributors":[275437],"plugin_business_model":[],"class_list":["post-351589","plugin","type-plugin","status-publish","hentry","plugin_tags-auto-publish","plugin_tags-pinterest","plugin_tags-pinterest-automation","plugin_tags-pinterest-scheduler","plugin_tags-social-media-auto-post","plugin_category-social-and-sharing","plugin_contributors-lalokupfer","plugin_committers-lalokupfer"],"banners":{"banner":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/banner-772x250.png?rev=3644112","banner_2x":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/banner-1544x500.png?rev=3644112","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/icon-128x128.png?rev=3644112","icon_2x":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/icon-256x256.png?rev=3644112","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/screenshot-1.png?rev=3702823","caption":"The Pinterest check-up: which posts have no big Pinterest image, which are not optimized for Pinterest, and which you have never pinned \u2014 each with a link to open and fix it."},{"src":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/screenshot-2.png?rev=3702823","caption":"\"Make it with AI\" on one post: a Pin title, a description and a cover preview. Nothing is pinned until you choose it."},{"src":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/screenshot-3.png?rev=3702823","caption":"The settings screen: connection status, plan, and today's Pin allowance."},{"src":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/screenshot-4.png?rev=3702823","caption":"Automation settings \u2014 when to pin, which posts, which board."},{"src":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/screenshot-5.png?rev=3702823","caption":"Pin older posts: queue the archive you published before installing, spread over safe posting times."},{"src":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/screenshot-6.png?rev=3702823","caption":"Pins from this site: impressions, saves and clicks for this website's Pins, without leaving WordPress."},{"src":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/screenshot-7.png?rev=3702823","caption":"The Pinterest box in the post editor, with per-post title, description and board."},{"src":"https:\/\/ps.w.org\/burnpedia-pin-scheduler-for-pinterest\/assets\/screenshot-8.png?rev=3702823","caption":"The Activity log: what was pinned, what was skipped, and why."}],"raw_content":"<!--section=description-->\n<p>Writing the post is the work. Remembering to pin it, three days later, is the part that quietly stops happening.<\/p>\n\n<p>This plugin is Pinterest automation for WordPress: it schedules Pinterest Pins for you, automatically, from the content you already publish. Burnpedia Pin Scheduler connects your WordPress site to your <a href=\"https:\/\/burnpedia.app\">Burnpedia<\/a> account; when a post goes live, it builds a Pin from that post's image, title and link and hands it to Burnpedia to publish on a schedule \u2014 to the board you picked, at a sensible time, without you opening Pinterest.<\/p>\n\n<p>It works the same way for a blog post, a page, a WooCommerce product or any other public post type, and it can pin the archive you published before you installed it as well as everything you publish from now on.<\/p>\n\n<p><strong>What it does<\/strong><\/p>\n\n<ul>\n<li>Creates a Pin automatically when a post is published \u2014 or only for the posts you tick.<\/li>\n<li>Pins posts, pages, WooCommerce products and any other public post type you switch on.<\/li>\n<li>Uses the featured image, or the first image in the post if there is no featured image.<\/li>\n<li>Makes up to six Pins from one post, each using a different photograph, a day apart.<\/li>\n<li>Designs a cover from the post's title when the post has no image at all \u2014 free, and at the size Pinterest likes.<\/li>\n<li>Sends the Pin to one fixed board, a board per category, or a board named after your site. A board that does not exist yet is created for you.<\/li>\n<li>Writes the Pin title and description from templates with <code>{title}<\/code>, <code>{excerpt}<\/code>, <code>{site}<\/code> and <code>{categories}<\/code> tags \u2014 editable per post.<\/li>\n<li>Adds UTM campaign tags to the link (<code>utm_source=pinterest<\/code>\u2026) so Pinterest traffic shows up in Google Analytics or whatever you use. Links that are already tagged are left alone.<\/li>\n<li>Schedules with a delay, so your caches and CDN are warm before Pinterest fetches the image.<\/li>\n<li>Retries by itself when something goes wrong, and waits for the reset when you have used up the day's allowance.<\/li>\n<li>Bulk-pins the posts you published before installing, spread over safe best-time slots rather than sent in one burst.<\/li>\n<li>Runs a free <strong>Pinterest check-up<\/strong> of every post: which posts have no big, tall image for Pinterest, which are not optimized for Pinterest (a title Pinterest would cut, a description too short to be found, an image with no alt text) and which posts you have never pinned \u2014 each one listed with a link to open the post and fix it.<\/li>\n<li>For any post you choose, can write a new Pin title and description and make a cover image with AI, using AI credit \u2014 shown as a preview first, and pinned only when you say so. Optional.<\/li>\n<li>Reports impressions, saves and link clicks for the Pins from this site. The site total is on every plan, free included; the per-post breakdown, next to each post in the posts list, is on the paid plans.<\/li>\n<li>Shows what happened, per post, in an Activity log \u2014 including the posts it skipped and why.<\/li>\n<li>Works in the block editor and the classic editor; the per-post Pinterest panel appears in both.<\/li>\n<\/ul>\n\n<p><strong>Works on the free plan<\/strong><\/p>\n\n<p>Nothing here is locked by the plugin: no trial, no time limit, no feature switched off until you pay us for the plugin. A free Burnpedia account publishes up to <strong>3 Pins a day<\/strong>, and every part of the publishing side \u2014 automatic pinning, boards, templates, UTM tags, scheduling, retries, bulk-pinning the backlog, the Activity log \u2014 works on it.<\/p>\n\n<p>One reporting feature is paid: the <strong>per-post<\/strong> breakdown of how each post's Pins are doing. The site-wide total is on every plan, free included. Paid plans also raise the daily allowance. AI-written Pin copy and AI images use AI credit: paid plans include some every day, and anyone can buy it \u2014 no plan needed \u2014 as a one-time bundle. See <a href=\"https:\/\/burnpedia.app\/pricing\">burnpedia.app\/pricing<\/a>.<\/p>\n\n<p><strong>You keep your Pinterest password<\/strong><\/p>\n\n<p>The plugin never sees your Pinterest credentials. You connect Pinterest once inside Burnpedia, on Pinterest's own login screen, over the official Pinterest API.<\/p>\n\n<p><strong>Open source<\/strong><\/p>\n\n<p>The plugin is GPL. Its source, and the API it talks to, are documented at <a href=\"https:\/\/burnpedia.app\/developers\">burnpedia.app\/developers<\/a>.<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin is a client for <strong>Burnpedia<\/strong>, a Pinterest scheduling service run by Burnpedia at <a href=\"https:\/\/burnpedia.app\">https:\/\/burnpedia.app<\/a>. The plugin cannot work without it: WordPress has no way to publish to Pinterest on its own, and Burnpedia is what holds the Pinterest connection.<\/p>\n\n<p><strong>Nothing is sent anywhere until you ask for it.<\/strong> With no key saved, the plugin makes exactly one kind of outbound request, and only after you press a button for it \u2014 the one-press connection described immediately below. Nothing happens on activation, and nothing happens on its own.<\/p>\n\n<p><strong>Connecting this site in one press (optional).<\/strong> On the <strong>Connection<\/strong> screen you can press <strong>Connect this site to Burnpedia<\/strong> instead of copying an API key by hand. When you press it:<\/p>\n\n<ul>\n<li>Your browser opens <code>https:\/\/burnpedia.app\/connect\/wordpress<\/code>, carrying the address of this site and its title, so that the approval screen can name the site you are about to connect. It also carries a random one-time request ID and a fingerprint of a secret that never leaves your server.<\/li>\n<li>After you approve it there, this site makes one <code>POST https:\/\/burnpedia.app\/api\/site-connect\/claim<\/code> request, sending that request ID and the secret, and receives an API key which is saved for you. The key is never shown in your browser.<\/li>\n<li>The request expires after fifteen minutes and can be collected only once. If you press Cancel, or never approve it, nothing is sent and nothing is created.<\/li>\n<li>You never have to use it: pasting a key by hand still works exactly as before, and is the way to connect a site that cannot reach the internet.<\/li>\n<\/ul>\n\n<p>Once a key is saved, the plugin contacts <code>https:\/\/burnpedia.app\/api\/v1<\/code> in these situations:<\/p>\n\n<ol>\n<li><strong>When you open the plugin's settings screen or press \"Check connection\"<\/strong> \u2014 a <code>GET \/api\/v1\/me<\/code> request that returns your Burnpedia plan, the Pinterest accounts connected to it, how much of today's Pin allowance you have used and when it resets, and \u2014 only while a Pro trial is running \u2014 how many days of it are left together with a short-lived link that opens checkout with the plan already chosen. Sent: your API key. Nothing new is sent for any of that; it is the same request, answered with more. The post editor reads the same answer (from a five-minute copy, so opening posts does not repeat the request) to decide whether to offer an AI cover and to show its price and your AI points balance. The <strong>Pinterest check-up<\/strong> tab reads it too, for your AI points, the price of making a post's Pin with AI, and the AI credit bundles Burnpedia sells with their prices; nothing new is sent for it.<\/li>\n<li><strong>When you press \"Load my boards\"<\/strong> \u2014 a <code>GET \/api\/v1\/boards<\/code> request. Sent: your API key.<\/li>\n<li><strong>When a post is published (with automatic pinning on), or you press \"Pin this post now\"<\/strong> \u2014 a <code>POST \/api\/v1\/pins<\/code> request. Sent: your API key, the Pin title, the Pin description, the post's public permalink, the URL of the post's image, the board name or id, and the time the Pin should be published. If the post has no image and you have left \"design a cover from its title\" switched on, no image URL is sent and a flag is sent instead, asking Burnpedia to design the cover from the title above. If you also switched on \"let Burnpedia generate one with AI\", that same flag asks for the cover to be drawn over a generated photograph, which spends AI points on your Burnpedia account; if it cannot be generated you get the free designed cover instead and are not charged. Nothing extra about your site is transmitted for either.<\/li>\n<li><strong>When you open the \"Pins from this site\" tab<\/strong> \u2014 a <code>GET \/api\/v1\/pins<\/code> request. Sent: your API key and this site's address, so that Burnpedia returns only the Pins that link to this website rather than every Pin on your account.<\/li>\n<li><strong>When you open the \"Pins from this site\" tab, or the posts list in WordPress<\/strong> \u2014 a <code>GET \/api\/v1\/analytics\/site<\/code> request. Sent: your API key and this site's address. It returns the impressions, saves and clicks Burnpedia has already recorded for your Pins; it does not ask Pinterest anything, so it cannot use up your Pinterest rate limit.<\/li>\n<li><p><strong>When you press \"Make a preview\" under \"Try an AI cover\" in the post editor<\/strong> \u2014 a <code>POST \/api\/v1\/covers<\/code> request. Sent: your API key, the Pin title, the post's public permalink, and a flag asking for an AI photograph. It uses AI points on your Burnpedia account (the panel shows the cost and your balance before you press it) and creates no Pin: the picture is shown to you, and it is pinned only if you then press \"Pin with this cover\", which sends the Pin request described above with that picture's URL. If the picture cannot be made you are not charged.<\/p><\/li>\n<li><p><strong>When you press \"Scan all posts\" on the Pinterest check-up tab<\/strong> \u2014 <code>POST \/api\/v1\/pinned-status<\/code> requests, up to 500 addresses each. Sent: your API key and the public addresses (permalinks) of your published posts that this plugin has not pinned yet. It returns, for each address, whether it was ever pinned by your Burnpedia account or is on your connected Pinterest account. Every other check-up result \u2014 picture size, alt text, title length, description \u2014 is worked out inside WordPress and is not sent anywhere. With no key saved, nothing is sent and the check-up only uses this plugin's own records.<\/p><\/li>\n<li><strong>When you press \"Make it with AI\" on a post in the Pinterest check-up<\/strong> \u2014 a <code>POST \/api\/v1\/copy<\/code> request, then the <code>POST \/api\/v1\/covers<\/code> request described in item 6. Sent to <code>\/copy<\/code>: your API key, the post's title, its public permalink, and its excerpt if it has one. It returns a Pin title and description, which are saved in that post's own Pin fields, and it uses AI points (the tab shows the price and your balance before you press). Nothing is pinned until you press \"Pin with this cover\". If the words cannot be written, nothing is charged and no picture is attempted.<\/li>\n<\/ol>\n\n<p>The <strong>Buy AI credit<\/strong> buttons on the check-up tab are ordinary links to <code>https:\/\/burnpedia.app\/buy-credit<\/code>, carrying the chosen bundle and this plugin's name so the purchase can be credited to it; the plugin itself sends nothing when you click one.<\/p>\n\n<p>Every request also carries a header naming the plugin and its version (for example <code>wordpress\/1.0.0<\/code>), the same way a browser identifies itself, so that support and compatibility questions can be answered.<\/p>\n\n<p>No visitor data, no analytics, no usage statistics and no content beyond the fields listed above are transmitted. The plugin has no telemetry of its own: it never reports your traffic, your other plugins, or anything about your visitors. Your site's address is sent as part of a Pin's own link, when looking up this site's Pins as described above, in the check-up's posts' addresses when you run it, and \u2014 if you use it \u2014 on the one-press connection screen so that it can name the site you are approving.<\/p>\n\n<p>Your use of the service is covered by Burnpedia's terms and privacy policy:<\/p>\n\n<ul>\n<li>Terms of service: <a href=\"https:\/\/burnpedia.app\/terms\">https:\/\/burnpedia.app\/terms<\/a><\/li>\n<li>Privacy policy: <a href=\"https:\/\/burnpedia.app\/privacy\">https:\/\/burnpedia.app\/privacy<\/a><\/li>\n<\/ul>\n\n<p>Pinterest itself is contacted by Burnpedia's servers, not by your site. Note that Pinterest downloads your image <strong>from your own site<\/strong>, so the image URL has to be publicly reachable \u2014 the settings screen warns you when it looks like it is not.<\/p>\n\n<p><strong>The install count (optional, off by default).<\/strong> WordPress.org does not tell\nplugin authors how many sites are running their plugin \u2014 for this plugin it\npublishes no figure at all. If you switch this on under <strong>Burnpedia Pins \u2192 Connection<\/strong>, this site\nsends a short report:<\/p>\n\n<ul>\n<li><code>POST https:\/\/burnpedia.app\/api\/plugin-insights<\/code> \u2014 once when you switch it on,\nthen at most once a week while an administrator is using wp-admin, once if you\ndeactivate the plugin, and once if you delete it. Sends exactly nine things: a\nrandom ID generated on this site, which plugin and which version, which of\nthose four events it is, your WordPress version, your PHP version, your site\nlanguage, whether this is a multisite network, and whether an API key is saved\n(true or false \u2014 never the key). Receives: nothing your site uses.<\/li>\n<\/ul>\n\n<p><strong>Your website address is not in that report and is never sent, so we cannot\ntell which website you are.<\/strong> The random ID is made up on your server and means\nnothing outside it. Switch the setting off and the ID is deleted, so counting\nstops and a later change of mind cannot be joined to it. It is off until you\nchoose it, no feature depends on it, and nothing about any reader or any\nlogged-in user is in it.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install and activate the plugin.<\/li>\n<li>Go to <strong>Burnpedia \u2192 Connection<\/strong> and press <strong>Connect this site to Burnpedia<\/strong>. Approve it in the tab that opens \u2014 a free account takes a moment to make if you do not have one \u2014 and this site collects its own key. There is nothing to copy or paste. You are then asked one question, <em>\"create a Pin when I publish?\"<\/em>, and that is the setup.<\/li>\n<\/ol>\n\n<p>Publish a post to try it. The <strong>Activity<\/strong> tab shows what happened.<\/p>\n\n<p><strong>Connecting by hand instead.<\/strong> If your site cannot reach the internet, or you would rather do it yourself:<\/p>\n\n<ol>\n<li>Create a free account at <a href=\"https:\/\/burnpedia.app\">burnpedia.app<\/a> and connect your Pinterest account there (this happens on Pinterest's own login screen).<\/li>\n<li>In Burnpedia, open <strong>Dashboard \u2192 API<\/strong> and create an API key. It is shown once \u2014 copy it.<\/li>\n<li>In WordPress, go to <strong>Burnpedia \u2192 Connection<\/strong>, paste the key and save.<\/li>\n<li>Open the <strong>Automation<\/strong> tab, turn on \"Create a Pin automatically when a post is published\", choose your board, and save.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"do%20i%20need%20a%20burnpedia%20account%3F\"><h3>Do I need a Burnpedia account?<\/h3><\/dt>\n<dd><p>Yes. This plugin is a client for Burnpedia, and it cannot publish to Pinterest without one \u2014 WordPress has no way to post to Pinterest on its own. Creating one is free, takes a moment, and needs no card. Pinterest itself is connected inside Burnpedia, on Pinterest's own login screen.<\/p><\/dd>\n<dt id=\"does%20this%20automatically%20post%20to%20pinterest%20when%20i%20publish%3F\"><h3>Does this automatically post to Pinterest when I publish?<\/h3><\/dt>\n<dd><p>Yes \u2014 that is the whole point. Turn on automatic pinning under <strong>Automation<\/strong>, and every post you publish becomes a scheduled Pin. You can also pin a single post by hand from the post editor, including old ones.<\/p><\/dd>\n<dt id=\"can%20i%20schedule%20pins%20instead%20of%20posting%20them%20immediately%3F\"><h3>Can I schedule Pins instead of posting them immediately?<\/h3><\/dt>\n<dd><p>Yes. Pins are scheduled by default, with a delay you choose, so your caches and CDN are warm before Pinterest fetches the image. Straight-away publishing is one setting away.<\/p><\/dd>\n<dt id=\"do%20i%20need%20a%20paid%20account%3F\"><h3>Do I need a paid account?<\/h3><\/dt>\n<dd><p>No. A free Burnpedia account publishes up to 3 Pins a day, and every feature of this plugin works on it. Paid plans exist for people publishing more than that, but nothing in the plugin is locked behind them.<\/p><\/dd>\n<dt id=\"what%20happens%20when%20i%20hit%203%20pins%20a%20day%20on%20the%20free%20plan%3F\"><h3>What happens when I hit 3 Pins a day on the free plan?<\/h3><\/dt>\n<dd><p>Nothing is lost. The Pin stays queued and the plugin retries it after the daily allowance resets, so it publishes the next day instead of failing. The Activity tab shows it waiting, and says when the allowance comes back in your site's own timezone.<\/p><\/dd>\n<dt id=\"does%20this%20need%20my%20pinterest%20password%3F\"><h3>Does this need my Pinterest password?<\/h3><\/dt>\n<dd><p>No, and it never asks for one. Pinterest is connected inside Burnpedia through Pinterest's official OAuth login, on Pinterest's own domain.<\/p><\/dd>\n<dt id=\"why%20did%20my%20post%20not%20get%20pinned%3F\"><h3>Why did my post not get pinned?<\/h3><\/dt>\n<dd><p>The <strong>Activity<\/strong> tab gives the reason for every post it skipped. The usual ones are: the post is password protected, its category is excluded, or the day's Pin allowance is used up (in which case it retries automatically after the reset). A post with no image is no longer one of them by default \u2014 it gets a designed cover instead.<\/p><\/dd>\n<dt id=\"what%20happens%20to%20a%20post%20that%20has%20no%20image%3F\"><h3>What happens to a post that has no image?<\/h3><\/dt>\n<dd><p>It gets a cover designed from its title: the headline set in one of Burnpedia's colour palettes, at 1000x1500. It is free, uses no AI points, and the same post always gets the same cover. Switch it off under <strong>Automation \u2192 Image<\/strong> and such posts are skipped and logged, as they were before.<\/p><\/dd>\n<dt id=\"my%20pins%20fail%20with%20an%20image%20error.\"><h3>My Pins fail with an image error.<\/h3><\/dt>\n<dd><p>Pinterest fetches the image from your server, so the image URL must be reachable from the public internet. Local development sites, sites behind HTTP authentication, and private networks cannot work \u2014 the settings screen shows a warning when it detects one.<\/p><\/dd>\n<dt id=\"can%20i%20pin%20an%20old%20post%3F\"><h3>Can I pin an old post?<\/h3><\/dt>\n<dd><p>Yes, one at a time or in bulk. Open a single post and use <strong>Pin this post now<\/strong> in the Pinterest box; to work through an archive, the <strong>Pin older posts<\/strong> tab lists every published post that has no Pin yet and queues the ones you tick, spread over safe posting slots rather than sent in one burst.<\/p><\/dd>\n<dt id=\"does%20it%20work%20with%20woocommerce%20products%3F\"><h3>Does it work with WooCommerce products?<\/h3><\/dt>\n<dd><p>Yes. Any public post type can be pinned \u2014 WooCommerce products, pages, portfolios, recipes, or any custom post type your theme or plugins register. You choose which ones under <strong>Automation<\/strong>; attachments are excluded on purpose.<\/p><\/dd>\n<dt id=\"does%20it%20work%20with%20the%20block%20editor%20and%20the%20classic%20editor%3F\"><h3>Does it work with the block editor and the classic editor?<\/h3><\/dt>\n<dd><p>Both. The per-post Pinterest panel appears in the block editor sidebar and in the classic editor, and the image is read from the featured image or from the images in the post content either way.<\/p><\/dd>\n<dt id=\"does%20it%20also%20post%20to%20instagram%2C%20facebook%20or%20x%3F\"><h3>Does it also post to Instagram, Facebook or X?<\/h3><\/dt>\n<dd><p>No \u2014 this plugin does Pinterest only, and does it properly. If you need other networks, use a separate plugin for them alongside this one.<\/p><\/dd>\n<dt id=\"does%20it%20show%20pinterest%20analytics%20inside%20wordpress%3F\"><h3>Does it show Pinterest analytics inside WordPress?<\/h3><\/dt>\n<dd><p>Yes. The <strong>Pins from this site<\/strong> tab is a Pinterest analytics screen for the Pins\nthis website published: impressions, saves, and clicks through to your site. The\nsite-wide total is on every plan, free included; the per-post breakdown is on the\npaid plans. The numbers come from Burnpedia's own copy of Pinterest's data, so\nopening the screen never spends your Pinterest rate limit.<\/p><\/dd>\n<dt id=\"can%20i%20see%20how%20my%20pins%20are%20performing%20without%20leaving%20wordpress%3F\"><h3>Can I see how my Pins are performing without leaving WordPress?<\/h3><\/dt>\n<dd><p>Yes. The <strong>Pins from this site<\/strong> tab shows impressions, saves and clicks through to your site. That site-wide total is on every plan, free included.<\/p>\n\n<p>The per-post breakdown \u2014 the same numbers beside each post in the posts list, which answers <em>which<\/em> post Pinterest is sending people to \u2014 is on the paid plans. Either way the numbers come from Burnpedia's own copy of the data, so opening those screens never uses up your Pinterest rate limit. Pinterest reports about two days behind, and the screen says so.<\/p><\/dd>\n<dt id=\"can%20i%20change%20the%20pin%27s%20title%2C%20description%20or%20board%20for%20one%20post%3F\"><h3>Can I change the Pin's title, description or board for one post?<\/h3><\/dt>\n<dd><p>Yes \u2014 all three are in the Pinterest box in the post editor and override the site-wide templates.<\/p><\/dd>\n<dt id=\"does%20it%20pin%20a%20post%20twice%20if%20i%20update%20it%3F\"><h3>Does it pin a post twice if I update it?<\/h3><\/dt>\n<dd><p>No. A post is pinned once. Re-publishing an already-pinned post does nothing; use \"Pin this post now\" if you want another Pin.<\/p><\/dd>\n<dt id=\"which%20post%20types%20can%20it%20pin%3F\"><h3>Which post types can it pin?<\/h3><\/dt>\n<dd><p>Any public post type on your site \u2014 choose them under <strong>Automation<\/strong>. Attachments are excluded on purpose.<\/p><\/dd>\n<dt id=\"does%20it%20work%20with%20custom%20fields%2C%20page%20builders%2C%20or%20a%20headless%20setup%3F\"><h3>Does it work with custom fields, page builders, or a headless setup?<\/h3><\/dt>\n<dd><p>It reads the featured image and the post content, so anything that stores those normally works. The <code>burnpedia_pin_image_url<\/code> and <code>burnpedia_pin_payload<\/code> filters let you supply your own values.<\/p><\/dd>\n<dt id=\"is%20it%20gdpr-relevant%3F\"><h3>Is it GDPR-relevant?<\/h3><\/dt>\n<dd><p>The plugin sends no personal data about your visitors anywhere. It sends the Pin fields listed under \"External services\", and only after you save an API key.<\/p><\/dd>\n<dt id=\"how%20do%20i%20find%20which%20of%20my%20posts%20are%20not%20optimized%20for%20pinterest%3F\"><h3>How do I find which of my posts are not optimized for Pinterest?<\/h3><\/dt>\n<dd><p>Open the <strong>Pinterest check-up<\/strong> tab and press <strong>Scan all posts<\/strong>. It lists every published post with no big, tall image for Pinterest (none at all, narrower than 1000 pixels, or wider than it is tall), every post that is not optimized for Pinterest (a Pin title over 100 characters, which Pinterest cuts off; a description too short to be found; an image with no alt text; pinning switched off) and every post you have never pinned. Each post has a link to view it and to edit it. The scan is free and the picture and text checks never leave your site.<\/p><\/dd>\n<dt id=\"which%20of%20my%20posts%20have%20never%20been%20pinned%3F\"><h3>Which of my posts have never been pinned?<\/h3><\/dt>\n<dd><p>The check-up's <strong>Never pinned by you<\/strong> list. It counts Pins this plugin made, Pins made in your Burnpedia account, and Pins on your connected Pinterest account, including ones you pinned by hand. Pinterest does not tell anyone whether somebody else pinned your page, so the list means never pinned by you. From there, the <strong>Pin older posts<\/strong> tab queues them.<\/p><\/dd>\n<dt id=\"do%20i%20have%20to%20buy%20ai%20credit%20to%20use%20the%20check-up%3F\"><h3>Do I have to buy AI credit to use the check-up?<\/h3><\/dt>\n<dd><p>No. The scan, the lists and the links are free on every plan. AI is optional: \"Make it with AI\" writes a post's Pin title and description and makes a cover preview, using AI points from your Burnpedia account. Paid plans include AI points every day, and anyone can buy a one-time bundle of AI credit \u2014 no plan needed; the tab shows each bundle and its price, as set by Burnpedia.<\/p><\/dd>\n<dt id=\"can%20i%20use%20ai%20points%20on%20a%20post%20that%20already%20has%20a%20photo%3F\"><h3>Can I use AI points on a post that already has a photo?<\/h3><\/dt>\n<dd><p>Yes, if your Burnpedia account has enough AI points. In the post editor the Pinterest panel shows \"Try an AI cover\" with its price and your balance. \"Make a preview\" makes a photograph from the Pin title, with the title set on it, and shows it to you. Nothing is pinned unless you press \"Pin with this cover\", and \"Discard\" throws the preview away. If the picture cannot be made you are not charged, and your post's own photo is never changed. Without enough points the option is not shown.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.31<\/h4>\n\n<ul>\n<li>New: the <strong>Pinterest check-up<\/strong> tab. One press scans every published post and\nlists the ones with no big, tall image for Pinterest, the ones not optimized\nfor Pinterest (a title Pinterest would cut, a description too short, an image\nwith no alt text, pinning switched off) and the ones you have never pinned,\neach with a link to view and edit the post. Free; the picture and text checks\nrun inside WordPress. Large sites scan in steps you can continue.<\/li>\n<li>New: \"Make it with AI\" on any post in the check-up writes its Pin title and\ndescription and makes a cover preview, using AI credit. Nothing is pinned\nuntil you press \"Pin with this cover\". Optional.<\/li>\n<li>New: the check-up shows your AI points and Burnpedia's AI credit bundles with\ntheir prices. Buying credit is optional and needs no plan.<\/li>\n<\/ul>\n\n<h4>1.0.30<\/h4>\n\n<ul>\n<li>Fixed: if the connection to Burnpedia dropped after a Pin had been created but\nbefore the answer reached your site, the automatic retry could create the same\nPin a second time \u2014 and, for an AI cover, use AI points twice. Each Pin is now\nsent with a one-time key, and a retry of that Pin gets back the Pin that was\nalready made instead of a new one.<\/li>\n<\/ul>\n\n<h4>1.0.29<\/h4>\n\n<ul>\n<li>New: \"Try an AI cover\" in the post editor's Pinterest panel. On a post that\nalready has a photo, you can use AI points from your Burnpedia account on a\ncover made for it: a photograph made from the Pin title, with the title set on\nit. You see a preview first, with the cost and your balance, and it is pinned\nonly if you press \"Pin with this cover\". It is shown only when your account has\nenough AI points.<\/li>\n<li>If a preview cannot be made you are not charged, and your post's own photo is\nnever changed.<\/li>\n<\/ul>\n\n<h4>1.0.28<\/h4>\n\n<ul>\n<li>Fixed: with automatic pinning switched off, which is how the plugin starts,\n\"Pin older posts\" marked posts in a category you had excluded as ready, and\ncould queue them. Excluded categories are now respected whether automatic\npinning is on or off.<\/li>\n<li>Every queued post is now checked again just before it is sent. A post you\nexclude or switch off after it was queued \u2014 including one an earlier version\nhad already queued \u2014 is skipped, and the Activity log says why.<\/li>\n<li>\"Send a test Pin\" no longer picks a post from an excluded category, or a post\nyou switched off.<\/li>\n<li>Fixed: the Activity log showed every post queued by \"Pin older posts\" as an\nerror. It now says queued.<\/li>\n<li>Fixed: when a post has no picture and AI images are on, the plugin now waits\nlong enough for Burnpedia to finish making the image. Before, a slow image\ncould make the plugin give up and try again, which could create a second Pin\nand use AI points twice.<\/li>\n<li>Fixed: if Burnpedia briefly cannot make a free designed cover, the post is now\ntried again later instead of being marked as failed for good. An AI cover is\nnot retried automatically, because each attempt would use AI points again.<\/li>\n<\/ul>\n\n<h4>1.0.27<\/h4>\n\n<ul>\n<li>Fixed the site totals on \"Pins from this site\". They were adding up only your\n200 most recent Pins, which on a site with more than that showed a number far\nsmaller than the truth \u2014 and because the newest Pins are the ones Pinterest has\nhad least time to show, the figure could read as almost nothing while the Pins\nwere in fact doing fine. The totals now cover every Pin for the site.<\/li>\n<li>The table still lists your most recent Pins, and now says so in one line when\nthere are more Pins than it shows.<\/li>\n<li>Your Pin count on that screen is now the real number of Pins for the site,\nrather than however many fitted in the table.<\/li>\n<\/ul>\n\n<h4>1.0.26<\/h4>\n\n<ul>\n<li>Names the Pinterest analytics this plugin has shown since 1.0.10. The feature\nis unchanged; the listing simply never used the words people search for, so\nnobody looking for \"Pinterest analytics\" in WordPress could find it.<\/li>\n<li>The new entry states the same free\/paid split as the rest of the page: the\nsite-wide total on every plan, the per-post breakdown on the paid plans.<\/li>\n<li>No code change.<\/li>\n<\/ul>\n\n<h4>1.0.25<\/h4>\n\n<ul>\n<li>Corrected the listing: the per-post breakdown of how each post's Pins are\ndoing is on the paid plans, and this page said it was free. The site-wide\ntotal is on every plan, free included, and always was. Everything on the\npublishing side - automatic pinning, boards, templates, UTM tags, scheduling,\nretries, the backlog run and the Activity log - is unchanged and still free.<\/li>\n<li>No code change.<\/li>\n<\/ul>\n\n<h4>1.0.24<\/h4>\n\n<ul>\n<li>New: <strong>Copy diagnostics<\/strong> on the Activity tab. One button gives you a\npaste-able summary of everything a support answer normally has to ask for\nfirst - WordPress and PHP versions, whether the scheduler is running, your\nsettings, and the last ten log entries.<\/li>\n<li>Your API key is never in it, and nothing is sent anywhere: the block is built\non your own site and you choose where to paste it.<\/li>\n<\/ul>\n\n<h4>1.0.23<\/h4>\n\n<ul>\n<li>The plugin's WordPress.org listing now describes what it already does in the\nwords people actually search for: pinning pages and WooCommerce products as\nwell as posts, working through an archive of older posts in bulk, the Pinterest\nimpressions, saves and clicks it reports, and the UTM tags it adds for Google\nAnalytics.<\/li>\n<li>Seven new questions answered on the listing, including the two that matter most\nbefore you install: yes, a free Burnpedia account is required, and no, hitting\nthe daily Pin allowance does not lose a Pin - it waits for the reset.<\/li>\n<li>No functional change. Nothing in the plugin itself behaves differently.<\/li>\n<\/ul>\n\n<h4>1.0.22<\/h4>\n\n<ul>\n<li>Once your site has been publishing Pins for a couple of weeks and they are\nbeing seen on Pinterest, the Pins tab asks \u2014 once \u2014 how it is going.<\/li>\n<li>Two links, side by side: tell us something is wrong, or leave a review.\nNothing is offered in return, and \"No thanks\" means it never comes back.<\/li>\n<\/ul>\n\n<h4>1.0.21<\/h4>\n\n<ul>\n<li>During a Pro trial the Connection screen now says how many days are left and\ngives you one button to keep it, instead of describing your plan as Starter.<\/li>\n<li>The button opens checkout with the plan already chosen \u2014 the link is created\nby Burnpedia, expires within a day, and never appears if no trial is running.<\/li>\n<\/ul>\n\n<h4>1.0.20<\/h4>\n\n<ul>\n<li>When the day's Pin allowance runs out, the message now says exactly when it\ncomes back \u2014 in your site's own timezone, not ours.<\/li>\n<li>The wording comes from Burnpedia, so it stays correct without updating the\nplugin, and it no longer offers an upgrade for the publishing-pace limit,\nwhich is the same on every plan.<\/li>\n<\/ul>\n\n<h4>1.0.19<\/h4>\n\n<ul>\n<li>New: <strong>Connect this site to Burnpedia<\/strong> \u2014 one button on the Connection screen.\nApprove it in the tab that opens and your site collects its own API key. There\nis nothing to copy, nothing to paste, and the key is never shown in a browser.<\/li>\n<li>Setup is now two steps instead of five, and finishes with one plain question:\ncreate a Pin when I publish? Nothing is pinned until you answer yes.<\/li>\n<li>Pasting a key by hand still works exactly as before, and is still the way to\nconnect a site that cannot reach the internet.<\/li>\n<\/ul>\n\n<h4>1.0.18<\/h4>\n\n<ul>\n<li>New: an optional install count under Burnpedia Pins \u2192 Connection. WordPress.org publishes no\ninstall figure for this plugin, so we genuinely cannot tell how many sites use\nit. Switch this on and your site sends a random ID once a week so it can be\ncounted. Your website address is never sent. It is off unless you turn it on,\nnothing depends on it, and turning it off deletes the ID.<\/li>\n<\/ul>\n\n<h4>1.0.17<\/h4>\n\n<ul>\n<li>\"Pins from this site\" now explains what the numbers mean, in plain English \u2014\nincluding when a lot of Pins went out on one day, which is the usual reason\nreach per Pin drops.<\/li>\n<li>Every row on that screen gets a \"Design a Pin\" link, the same one the Posts\nlist has.<\/li>\n<li>The wording comes from Burnpedia, so it stays correct without updating the\nplugin.<\/li>\n<\/ul>\n\n<h4>1.0.16<\/h4>\n\n<ul>\n<li>Safer pacing: \"Pin older posts\" now skips days your Pinterest account has\nalready filled, instead of adding to them. Running a backfill twice used to\nstack both runs onto the same days.<\/li>\n<li>Burnpedia enforces the same daily limit on its side, so a Pin over the limit\nis moved to the next free day rather than published in a burst. Publishing a\nlot in one day sharply reduces how many people see each Pin.<\/li>\n<li>Nothing changes for a normal day, and no setting moved.<\/li>\n<\/ul>\n\n<h4>1.0.15<\/h4>\n\n<ul>\n<li>New: \"Pins per post\" (1-6) under Automation. Each Pin uses a different\nphotograph from the post and they go out a day apart, which is better\nPinterest practice than one Pin per page.<\/li>\n<li>A post only has as many Pins as it has pictures. Four sizes of the same\nphotograph count as one photograph, so you never get the same picture\ntwice at different sizes.<\/li>\n<li>Raising it does not raise your daily rate: \"Pin older posts\" queues fewer\nposts a day to keep the Pins-a-day figure you chose, and the estimate on\nthat screen now counts Pins rather than posts.<\/li>\n<li>AI covers: if you have \"let Burnpedia generate one with AI\" switched on, a\npost with no picture now gets your headline set ON the generated photograph,\nrather than a photograph with no words on it.<\/li>\n<li>It is one request instead of two. Before, the picture was paid for in the\nfirst request and pinned in the second, so a failure in between could charge\nyou for a picture that never became a Pin.<\/li>\n<li>If the picture cannot be generated - most often because you are out of AI\npoints - you get the free designed cover instead, the post is still pinned,\nand you are not charged.<\/li>\n<\/ul>\n\n<h4>1.0.14<\/h4>\n\n<ul>\n<li>New: a post with no picture now gets a designed cover instead of being\nskipped. Its title is set in one of Burnpedia's colour palettes at 1000x1500,\nthe size Pinterest likes, and the same post always gets the same cover.<\/li>\n<li>It is free and uses no AI points. It is on by default and can be switched off\nunder Automation - Image.<\/li>\n<li>If AI images are switched on and a generation fails - most often because the\naccount is out of points - the post now gets a designed cover instead of no\nPin at all. Both are written to the Activity log.<\/li>\n<li>The \"Pin older posts\" list no longer marks image-less posts as not ready when\na cover or an AI image would be made for them.<\/li>\n<li>New: a \"Design a Pin\" link beside every post in the Posts list, and one on\nthe plugin's own settings screen. It opens Burnpedia's free Pin maker with\nthat post's headline already filled in - no account needed, nothing is sent.<\/li>\n<\/ul>\n\n<h4>1.0.13<\/h4>\n\n<ul>\n<li>New: the \"Pin older posts\" tab now tells you how many published posts have no\nPin - on the tab itself, so you can see it without opening it - and roughly how\nmany days it would take to work through them.<\/li>\n<li>Each post in the list says whether it is ready, or why it is not: no image\nPinterest can use, in a category you excluded, or switched off by hand. You can\nno longer tick a post that would immediately be skipped.<\/li>\n<li>Long archives now page, and there is a tick-all for the page you are on.<\/li>\n<li>This works on every plan, including the free one. A bigger plan clears the\nbacklog faster; nothing here is locked.<\/li>\n<li>New: when your Pins are stuck because WordPress is not running its scheduler,\nthere is now a \"Run it now\" button next to the warning. It sends the waiting\nPins straight away, so you are not stuck until your host answers.<\/li>\n<li>The button only appears when something is actually overdue, sends up to five\nPins per press, and can be pressed once a minute. It is a nudge, not a fix -\nthe cron line under it is still what stops the problem coming back.<\/li>\n<\/ul>\n\n<h4>1.0.12<\/h4>\n\n<ul>\n<li>New: if you are publishing far more Pins per day than is safe for a Pinterest\naccount, the plugin's settings screen now says so, with the number you actually\npublished and what we recommend. Pinterest has suspended accounts for high-volume\npublishing, and a suspension cannot be undone by reconnecting.<\/li>\n<li>You can close the notice. It comes back after a few days if the pace continues,\nand straight away if it gets faster.<\/li>\n<\/ul>\n\n<h4>1.0.11<\/h4>\n\n<ul>\n<li>Fixed: the \"Pinterest account\" setting only ever offered one choice. If you have\nseveral Pinterest accounts connected to Burnpedia, all of them are now listed by\nusername, and the one you picked is remembered.<\/li>\n<li>If the account this site was set to publish to is disconnected on Burnpedia, the\nsetting now says so instead of quietly falling back to your default account.<\/li>\n<li>Internal: the Burnpedia API transport is now a single shared file, so both\nBurnpedia plugins handle errors, rate limits and daily-limit resets identically.<\/li>\n<li>Upgrade links now say which plugin they came from.<\/li>\n<\/ul>\n\n<h4>1.0.10<\/h4>\n\n<ul>\n<li>The \"Pins from this site\" tab now shows what your Pins actually did: impressions, saves, and clicks through to your site - for the whole site, and per Pin.<\/li>\n<li>The posts list shows the same numbers next to each post, so you can see which posts Pinterest is actually sending people to without leaving WordPress.<\/li>\n<li>Pinterest reports about two days behind, and the screen says so rather than showing the missing days as zero.<\/li>\n<li>A Pin published this week reads \"No numbers yet\" instead of \"0 impressions\" - they are different things.<\/li>\n<li>Per-post numbers are on the paid plans; the site total is on every plan, including free.<\/li>\n<li>None of it costs you anything on Pinterest's side: the numbers come from Burnpedia's own copy, so opening these screens can never slow down or rate-limit your account.<\/li>\n<\/ul>\n\n<h4>1.0.9<\/h4>\n\n<ul>\n<li>New tab: <strong>Pins from this site<\/strong>. Everything Burnpedia holds for this website - what went out, when, to which board, and what is still queued - with a link straight to the live Pin.<\/li>\n<li>It reads from Burnpedia rather than from the plugin's own log, so it shows Pins that published after the log was written, Pins you made in the Burnpedia composer for this site, and the real Pinterest link once a Pin is live.<\/li>\n<li>Only this site's Pins are listed, even if your Burnpedia account also schedules for other websites.<\/li>\n<li>New, and off until you turn it on: <strong>when a post has no image, Burnpedia can generate one with AI<\/strong>. Until now a post with no featured image and no image in its content produced no Pin at all - it was skipped and logged. Automation tab, under Image.<\/li>\n<li>It spends AI points from your Burnpedia account, one generation per image-less post, and every one is written to the Activity log so you can see what was used. Nothing is charged when a generation fails.<\/li>\n<li>You get a photographic background with no text on it. Posts that already have an image are never touched.<\/li>\n<li>Per post, too: a post with no image shows the choice right in the editor sidebar, so you can spend on one post without turning it on everywhere - or skip one on a site where it is on.<\/li>\n<li>If the AI provider has a bad moment the Pin is retried on the usual schedule instead of being skipped for good.<\/li>\n<li>Clearer messages when Burnpedia says you are out of AI points, or when AI is switched off for your login by an account owner.<\/li>\n<\/ul>\n\n<h4>1.0.8<\/h4>\n\n<ul>\n<li>New: a \"WordPress scheduler\" panel on the Connection tab. Publishing a post does not send a Pin immediately - it hands the job to WordPress's own scheduler - and on some hosts that scheduler never runs. Until now the plugin said nothing and the Pins simply sat there.<\/li>\n<li>If Pins are waiting, it says how many and how long the oldest has been overdue, and gives you the exact cron line to hand your host.<\/li>\n<li>If your host already runs WordPress's scheduler from a real cron job, it says so and stays quiet. Having DISABLE_WP_CRON set is not treated as a problem on its own.<\/li>\n<li>The warning appears on the plugin's other tabs only when something is actually wrong.<\/li>\n<\/ul>\n\n<h4>1.0.7<\/h4>\n\n<ul>\n<li>New \"Pin older posts\" tab: pick posts you published before installing the plugin and queue them in one go. They are spread across the same best-time slots the Burnpedia scheduler uses (9am, 1pm, 5pm, 8pm) and sent one at a time - selecting 200 posts creates Pins at exactly the same rate as selecting 2, only for longer.<\/li>\n<li>Nothing about it is locked to a plan. Every plan can queue the same posts; your plan decides how quickly the queue drains, and when the daily allowance runs out the queue waits for the reset instead of failing.<\/li>\n<li>You can stop a run at any time; posts already sent keep their Pins.<\/li>\n<\/ul>\n\n<h4>1.0.6<\/h4>\n\n<ul>\n<li>Your plan card now shows the same wording Burnpedia itself uses \u2014 \"1 of 3 Pins used today on the Starter plan\" \u2014 instead of a number the plugin had to phrase on its own. It stays correct through a plan change or a trial without waiting for a plugin update.<\/li>\n<li>When today's allowance is actually used up, the plan card links to the plans page. It appears only when the allowance is spent and only when there is a higher plan to move to; nothing in this plugin is locked.<\/li>\n<li>\"Daily pin limit reached\" now tells you where to go if you want more Pins today.<\/li>\n<li>Fixed: the plugin reported its version as 1.0.4 in 1.0.5, which could serve stale admin CSS\/JS from cache after an update.<\/li>\n<\/ul>\n\n<h4>1.0.5<\/h4>\n\n<ul>\n<li>Tested with WordPress 7.1. Removes the \"has not been tested with your current version of WordPress\" warning on the plugin screen.<\/li>\n<li>No functional change.<\/li>\n<\/ul>\n\n<h4>1.0.4<\/h4>\n\n<ul>\n<li>New: a \"Coming next\" table on the Activity tab. It shows Pins that are queued, waiting for tomorrow's allowance, or retrying after a problem \u2014 with when each one is due. Previously only finished attempts appeared, so a Pin on its way looked like nothing happening.<\/li>\n<li>An overdue Pin now says so, and says why: WordPress has not run its scheduler.<\/li>\n<li>Success rows show the destination board and link straight to the Pin.<\/li>\n<li>A post skipped for having no image now offers a button to go and add one.<\/li>\n<\/ul>\n\n<h4>1.0.3<\/h4>\n\n<ul>\n<li>New: \"Send a test Pin\" on the Connection tab. It runs the real publishing path without sending anything and reports every step \u2014 which post it would use, the image URL it resolved, the board, the exact title and description, whether your site is reachable from the internet, and whether WordPress is running its scheduler. A second button then sends it for real.<\/li>\n<li>The check uses the same code that publishes, so it cannot pass while publishing fails.<\/li>\n<li>A test Pin is a real Pin: it appears on your Pinterest account and uses one of the day's Pins. The button says so before you press it.<\/li>\n<\/ul>\n\n<h4>1.0.2<\/h4>\n\n<ul>\n<li>New: a first-run checklist on the Connection tab \u2014 API key, Pinterest account, board, automatic pinning, first Pin \u2014 so you can see at a glance which step is still missing.<\/li>\n<li>New: a dismissible notice on the plugin's own screens when automatic pinning is off and posts have been published since you connected. Previously nothing said the switch was off, and posts went out with no Pin and no explanation.<\/li>\n<li>The \"Getting started\" steps now show a distinct \"checking\u2026\" state while your account is being looked up, instead of showing a red cross for something we have not asked about yet.<\/li>\n<li>Larger touch targets and 16px form text on touch devices, so wp-admin no longer zooms when you tap a field on a phone.<\/li>\n<\/ul>\n\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>Stricter capability checks on the plugin's own admin REST routes.<\/li>\n<li>\"Pin this post now\" now requires the publish capability for the post type, not only edit access to the post.<\/li>\n<li>A post that is not published and publicly viewable can no longer be pinned by hand.<\/li>\n<li>Reading the connection status and listing boards now require the manage_options capability.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First release.<\/li>\n<\/ul>","raw_excerpt":"Auto post to Pinterest: every post, page or product you publish becomes a scheduled Pin \u2014 image, title and link \u2014 on the board you choose.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/351589","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=351589"}],"author":[{"embeddable":true,"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/lalokupfer"}],"wp:attachment":[{"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=351589"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=351589"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=351589"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=351589"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=351589"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/br.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=351589"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}