ENPLDEES
Volver a Sekvov1.1.2 (23 versiones)

Changelog Sekvo

Changelog del plugin de WooCommerce Sekvo (previsto): actualizaciones, correcciones y desarrollo de funciones.

v1.1.2
  • The upgrade notice's "Coming soon" and "Get notified" labels are English source strings for every language; Polish sites used to get their own Polish source text, which translators in other languages then saw untranslated.
v1.1.1
  • The sidebar upgrade promo now follows the same dismissal as the banner. Dismissing the banner used to leave a full-height advert on the settings screen for good, which is not what the WordPress.org guideline on upgrade prompts means by used with moderation.
v1.1.0
  • Renamed to Sekvo. The WordPress.org review team asks a plugin name to lead with a distinctive, coined identifier rather than a generic descriptive word. Sekvo is Esperanto for a following. The text domain follows the name; the stored data, the settings and every hook are unchanged.
v1.0.15
  • Fixed a wall of orders that cannot be sent being read over and over inside a single run. When the run reached the end of such a queue it treated the empty page that follows as a stale position and started again from the top, up to the 1,000-order read ceiling. Measured on a queue of exactly 200 held-back orders: 20 queries and 2,000 rows read every day for 200 orders, against 6 queries and 400 rows now. The same run also recorded a position it had already read past, so the next run started in the middle of a queue it had finished.
  • Fixed orders that share a last-modified second, which is what a bulk status change gives a whole screen of them, having no fixed order between two queries. A page boundary inside such a group could offer one order twice and skip another. Orders are now read oldest first and by order number within the same second.
  • Corrected the FAQ on how far a run reads. Only a run stopped by the 1,000-order ceiling records where it stopped; a run that reaches the end of a type's queue starts the next one at the top, which is what gives a held-back order another chance.
  • Documented that WooCommerce only filters orders by the "already sent" marker on High-Performance Order Storage. On the legacy posts table that filter is dropped, so each run walks about 800 past orders before reaching the due ones: with 3,000 followed-up orders behind it a new order is mailed on the fourth run, with 30,000 on the thirty-eighth. Nothing is sent twice and nothing is lost either way.
  • On the settings screen, the cut-off date no longer reads as a promise that every order after it is followed up. When the plugin has been switched back on, the screen now also names that moment and says each email reaches back only by its own delay from it.
v1.0.14
  • Fixed re-activation handing the short follow-ups the longest delay's reach-back. Switching the plugin back on moved the cut-off forward by the longest delay configured anywhere in the sequence, and that one cut-off applied to every email type, so with the packaged settings the 7 day review request gave the thank-you a week of orders to thank people for, and a 30 day step added by Plogins Followup Pro gave it a month. Each type now reaches back by its own delay: on the packaged settings the thank-you covers the last day, the review request the last 7 days.
  • Fixed a shop that cannot deliver stopping its follow-ups for good. The 200-per-run ceiling counted orders read rather than emails sent, so 200 orders that could not be sent, held back by an add-on or refused by the mail server, filled it every day and the orders behind them were never reached. The ceiling now counts emails: an order that cannot be sent costs nothing, the run reads on past it up to 1,000 orders per type, and a run that ends inside such a stretch records where it stopped so the next one carries on from there.
v1.0.13
  • Fixed the cut-off staying pinned to your very first install. Switching the plugin off stops every follow-up, because deactivating removes the daily task, but the cut-off did not move, so switching it back on months later handed the first run every order taken in between. A shop that installed the plugin, turned it off the next day and turned it on a year later mailed 200 thank-yous a day until that year of orders ran out. Re-activating now moves the cut-off forward to the longest delay you have configured, 7 days on the packaged settings: orders still inside that window are followed up, the rest are left alone.
  • Fixed network activation on multisite mailing old orders. WordPress runs the activation step only on the site you were on when you clicked, so every other site in the network had no cut-off and took one that reached a week into the past, then mailed those customers. A site with no cut-off recorded, which is any site the activation step never reached and any site updating from 1.0.11 or earlier, now takes the moment the sender first runs there, and follows up nothing older. On a site updating from 1.0.11 that is stricter than 1.0.12 promised: a follow-up that was due in the last few days is skipped rather than sent late, which is the side we would rather be wrong on.
  • Fixed a follow-up going out for an order that had left the status that triggers it. A send interrupted by a crash is retried the next day, and that retry was not checking the status again, so an order refunded or cancelled in between was still thanked for its purchase.
  • Fixed the sender jamming when an add-on holds sends back. Plogins Followup Pro can defer a send to a chosen hour or day. An order that was held back after a crash had claimed it was counted against the 200-per-run ceiling every day without ever being resolved, and 200 of them filled the ceiling, at which point the shop stopped sending follow-ups entirely and said nothing. A held-back order now gives its claim back and is picked up again when it is allowed to send.
  • Fixed one mail failure burying a follow-up for good. If a send crashed and the retry the next day then hit an ordinary failure, a mail server refusing the message or being down for a minute, the follow-up was marked spent even though nothing had been sent, and it was never tried again. A refusal is now what it is, a message that did not go out, so the next run tries again.
  • Corrected the claim that a follow-up is "never sent twice". It is sent once per order, and the two ways a customer can see it twice both need a send to die after the mail server has already taken the message. The FAQ now says which trade-off this plugin makes and why: the order is marked before the email is handed over, which turns a crash into a possible duplicate rather than into a follow-up that is silently never sent.
  • On the settings screen, the cut-off date no longer describes itself as the day you switched the plugin on. On a site that inherited the plugin, or one updating from an older version, it is the day the sender first ran there.
v1.0.12
  • Fixed the worst thing this plugin could do: on a shop that already had orders, the first daily run after activation treated the entire order history as due and started mailing customers who had ordered months or years earlier, 200 per follow-up type per day until the backlog drained. Activation now records the moment you switched the plugin on, and orders placed before it are never followed up. Sites updating from an earlier version get that floor set at their longest configured delay, which keeps the follow-ups still legitimately pending and leaves the rest of the history alone.
  • Fixed follow-ups being dropped for good when a send died mid-flight. The order is marked before the email is handed to `wp_mail` so an overlapping run cannot send it twice, but a PHP fatal error or a script timeout inside `wp_mail` left that mark behind with no email sent and nothing to undo it. An unfinished send is now recognised as unfinished and retried once, then left alone, so one crash can neither lose a follow-up silently nor mail the same customer every day.
  • The delay is now counted to the second rather than to the day. WooCommerce reads a plain date as a whole day, so a follow-up could go out up to a day earlier than the delay you set. It now never goes out early, which means the first send after this update can land up to a day later than you are used to.
  • The settings screen and the listing now state the ceiling: at most 200 emails per follow-up type per daily run.
v1.0.11
  • Fixed: the PRO upgrade promo kept selling to people who had already bought the paid edition. Only the banner could be dismissed, so the sidebar promo and the locked feature cards followed a paying customer around for good. The promo now checks whether the paid edition is active and steps aside when it is.
  • Fixed: deleting the plugin left the per-user "dismiss" flag from the PRO notice in the database. Uninstall now removes it for every user, not just the one who dismissed it.
v1.0.10
  • Fixed the follow-up email subjects and bodies being stuck in English. The packaged wording lived in a config file rather than in a translatable string, so it never reached the translation files, and the settings screen wrote that English back into the database whenever a field was left blank. A store running in Polish, German or Spanish mailed its customers in English no matter how complete the language pack was.
  • The subject and body fields now ship empty and show the translated default in grey. Leave a field blank and the wording follows your store language as soon as a translation for it exists; type your own and it is used exactly as typed. Translations are delivered by WordPress.org language packs rather than bundled in this download, so a blank field stays English until a pack is published. Wording you had already customised is left alone. A stored template that is still word for word the old English default is cleared on update, so it starts following your store language.
v1.0.9
  • Renamed to Plogins Followup - Follow-Up Emails for WooCommerce so the name leads with the brand rather than a generic word, which is what the WordPress.org plugin review team asks for. The plugin slug is unchanged.
v1.0.8
  • Removed the "Tested up to" header from the main PHP file. It belongs in readme.txt only, where it is already declared; present in both, the header can override the readme and show a compatibility version that was never intended.
v1.0.7
  • Tested against WordPress 7.1. Verified by activating this build on a clean 7.1 install with WooCommerce 11.1, not by editing the header.
v1.0.6
  • Fixed the PRO promo on the settings screen quoting a price in PLN. PRO is priced and charged in EUR, so an admin on a Polish site was shown a zloty amount and then billed in euro, and the zloty figure was a fixed conversion that drifted from the real charge as the rate moved. The promo now shows the euro price that is actually taken.
v1.0.4
  • Translations: completed Polish, German and Spanish for the PRO upgrade panel.
v1.0.3
  • Fixed low-contrast admin headings under an OS dark-mode preference.
v1.0.2
  • Added bundled Polish, German and Spanish translations for the plugin interface.
v1.0.1
  • First stable release.
v0.1.5
  • Renamed to Plogins Followup for WooCommerce for a more distinctive plugin name.
v0.1.4
  • `followup/email_links` filter exposes URLs discovered in the final follow-up body for PRO engagement tracking.
v0.1.3
  • `followup/should_send` filter before a follow-up claims an order, so PRO can defer sends to a chosen hour or weekday.
v0.1.2
  • Fire `followup/email_sent` after a follow-up is accepted by wp_mail for PRO send reporting.
  • Document the `{coupon}` placeholder for Followup Pro coupon blocks.
v0.1.1
  • Add the `followup/sequence_steps` extension filter so add-ons can append custom post-purchase email steps.
v0.1.0
  • Initial release: thank-you and review request follow-up emails with per-type enable, trigger status, delay and templates; idempotent daily sender.
Volver a Sekvo