Burnpedia Pin Scheduler for Pinterest

Registro de alterações

1.0.31

• New: the Pinterest check-up tab. One press scans every published post and
  lists the ones with no big, tall image for Pinterest, the ones not optimized
  for Pinterest (a title Pinterest would cut, a description too short, an image
  with no alt text, pinning switched off) and the ones you have never pinned,
  each with a link to view and edit the post. Free; the picture and text checks
  run inside WordPress. Large sites scan in steps you can continue.
• New: “Make it with AI” on any post in the check-up writes its Pin title and
  description and makes a cover preview, using AI credit. Nothing is pinned
  until you press “Pin with this cover”. Optional.
• New: the check-up shows your AI points and Burnpedia’s AI credit bundles with
  their prices. Buying credit is optional and needs no plan.

1.0.30

• Fixed: if the connection to Burnpedia dropped after a Pin had been created but
  before the answer reached your site, the automatic retry could create the same
  Pin a second time — and, for an AI cover, use AI points twice. Each Pin is now
  sent with a one-time key, and a retry of that Pin gets back the Pin that was
  already made instead of a new one.

1.0.29

• New: “Try an AI cover” in the post editor’s Pinterest panel. On a post that
  already has a photo, you can use AI points from your Burnpedia account on a
  cover made for it: a photograph made from the Pin title, with the title set on
  it. You see a preview first, with the cost and your balance, and it is pinned
  only if you press “Pin with this cover”. It is shown only when your account has
  enough AI points.
• If a preview cannot be made you are not charged, and your post’s own photo is
  never changed.

1.0.28

• Fixed: with automatic pinning switched off, which is how the plugin starts,
  “Pin older posts” marked posts in a category you had excluded as ready, and
  could queue them. Excluded categories are now respected whether automatic
  pinning is on or off.
• Every queued post is now checked again just before it is sent. A post you
  exclude or switch off after it was queued — including one an earlier version
  had already queued — is skipped, and the Activity log says why.
• “Send a test Pin” no longer picks a post from an excluded category, or a post
  you switched off.
• Fixed: the Activity log showed every post queued by “Pin older posts” as an
  error. It now says queued.
• Fixed: when a post has no picture and AI images are on, the plugin now waits
  long enough for Burnpedia to finish making the image. Before, a slow image
  could make the plugin give up and try again, which could create a second Pin
  and use AI points twice.
• Fixed: if Burnpedia briefly cannot make a free designed cover, the post is now
  tried again later instead of being marked as failed for good. An AI cover is
  not retried automatically, because each attempt would use AI points again.

1.0.27

• Fixed the site totals on “Pins from this site”. They were adding up only your
  200 most recent Pins, which on a site with more than that showed a number far
  smaller than the truth — and because the newest Pins are the ones Pinterest has
  had least time to show, the figure could read as almost nothing while the Pins
  were in fact doing fine. The totals now cover every Pin for the site.
• The table still lists your most recent Pins, and now says so in one line when
  there are more Pins than it shows.
• Your Pin count on that screen is now the real number of Pins for the site,
  rather than however many fitted in the table.

1.0.26

• Names the Pinterest analytics this plugin has shown since 1.0.10. The feature
  is unchanged; the listing simply never used the words people search for, so
  nobody looking for “Pinterest analytics” in WordPress could find it.
• The new entry states the same free/paid split as the rest of the page: the
  site-wide total on every plan, the per-post breakdown on the paid plans.
• No code change.

1.0.25

• Corrected the listing: the per-post breakdown of how each post’s Pins are
  doing is on the paid plans, and this page said it was free. The site-wide
  total is on every plan, free included, and always was. Everything on the
  publishing side – automatic pinning, boards, templates, UTM tags, scheduling,
  retries, the backlog run and the Activity log – is unchanged and still free.
• No code change.

1.0.24

• New: Copy diagnostics on the Activity tab. One button gives you a
  paste-able summary of everything a support answer normally has to ask for
  first – WordPress and PHP versions, whether the scheduler is running, your
  settings, and the last ten log entries.
• Your API key is never in it, and nothing is sent anywhere: the block is built
  on your own site and you choose where to paste it.

1.0.23

• The plugin’s WordPress.org listing now describes what it already does in the
  words people actually search for: pinning pages and WooCommerce products as
  well as posts, working through an archive of older posts in bulk, the Pinterest
  impressions, saves and clicks it reports, and the UTM tags it adds for Google
  Analytics.
• Seven new questions answered on the listing, including the two that matter most
  before you install: yes, a free Burnpedia account is required, and no, hitting
  the daily Pin allowance does not lose a Pin – it waits for the reset.
• No functional change. Nothing in the plugin itself behaves differently.

1.0.22

• Once your site has been publishing Pins for a couple of weeks and they are
  being seen on Pinterest, the Pins tab asks — once — how it is going.
• Two links, side by side: tell us something is wrong, or leave a review.
  Nothing is offered in return, and “No thanks” means it never comes back.

1.0.21

• During a Pro trial the Connection screen now says how many days are left and
  gives you one button to keep it, instead of describing your plan as Starter.
• The button opens checkout with the plan already chosen — the link is created
  by Burnpedia, expires within a day, and never appears if no trial is running.

1.0.20

• When the day’s Pin allowance runs out, the message now says exactly when it
  comes back — in your site’s own timezone, not ours.
• The wording comes from Burnpedia, so it stays correct without updating the
  plugin, and it no longer offers an upgrade for the publishing-pace limit,
  which is the same on every plan.

1.0.19

• New: Connect this site to Burnpedia — one button on the Connection screen.
  Approve it in the tab that opens and your site collects its own API key. There
  is nothing to copy, nothing to paste, and the key is never shown in a browser.
• Setup is now two steps instead of five, and finishes with one plain question:
  create a Pin when I publish? Nothing is pinned until you answer yes.
• Pasting a key by hand still works exactly as before, and is still the way to
  connect a site that cannot reach the internet.

1.0.18

• New: an optional install count under Burnpedia Pins → Connection. WordPress.org publishes no
  install figure for this plugin, so we genuinely cannot tell how many sites use
  it. Switch this on and your site sends a random ID once a week so it can be
  counted. Your website address is never sent. It is off unless you turn it on,
  nothing depends on it, and turning it off deletes the ID.

1.0.17

• “Pins from this site” now explains what the numbers mean, in plain English —
  including when a lot of Pins went out on one day, which is the usual reason
  reach per Pin drops.
• Every row on that screen gets a “Design a Pin” link, the same one the Posts
  list has.
• The wording comes from Burnpedia, so it stays correct without updating the
  plugin.

1.0.16

• Safer pacing: “Pin older posts” now skips days your Pinterest account has
  already filled, instead of adding to them. Running a backfill twice used to
  stack both runs onto the same days.
• Burnpedia enforces the same daily limit on its side, so a Pin over the limit
  is moved to the next free day rather than published in a burst. Publishing a
  lot in one day sharply reduces how many people see each Pin.
• Nothing changes for a normal day, and no setting moved.

1.0.15

• New: “Pins per post” (1-6) under Automation. Each Pin uses a different
  photograph from the post and they go out a day apart, which is better
  Pinterest practice than one Pin per page.
• A post only has as many Pins as it has pictures. Four sizes of the same
  photograph count as one photograph, so you never get the same picture
  twice at different sizes.
• Raising it does not raise your daily rate: “Pin older posts” queues fewer
  posts a day to keep the Pins-a-day figure you chose, and the estimate on
  that screen now counts Pins rather than posts.
• AI covers: if you have “let Burnpedia generate one with AI” switched on, a
  post with no picture now gets your headline set ON the generated photograph,
  rather than a photograph with no words on it.
• It is one request instead of two. Before, the picture was paid for in the
  first request and pinned in the second, so a failure in between could charge
  you for a picture that never became a Pin.
• If the picture cannot be generated – most often because you are out of AI
  points – you get the free designed cover instead, the post is still pinned,
  and you are not charged.

1.0.14

• New: a post with no picture now gets a designed cover instead of being
  skipped. Its title is set in one of Burnpedia’s colour palettes at 1000×1500,
  the size Pinterest likes, and the same post always gets the same cover.
• It is free and uses no AI points. It is on by default and can be switched off
  under Automation – Image.
• If AI images are switched on and a generation fails – most often because the
  account is out of points – the post now gets a designed cover instead of no
  Pin at all. Both are written to the Activity log.
• The “Pin older posts” list no longer marks image-less posts as not ready when
  a cover or an AI image would be made for them.
• New: a “Design a Pin” link beside every post in the Posts list, and one on
  the plugin’s own settings screen. It opens Burnpedia’s free Pin maker with
  that post’s headline already filled in – no account needed, nothing is sent.

1.0.13

• New: the “Pin older posts” tab now tells you how many published posts have no
  Pin – on the tab itself, so you can see it without opening it – and roughly how
  many days it would take to work through them.
• Each post in the list says whether it is ready, or why it is not: no image
  Pinterest can use, in a category you excluded, or switched off by hand. You can
  no longer tick a post that would immediately be skipped.
• Long archives now page, and there is a tick-all for the page you are on.
• This works on every plan, including the free one. A bigger plan clears the
  backlog faster; nothing here is locked.
• New: when your Pins are stuck because WordPress is not running its scheduler,
  there is now a “Run it now” button next to the warning. It sends the waiting
  Pins straight away, so you are not stuck until your host answers.
• The button only appears when something is actually overdue, sends up to five
  Pins per press, and can be pressed once a minute. It is a nudge, not a fix –
  the cron line under it is still what stops the problem coming back.

1.0.12

• New: if you are publishing far more Pins per day than is safe for a Pinterest
  account, the plugin’s settings screen now says so, with the number you actually
  published and what we recommend. Pinterest has suspended accounts for high-volume
  publishing, and a suspension cannot be undone by reconnecting.
• You can close the notice. It comes back after a few days if the pace continues,
  and straight away if it gets faster.

1.0.11

• Fixed: the “Pinterest account” setting only ever offered one choice. If you have
  several Pinterest accounts connected to Burnpedia, all of them are now listed by
  username, and the one you picked is remembered.
• If the account this site was set to publish to is disconnected on Burnpedia, the
  setting now says so instead of quietly falling back to your default account.
• Internal: the Burnpedia API transport is now a single shared file, so both
  Burnpedia plugins handle errors, rate limits and daily-limit resets identically.
• Upgrade links now say which plugin they came from.

1.0.10

• 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.
• 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.
• Pinterest reports about two days behind, and the screen says so rather than showing the missing days as zero.
• A Pin published this week reads “No numbers yet” instead of “0 impressions” – they are different things.
• Per-post numbers are on the paid plans; the site total is on every plan, including free.
• 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.

1.0.9

• New tab: Pins from this site. 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.
• 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.
• Only this site’s Pins are listed, even if your Burnpedia account also schedules for other websites.
• New, and off until you turn it on: when a post has no image, Burnpedia can generate one with AI. 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.
• 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.
• You get a photographic background with no text on it. Posts that already have an image are never touched.
• 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.
• If the AI provider has a bad moment the Pin is retried on the usual schedule instead of being skipped for good.
• Clearer messages when Burnpedia says you are out of AI points, or when AI is switched off for your login by an account owner.

1.0.8

• 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.
• 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.
• 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.
• The warning appears on the plugin’s other tabs only when something is actually wrong.

1.0.7

• 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.
• 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.
• You can stop a run at any time; posts already sent keep their Pins.

1.0.6

• Your plan card now shows the same wording Burnpedia itself uses — “1 of 3 Pins used today on the Starter plan” — 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.
• 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.
• “Daily pin limit reached” now tells you where to go if you want more Pins today.
• 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.

1.0.5

• Tested with WordPress 7.1. Removes the “has not been tested with your current version of WordPress” warning on the plugin screen.
• No functional change.

1.0.4

• 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 — with when each one is due. Previously only finished attempts appeared, so a Pin on its way looked like nothing happening.
• An overdue Pin now says so, and says why: WordPress has not run its scheduler.
• Success rows show the destination board and link straight to the Pin.
• A post skipped for having no image now offers a button to go and add one.

1.0.3

• New: “Send a test Pin” on the Connection tab. It runs the real publishing path without sending anything and reports every step — 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.
• The check uses the same code that publishes, so it cannot pass while publishing fails.
• 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.

1.0.2

• New: a first-run checklist on the Connection tab — API key, Pinterest account, board, automatic pinning, first Pin — so you can see at a glance which step is still missing.
• 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.
• The “Getting started” steps now show a distinct “checking…” state while your account is being looked up, instead of showing a red cross for something we have not asked about yet.
• Larger touch targets and 16px form text on touch devices, so wp-admin no longer zooms when you tap a field on a phone.

1.0.1

• Stricter capability checks on the plugin’s own admin REST routes.
• “Pin this post now” now requires the publish capability for the post type, not only edit access to the post.
• A post that is not published and publicly viewable can no longer be pinned by hand.
• Reading the connection status and listing boards now require the manage_options capability.

1.0.0

• First release.