The last three releases of every CodeOn plugin, summarised in a couple of paragraphs the way a merchant would actually want to read them — no commit lists, no contributor blurbs, no GitHub footers. Filter by plugin or by change type to find what you care about.
We fixed an issue where re-syncing an order after changing your Document Type setting could create a duplicate document in Balance. Now, if you attempt to re-sync an order under a different document type, the plugin will prevent the duplicate from being created and prompt you to either remove the original document in Balance or switch your setting back first.
Orders synced prior to this update do not have a record of which document type they originally used. If you need to re-sync older orders after updating your Document Type setting, please double-check Balance to make sure duplicate records are not created.
Fixed: a scheduled import that timed out gave up for the whole hour, taking your stock and price refresh down with it, because they are fetched by the same job. It now tries a second time 15 seconds later, which is enough for the great majority of these. Background: as your Balance catalogue grows, reading all of it takes longer — on a 4200-item catalogue it is now close to two minutes, right at the limit Balance itself allows.
Fixed a mistake in 0.3.30 — please install this instead. The delivery-fee list in 0.3.30 read your entire Balance catalogue every time the Orders screen opened, which on a large catalogue meant the page sat there for about a minute, and it filtered on an item type field that turns out not to be reliable, so the list came back full of groceries rather than delivery services. The delivery-fee item is now found with a search box under the form: type part of the name, press searc…
Fixed: a refund that Flitt declined, or had not finished processing, was recorded as a completed refund. WooCommerce showed the customer refunded while Flitt had sent nothing. Refunds are now only recorded once Flitt confirms the money moved. Fixed: retrying a refund could pay the customer twice.
The check that runs when your customer comes back from Flitt is now triggered two ways, so a caching plugin, a custom theme or the checkout block cannot swallow it. Flitt sends customers back within about half a minute, so this is the normal path and it needs to be reliable. The background check now runs every five minutes instead of ten, halving the wait for customers who never return to the site.…
Orders now go green on their own, without any firewall or server setup. The plugin checks with Flitt the moment your customer returns from payment, so a paid order is confirmed in seconds. If a customer closes the tab or loses signal, a background check catches it within about ten minutes.
Fixed: the message box for each order status was invisible. Ticking "Text the customer" appeared to do nothing, so there was no way to write a template at all. The boxes now appear as soon as you tick the switch. The tab is now called Templates rather than Messages, which is what it actually is. Fixed: test messages were never written to the delivery log, so the log looked broken after sending one.
Fixed: campaigns could not be sent. The Preview and Send now buttons, and Resend in the delivery log, did nothing at all — they reported "Settings saved" and stopped there. All of them now work. Fixed: Resend could text the wrong customer.
Fixed: the merge-tag list on the Messages screen ran off the side of the page and gave the whole tab a horizontal scrollbar. The tags now wrap onto as many lines as they need. New: a worked example next to the tag list, so it is obvious how to write a message like "თქვენი შეკვეთა #{order_number} მზადაა" without reading the whole list first. Fixed: the Send test message button did not exist.
We've made a small but important improvement to how you cancel shipments. Now, when you click to cancel a shipment, the confirmation prompt will always appear, even if you use a special click like a middle-click. This helps prevent accidental cancellations and ensures you always confirm your choice.
We also fixed an issue where some stores had trouble returning to an order after creating, refreshing, or canceling a shipment. This should now work smoothly for everyone. These changes help make the plugin more reliable and secure for your store.
Fix: with the plugin active, WooCommerce orders could not be saved — changing an order's status did nothing and WordPress redirected to the orders list with the change lost. The QuickShipper order panel rendered its buttons inside their own HTML form, and because the order edit screen is itself one big form, the browser closed WordPress's form early and the Update button stopped submitting the fields WordPress needs.
Fix: the job tables ( + ) no longer grow forever. A daily housekeeping event now prunes finished/error/canceled jobs older than 30 days and sweeps orphaned job items ( existed but was never scheduled). In-flight and recent jobs are untouched; the schedule self-heals on update.…
Fix: size (and other taxonomy attributes) now show their Fina value on the storefront. Term lookup used termexists()/getterm_by(), which WPML remaps onto a translation-group sibling — so a Fina size "8" could attach a term literally named "8-იანი" (and leave the variation unfinished).
Feature: new "Product title from field" mapping in Imports. Pick a Fina field (e.g. usrcolumn509, your "webtitle") and new products are created with that field's value as the WooCommerce product name (still as drafts). Multiple spaces are collapsed; falls back to Fina's built-in name when the field is empty. Leave unset for the previous behaviour. Fix: variations whose size value maps to a term whose slug differs from the value (e.g.
This update includes some behind-the-scenes improvements to keep your plugin running smoothly. You won't notice any big changes in your store, but these updates help us prepare for future enhancements.
This update includes some behind-the-scenes improvements to keep your plugin running smoothly. You won't notice any changes in how you use the plugin or how your customers check out, but these updates help us maintain the plugin's stability and prepare for future enhancements.
This update includes some behind-the-scenes improvements to keep your plugin running smoothly. You won't notice any changes in how your store works, but these updates help us maintain the plugin's stability and prepare for future enhancements.
This update includes some behind-the-scenes maintenance to keep your plugin running smoothly. You won't notice any changes in how your store operates, but these updates help ensure everything stays in good working order.
This update includes some behind-the-scenes maintenance to keep your plugin running smoothly. You won't notice any new features or changes in how your store operates, but these updates help ensure everything continues to work well.
This update includes some behind-the-scenes improvements to keep your plugin running smoothly. You won't see any new features or changes in how you use the plugin, but these updates help ensure everything works well in the background.
This update is focused on behind-the-scenes improvements and maintenance to keep your plugin running smoothly. You won't notice any new features or changes in how your store operates, but these updates help ensure everything continues to work reliably.
This is a small update that helps your WordPress dashboard show the latest artwork for the Liberty Card Payments plugin right away. You'll now see our updated icon and banner when you look at your plugins. This change doesn't affect how the plugin works in your store, but it ensures everything looks fresh and up-to-date in your admin area.
New: plugin icon + banner artwork. Liberty torch / flame motif on the family-consistent CodeOn deep-blue gradient — sits in the same chip slot used by TBC (square), BOG (round), Flitt (lightning), so the card plugins read as one suite while each is instantly distinguishable at the 40px tile.
Fix: license enforcement — bumps bundled to v0.3.18, which makes honor a server-side verdict from codeon.ge instead of letting the local grace window mask it. Effect: when codeon admin marks a license expired, the Credo Installments option now vanishes from WooCommerce checkout immediately (via the framework's gate) and the License tab hides the Key/Plan/Expires meta block.…
This update improves how your plugin license is managed. Previously, there might have been a delay in recognizing an expired license, but now the plugin will check its status more directly with our server.
This means that if your license expires, the BoG Installments and BoG BNPL payment options will immediately be removed from your WooCommerce checkout. You'll also notice that the license details on your plugin's License tab will no longer be visible.
Fix: license enforcement — bumps bundled to v0.3.18, which makes honor a server-side verdict from codeon.ge instead of letting the local grace window mask it. Effect: when codeon admin marks a license expired, the BOG Card option (and Apple Pay / Google Pay / BOG P2P sub-methods) now vanish from WooCommerce checkout immediately (via the framework's gate) and the License tab hides the Key/Plan/Expires meta block.…
Fix: license enforcement — bumps bundled to v0.3.18, which makes honor a server-side verdict from codeon.ge instead of letting the local grace window mask it. Effect: when codeon admin marks a license expired, the TBC Online Installments option now vanishes from WooCommerce checkout immediately (via the framework's gate) and the License tab hides the Key/Plan/Expires meta block.…
This update improves how your plugin license is managed. Previously, there might have been a short delay between your license expiring and the payment options disappearing from your store.
Now, if your license expires, the TBC Card and TBC BNPL payment options will be removed from your WooCommerce checkout immediately. You will also notice that the license details in the plugin's settings will no longer show your key, plan, or expiration date once your license has expired.
WC order id now visible in TBC merchant dashboard (Field 98 / FLD_098). The legacy plugin used to write the order id into TPay's field, so support staff and bank reconciliation could match a TBC transaction to a WC order at a glance. v0.3.4 and earlier wrote the callback HMAC into instead — making the dashboard column a useless 20-char hash. v0.3.5 mirrors the old plugin's exact format ( ) in , and moves the callback HMAC to TPay's field.
Fix — late callbacks for an abandoned BOG payment attempt no longer flip a paid order to . When a customer abandoned their first iPay session, the gateway (since v0.3.6) re-initiated a fresh session and stored the previous id under . BOG eventually expires abandoned sessions and POSTs a callback for the old id.
Invariant: WC order status must always mirror TBC's current application status. TBC is the source of truth — manual edits in WC that drift from TBC get re-aligned on the next cron tick (1 hour) or immediately on "Re-check with TBC". The only carve-out is WC , which never gets overwritten (an order note records the mismatch instead). 48h auto-cancel for stale alive applications.
Re-init recovery for the "approved but stuck on-hold" bug, ported from v0.3.7. If a customer reloaded the BOG hosted installment / BNPL application (or hit "back" then re-clicked Pay) mid-flow, called BOG again for the same WC order — overwriting the stored BOG id with a new one. The bank still processed the application against the original id, but the late callback for that id was logged as and dropped, and the reconcile cron forever polled the new (un-actioned) id.
We've made a small visual update to your checkout page. The Credo logo for installments will now line up more consistently with your other payment options. This helps create a cleaner and more professional look for your customers as they complete their purchase.