Groundhogg — CRM, ຈົດໝາຍຂ່າວ ແລະ ການຕະຫຼາດອັດຕະໂນມັດ

ບັນທຶກການປ່ຽນແປງ

4.9.4 (2026-10-13)

• ADDED The email abilities can set an email’s custom CSS, custom headers and UTM parameters when they create or update an email, and they return them when an email is read.
• TWEAKED Four column layouts show as two rows of two columns on small screens, instead of a single column. Use the column padding to space them.
• FIXED Emails scrolled sideways on phones in email apps that ignore the styles in an email’s head, such as Gmail with a non-Google account. This includes emails that were saved before this version.
• FIXED A font set for the links in a text block could break the CSS that came after it. Emails saved this way are repaired when they are sent or viewed.
• FIXED The tag picker on the map step of an import failed with “Groundhogg.createState is not a function” when the admin scripts were delayed or deferred. The step now loads the script that it needs.
• SECURITY Hardened how files are copied to a contact’s files by imports, the REST API and webhooks. Credit: Supakiad S. (m3ez) of E-CQURITY, via Wordfence.

4.9.3 (2026-10-09)

• SECURITY The page for an email in a campaign’s archive showed any broadcast on the site, including ones that hadn’t been sent and ones in campaigns that aren’t public, to anyone who knew its number. It only shows emails that have been sent and are in that campaign, and it can no longer be cached.
• FIXED Files uploaded to a contact before 4.7.2 were missing from the contact’s Files tab, and from {files} and the contact’s downloads. 4.7.2 changed the name of the folder that a contact’s files are kept in, and the files were left in the old one. They are moved to the right folder when the contact’s files are asked for, when the contact’s email address is changed, and when an old link to one of them is followed. Files that are in both folders are kept, and nothing is overwritten.
• FIXED Opening the archive of a campaign that isn’t public as someone who manages campaigns ended in a white screen. Anyone else gets a page that says it can’t be found.
• FIXED The flow editor couldn’t add or move a step into an empty branch of a split path, random distribution, split test or evergreen sequence. It said the branch didn’t exist.
• FIXED The bounce check could stop moving on when 200 or more emails in the inbox were dated within the same few hours, and read the same emails every time it ran.
• FIXED Setting up Incoming Messages sent an expired key when the site has an expired master license and a valid license for a single product.
• FIXED Activating a license key that the site hadn’t seen before logged a warning that included the key, and re-activating a key returned the license as it was before.
• IMPROVED The archive pages and the preferences center, including the profile, erase and unsubscribe pages, have a new look with cards, light and dark colors that follow the visitor’s setting, and a layout for small screens.
• DEV New File_Box::get_legacy_upload_folder_basename() and File_Box::maybe_move_legacy_upload_folder(). get_uploads_folder() moves the files of a folder from before 4.7.2 before it gives the folder.
• DEV New Rewrites::current_upload_folder_path() and Rewrites::is_in_campaign_archive().
• DEV The colors of the managed pages are CSS variables that begin with --mp-, set on body.managed-page.

4.9.2 (2026-10-06)

• ADDED Handle Bounces Now in Settings > Email, for sites that receive bounces in an IMAP inbox. It checks the last 7 days of the inbox and shows how many emails it checked, how many contacts were marked as bounced, and what it decided for each recipient.
• ADDED When contacts waiting at a deleted step are moved to another step, you can choose to run them when that step normally runs, or on a date and time.
• SECURITY Messages are now deleted with their contact, and a message that is left without its contact can no longer be read by anyone. Messages left behind by contacts that were deleted before this update are no longer readable, but they aren’t deleted.
• SECURITY The secret that verifies incoming messages is no longer created while a request is being checked, and a secret defined with GH_INBOUND_SECRET is the only secret that’s used.
• FIXED Bounces in an IMAP inbox were missed when the email had been read, or was more than a day old.
  • The bounce checker carries on from where it last got to instead of only looking at unread email from the last day.
  • A failure with a temporary status (4.x.x), like a full mailbox, is never marked as a hard bounce, and the action in a bounce report is read in any case.
  • A failure with a permanent status (5.x.x) is no longer changed into a temporary one because of what the mail server said about it.
  • A bounce report without a recipient can no longer mark whichever contact is being processed as bounced.
• FIXED Cancelling a broadcast, including when a segment filter fails while it’s scheduling, no longer clears the cancelled events of other broadcasts and flows from the queue.
• FIXED The Replies widget set to All said there was nothing to read when the newest replies were on contacts that you can’t see.
• FIXED A delay timer set to run on a day that none of its months have, like the 30th of February, ran on the delayed date. It now runs on the last day of the month. A step that has no time to run no longer has contacts put in it, and the reason is recorded as a failed event.
• FIXED The 4.9 update added an email composed to a contact that no longer exists, or with no contact, to whichever contact was being tracked, and copied an email a second time if the update was interrupted.
• FIXED Adding the activity table indexes in the 4.9 update locked the table when the server couldn’t add them without blocking. It now tries again a few times, and reports the database’s error if it can’t. Sites that can’t add indexes without blocking need to add them manually.
• IMPROVED Load earlier activity in a contact’s timeline keeps looking further back when a stretch of time has no activity, instead of showing nothing, and says “Beginning of contact history” when there is nothing more to load.
• FIXED Load earlier messages got stuck in a conversation when a whole page of messages was written in the same second, like after emails composed before the 4.9 update were moved, or an import.
• FIXED An undo or redo in the flow editor that failed partway left the flow showing only part of the change, and cleared the undo history. The flow is put back as it was, and the history is kept.
• DEV The messages feed takes before_kind and before_id with before, and returns the cursor for the next page in next.
• DEV Moved contacts take date and time in the deleted step choices of the flow abilities, and Funnel::resolve_deleted_step_events() takes a time timestamp for them. The outcomes include run_at.
• DEV Task::process() can return null to stop for now and be picked up again on the next pass.
• DEV New groundhogg/bounce_checker/manual_days and groundhogg/bounce_checker/limit filters, and Bounce_Checker::classify().
• DEV New Inbound_Signature::ensure(). Inbound_Signature::secret() only reads the secret.
• UPDATED The license store URL, and the store products now come from License_Manager.

4.9.1 (2026-10-02)

• SECURITY Hardened how contacts are linked to WordPress users and how sign-in links are created. Credit: Wordfence PRISM, via Wordfence.
  • Linking a contact to a WordPress user now requires permission to edit that user.
  • {auto_login_link} only creates a sign-in link in emails sent to the contact’s own user account.
  • Sign-in keys are always blacked out in the email log, and sensitive logs are now hidden from non-administrators.
• FIXED {auto_login_link} caused a fatal error in emails composed to a contact.
• FIXED The v3 REST API now checks permission to edit when creating a contact with an email address that already exists.
• FIXED An email that failed to send left Groundhogg treating the rest of the request as if an email was still being sent.

4.9 (2026-10-01)

• ADDED Receive replies in Groundhogg. Turn on Incoming Messages in Settings > Email (needs an active Groundhogg license), then switch on “Save replies as messages” in an email’s settings, and replies to it are saved to the contact who replied instead of going to your own mailbox. You can also BCC your site’s private inbox address to keep a copy of emails you send from your own mailbox.
  • A Messages tab in the contact record shows your conversation with each contact, the emails you’ve sent them and their replies, laid out like a chat. Emails you composed to contacts before this update are moved into it in the background.
  • A “Replies” dashboard widget lists contacts who’ve replied and haven’t been read yet. Open a conversation right from the dashboard to read it, reply, or mark it read or unread.
  • When composing an email to a contact, choose who it’s from out of your sender profiles.
• ADDED A new, shorter guided setup that gets your site ready to send: your business and who emails come from (with details filled in from WooCommerce or Easy Digital Downloads), privacy, your license, receiving replies, and updates. The last step helps you get started with AI, invite your team, and add your site’s users as contacts.
• ADDED Flow abilities for AI assistants.
  • “Get Flow”, “Edit Flow”, “Publish Flow Changes” and “Discard Flow Changes” abilities, so an AI assistant can read an existing flow and add, change, move, duplicate, lock or delete its steps. Changes to an active flow are staged until they’re published, the same as in the flow editor.
  • Segments used by the abilities can target contacts by behavior: email opens and clicks, page visits, form submissions, flow conversions, and other activity. They can also exclude another segment, and contact searches link to the matching contacts in the Contacts page.
  • The simulate abilities can run against a flow’s unpublished changes, so a change can be tested before it’s published.
• ADDED When you publish changes to a flow or activate it, you choose what happens to contacts waiting at steps you deleted: cancel their events, or move them to another step. Before, they were silently removed from the flow. Deleted steps that contacts have already been through are archived, so their history and reports still work.
• TWEAKED The flow editor has been rebuilt to be much faster. Adding, moving, deleting and changing steps shows right away and saves in the background, and undo and redo now cover step settings, duplicated steps and pasted steps too.
• TWEAKED If a flow or an email is changed from somewhere else while you have it open in the editor, the editor tells you and offers to reload.
• TWEAKED Public form submissions are limited to 20 per form, per IP address, every 10 minutes. People who can add contacts aren’t limited.
• TWEAKED The send time optimization option is hidden in the broadcast scheduler for now.
  • Only one person can edit a flow at a time, so two people can’t overwrite each other’s changes. The flow is unlocked as soon as its editor is closed.
  • Duplicating a step with branches, like a Yes/No, copies the steps in its branches too, and steps copied from one flow can be pasted into another.
  • Steps that other steps rely on, like the step a Reroute goes to or the step another flow’s “Add to Flow” starts at, can’t be deleted until those steps are changed.
  • The search in the add steps panel stays while you switch between Triggers, Actions and Logic.
  • The flow editor tour is written for people new to Groundhogg.
• TWEAKED Faster reports, segments and contact timelines.
  • Segments, reports, and contact timelines that filter activity by type or by contact and date are faster, thanks to new indexes on the activity table. Existing sites get them from a background task after updating.
  • Reports and contact counts are cached, so dashboards and reports load faster.
• TWEAKED Number filters in contact searches understand numbers formatted for your locale, and the flow, step and email filters can match more than one at a time.
• TWEAKED Settings and integrations.
  • The telemetry setting explains exactly what’s shared when it’s turned on.
  • Groundhogg’s capabilities are grouped under “Groundhogg” in the User Role Editor plugin.
  • Dashboard notices and the template library load from Groundhogg’s CDN, with the original servers as a fallback.
• FIXED Flow triggers and timing.
  • A trigger’s “Can be triggered” limit, like “At most once per contact” or “Up to X times per contact in X days”, was never enforced.
  • When a trigger fired more than once at the same time, for example tagging several contacts at once, contacts after the first could get the first contact’s details in the flow.
  • Delay timers set to run on the last day of the month never ran, dates that don’t exist like April 31 ran on the next month, runs on the 29th to the 31st could skip a month, and long delays could ignore which days they were allowed to run on.
  • Delay timers in flows built with the abilities were titled “Wait 3 days” whatever they were set to.
• FIXED Flow editor and simulator issues.
  • Unsaved step settings were lost when the flow editor couldn’t save, and autosave stopped after a failed save.
  • The Publish Changes button stayed off when the only change to a flow was deleting steps, and deactivating a flow brought back steps deleted while it was inactive.
  • The flow simulator stayed stuck loading when the contact it last simulated with had been deleted. Now it asks you to select a contact.
  • The REST API’s commit route for flows always returned an error, and importing a flow could interfere with flows imported before it.
  • Branch, trigger and jump lines that should curve were drawn straight when the editor was scrolled.
• FIXED Contact searches and counts could show out-of-date results right after a tag, activity or custom field changed, and a search combining two flow activity filters ignored the step and date range of the second one.
• FIXED Email tracking and contact identification.
  • The open tracking pixel was missing from HTML emails that weren’t a full HTML document.
  • Contacts that arrived from a link in a tracked email weren’t recognized as who they are, so merge tags like {user.*} were blocked for them.
• FIXED Activating a license from the guided setup or the troubleshooter failed, and the old guided setup never saved its privacy and sender settings.
• FIXED Forms on pages served by a full page cache could fail to submit because of an out of date nonce.
• FIXED Triggers that pass a WooCommerce order to a flow logged an “Order properties should not be accessed directly” notice on every paid order.
• FIXED The query table ability returned every contact, with the wrong total, when it was given filters. It now points to the search contacts ability instead.
• SECURITY Access and verification hardening.
  • An account could get administrator access by posing as the Groundhogg support user when an admin turned on support access.
  • Contacts created by a form submission are no longer treated as verified visitors, since anyone can submit a form.
  • The privacy policy and terms links in settings are only saved as real links.
• DEV The flow editor’s canvas, settings panels and add steps panel are drawn in JavaScript, and edits are saved as operations through the gh_flow_operations and gh_flow_action ajax actions.
  • Step types can register JavaScript settings, titles and branch previews with Funnel.registerStepType(). Funnel_Step::save(), get_posted_data(), setting_name_prefix() and setting_id_prefix() work as before. See docs/flow-architecture.md.
  • Step::save() takes the settings to save, and Step::update_settings() changes some of them.
• DEV Query caching and the activity table.
  • Queries take a cache var, false to skip the cache or a number of seconds that results can be stale for, and the groundhogg/query/table_cache_group filter lets queries on other plugins’ tables be cached. Table_Query::where() and Where::subWhere() accept a callback.
  • The activity table has two new indexes, type_time_contact_idx (activity_type, timestamp, contact_id) and contact_time_idx (contact_id, timestamp, activity_type, email_id, step_id), which replaces contact_idx. New DB::index_exists(), DB::add_index_online() and DB::is_being_altered() methods.
• DEV New groundhogg/email/reply_to_messages and groundhogg/inbox/address_prefix filters, and gh/v4/messages/unread and gh/v4/messages/read REST endpoints.
• DEV Add-ons register their abilities on ordered actions: groundhogg/abilities/register_schema_extensions, groundhogg/abilities/register_step_types, groundhogg/abilities/register_categories and groundhogg/abilities/register_abilities, so step types see the schema extensions of every add-on. See docs/abilities-registration.md.
• DEV New groundhogg/form/v2/rate_limit and groundhogg/form/v2/rate_limit_window filters for the form submission limit, 0 turns it off.
• DEV The Legacy_Contact_Query class, deprecated since 3.2, has been removed.

4.8.3 (18 ກັນຍາ 2026)

• ເພີ່ມ: ລາຍງານແບບກຳນົດເອງຖືກສ້າງຂຶ້ນໃໝ່ເພື່ອໃຫ້ຕົວແກ້ໄຂໄວຂຶ້ນ ແລະ ສະໝ່ຳສະເໝີຂຶ້ນ, ພ້ອມກັບລາຍງານປະເພດໃໝ່ “ຕາຕະລາງ (ແທັກ)” ແລະ “ກຣາບວົງມົນ (ແທັກ)” ທີ່ຈັດກຸ່ມຈຳນວນຜູ້ຕິດຕໍ່ຕາມແທັກໜຶ່ງອັນ ຫຼື ຫຼາຍອັນ, ພ້ອມທັງສາມາດເຈາະເລິກໄປເບິ່ງຜູ້ຕິດຕໍ່ທີ່ກົງກັນໄດ້.
• ປັບປຸງ: ຕົວເລືອກວັນທີປະຕິທິນມີສະຖານະຕອນວາງເມົາສ໌ (hover) ທີ່ແຈ້ງຂຶ້ນ, ເຮັດໃຫ້ວັນທີທີ່ຢູ່ນອກຂອບເຂດເປັນສີເທົາ ແລະ ຕົວເລືອກເດືອນມີການໂຕ້ຕອບໄດ້ດີຂຶ້ນ.
• ແກ້ໄຂ: ຂັ້ນຕອນການແຈ້ງເຕືອນແອັດມິນອາດລົ້ມເຫຼວພ້ອມກັບຂໍ້ຜິດພາດຮ້າຍແຮງ (fatal error), ເຮັດໃຫ້ເຫດການຄ້າງຢູ່ສະຖານະ “ກຳລັງດຳເນີນການ” ແລະ ສົ່ງແຈ້ງເຕືອນຊ້ຳກັນ.
• ແກ້ໄຂ: ຕົວປ່ຽນແທນ select2 ທີ່ມາກັບ Groundhogg ຈະບໍ່ເຂົ້າໄປກວນ dropdowns select2 ຂອງປລັກອິນອື່ນໆໃນໜ້າ wp-admin ອີກຕໍ່ໄປ.
• ແກ້ໄຂ: ແຈ້ງເຕືອນ “Translation loading for the groundhogg domain was triggered too early” ໃນ WordPress 6.7+, ໂດຍການໂຫຼດ textdomain ຂອງປລັກອິນກ່ອນທີ່ປລັກອິນຈະເລີ່ມເຮັດວຽກ.
• ແກ້ໄຂ: ຟອມທີ່ສ້າງຂຶ້ນດ້ວຍຄວາມສາມາດ “Create Flow” ບໍ່ສາມາດສົ່ງໄດ້.
• ຄວາມປອດໄພ: ເພີ່ມຄວາມເຂັ້ມງວດໃນການຈັດການຂໍ້ມູນຜູ້ຕິດຕໍ່ ແລະ ການສະແດງຜົນອີເມວສຳລັບຜູ້ເຂົ້າຊົມທີ່ຍັງບໍ່ໄດ້ຮັບການຢືນຢັນຕົວຕົນ. ໃຫ້ເຄຣດິດ: Ayukiab, ຜ່ານ Patchstack.

4.8.2 (16 ກັນຍາ 2026)

• ເພີ່ມ: ຂັ້ນຕອນການກະທຳ “Add to Flow”, ເພື່ອໃຫ້ flow ສາມາດເພີ່ມຜູ້ຕິດຕໍ່ເຂົ້າໄປໃນ flow ອື່ນ (ຫຼື ເລີ່ມ flow ເດີມໃໝ່) ທີ່ຂັ້ນຕອນທຳອິດ ຫຼື ຂັ້ນຕອນທີ່ທ່ານເລືອກ, ແທນທີ່ຈະຕ້ອງໃຊ້ຂັ້ນຕອນດ້ວຍຕົນເອງ ຫຼື ລະບົບອັດຕະໂນມັດອື່ນມາຊ່ວຍເຮັດ.
• ເພີ່ມ: ຄວາມສາມາດ “Simulate Flow” ແລະ “Live Simulate Flow”, ເພື່ອໃຫ້ຕົວແທນສາມາດຕິດຕາມສິ່ງທີ່ flow ຈະເຮັດກັບຜູ້ຕິດຕໍ່ຈາກຂັ້ນຕອນທີ່ກຳນົດໄດ້ (ສາຂາທີ່ເລືອກ, ເວລາປະມານທີ່ຕົວຈັບເວລາຈະເຮັດວຽກ) ໂດຍບໍ່ມີຜົນກະທົບໃດໆ, ຫຼື ແລ່ນມັນແທ້ໆເລີຍ – ເຊິ່ງເປັນການຈຳລອງແບບດຽວກັນກັບທີ່ໜ້າຕ່າງ “Simulate” ຂອງຕົວແກ້ໄຂ funnel ໃຊ້.
• ເພີ່ມ: ຄວາມສາມາດ “List Settings” ແລະ “Update Settings”, ທີ່ຮອງຮັບໂດຍລະບົບລົງທະບຽນການຕັ້ງຄ່າໃໝ່ພ້ອມການກວດສອບ JSON-schema, ເພື່ອໃຫ້ຕົວແທນສາມາດຄົ້ນພົບ ແລະ ປ່ຽນແປງການຕັ້ງຄ່າທີ່ລົງທະບຽນໄວ້ຂອງປລັກອິນໄດ້ ແທນທີ່ຈະເຮັດໄດ້ແຕ່ສະເພາະກັບສິ່ງທີ່ຄວາມສາມາດກວມເອົາແລ້ວ (ຜູ້ຕິດຕໍ່, ອີເມວ, flows ແລະ ອື່ນໆ).
• ເພີ່ມ: ຄວາມສາມາດ “Add Custom Field” ແລະ “Update Custom Field” ສຳລັບການສ້າງ ແລະ ແກ້ໄຂຊ່ອງຂໍ້ມູນກຳນົດເອງຂອງຜູ້ຕິດຕໍ່, ໂດຍມີກົດການກວດສອບແບບດຽວກັນກັບທີ່ຕົວແກ້ໄຂຜູ້ຕິດຕໍ່ໃຊ້.
• ເພີ່ມ: ໝວດໝູ່ຄວາມສາມາດ “Groundhogg Extensions”: “List Extensions” ເພື່ອເບິ່ງວ່າສ່ວນເສີມທາງການອັນໃດທີ່ຕິດຕັ້ງ ແລະ ມີໄລເຊັນແລ້ວ, “Check License” ແລະ “Activate License” ເພື່ອຈັດການປຸ່ມໄລເຊັນ ແລະ “Install Extension” ເພື່ອຕິດຕັ້ງ ແລະ ເປີດໃຊ້ງານທາງໄກ – ໂດຍຂຶ້ນກັບຄວາມສາມາດ install_plugins/activate_plugins ຂອງ WordPress ເອງເນື່ອງຈາກມັນເປັນການຕິດຕັ້ງໂຄ້ດໃນເວັບໄຊ.
• ເພີ່ມ: ຄວາມສາມາດ “Create Tag” ແລະ “Create Campaign”/”Associate Campaign” ສຳລັບການສ້າງແທັກ ແລະ ແຄມເປນ ພ້ອມທັງແນບແຄມເປນເຂົ້າກັບອັນອື່ນໆ, ແທນທີ່ຈະຕ້ອງມີຢູ່ແລ້ວ.
• ປັບປຸງ: ດຽວນີ້ວິດເຈັດໜ້າປັດສາມາດຈັດລຽງໃໝ່ໄດ້ດ້ວຍການລາກ ແລະ ວາງ; ຮູບແບບຈະຖືກຈື່ໄວ້ຕາມແຕ່ລະບຣາວເຊີ.
• ຄວາມປອດໄພ: ເພີ່ມຄວາມເຂັ້ມງວດໃນການຈັດການຂໍ້ມູນທີ່ຜູ້ຕິດຕໍ່ສົ່ງມາ ເພື່ອປ້ອງກັນບໍ່ໃຫ້ມັນຖືກແປຄວາມໝາຍໃໝ່ເປັນເນື້ອຫາທີ່ໃຊ້ງານໄດ້ໃນສ່ວນອື່ນໆຂອງ CRM. ໃຫ້ເຄຣດິດ: Ayukiab, ຜ່ານ Patchstack.

4.8.1 (14 ກັນຍາ 2026)

• ເພີ່ມ: ຄວາມສາມາດ “Create Flow” ແລະ “Activate Flow”, ເພື່ອໃຫ້ຕົວແທນ AI ສາມາດສ້າງ flow (funnel) ຕັ້ງແຕ່ເລີ່ມຕົ້ນ ລວມທັງຂັ້ນຕອນແຍກສາຂາ ແລະ ເປີດໃຊ້ງານມັນໄດ້. ຄວາມສາມາດໃໝ່ “List Step Types” ຈະສະແດງປະເພດຂັ້ນຕອນທີ່ສາມາດສ້າງໄດ້ ແລະ ການຕັ້ງຄ່າຂອງມັນ ເພື່ອໃຫ້ຕົວແທນສາມາດຄົ້ນພົບສິ່ງທີ່ມີໃຫ້ກ່ອນລົງມືສ້າງ.
• ເພີ່ມ: ຄວາມສາມາດ “List Replacement Codes” ສຳລັບການຄົ້ນຫາແທັກປະສົມ (merge tags) ທີ່ມີໃຫ້ໃຊ້ໃນອີເມວ.
• ເພີ່ມ: ສ່ວນເສີມຕ່າງໆຕອນນີ້ສາມາດລົງທະບຽນໝວດໝູ່ຄວາມສາມາດ ແລະ ຄວາມສາມາດຂອງຕົນເອງຄວບຄູ່ໄປກັບຂອງ Groundhogg ໄດ້ແລ້ວ ແລະ ສາມາດຂະຫຍາຍຮູບແບບຂອງຜູ້ຕິດຕໍ່ ແລະ ກຸ່ມ (segment) ດ້ວຍຊ່ອງຂໍ້ມູນຂອງຕົນເອງໄດ້, ເພື່ອໃຫ້ການເຊື່ອມຕໍ່ WordPress Abilities API ທີ່ນຳສະເໜີໃນ 4.8 ບໍ່ໄດ້ຈຳກັດຢູ່ພຽງແຕ່ສິ່ງທີ່ Groundhogg ມີໃຫ້.
• ປັບປຸງ: ຄວາມສາມາດທີ່ກ່ຽວຂ້ອງກັບອີເມວຕອນນີ້ຖືກຕັ້ງຊື່ໃຫ້ສອດຄ່ອງກັນໂດຍໃຊ້ຄຳວ່າ “email template” (create-email-template, update-email-template, get-email-template) ແທນທີ່ຈະປະສົມກັນລະຫວ່າງ “email” ແລະ “email-template”.
• ປັບປຸງ: ຄຳອະທິບາຍຄວາມສາມາດຕອນນີ້ມີລິ້ງໄປຫາເອກະສານທີ່ກ່ຽວຂ້ອງແລ້ວ ເພື່ອໃຫ້ອ້າງອີງໄດ້ງ່າຍຂຶ້ນເມື່ອເຮັດວຽກກັບຕົວແທນ.

4.8 (10 ກັນຍາ 2026)

• ເພີ່ມ: ຕົວແທນ AI ແລະ ເຄື່ອງມືອື່ນໆ ຕອນນີ້ສາມາດຈັດການ CRM ຂອງທ່ານຜ່ານ WordPress Abilities API ໄດ້ແລ້ວ: ຄົ້ນຫາ ແລະ ຈັດການຜູ້ຕິດຕໍ່ ແລະ ບັນທຶກຂອງພວກເຂົາ, ສ້າງ ແລະ ສົ່ງອີເມວທີ່ບັນທຶກໄວ້ ຫຼື ສົ່ງຄັ້ງດຽວ, ຕັ້ງເວລາ ແລະ ລາຍງານການບຣອດແຄສ ແລະ ເພີ່ມຜູ້ຕິດຕໍ່ເຂົ້າໃນ flows. ທຸກຄວາມສາມາດຈະດຳເນີນການຜ່ານການກວດສອບຄວາມສາມາດ ແລະ ສິດການເຂົ້າເຖິງແຕ່ລະອັນຄືກັນກັບສ່ວນອື່ນໆຂອງ Groundhogg. ນີ້ແມ່ນເວີຊັ່ນທົດລອງເລີ່ມຕົ້ນ — ຄວາມສາມາດເພີ່ມເຕີມ ລວມທັງ SMS ຈະມີມາໃນການອັບເດດຄັ້ງຕໍ່ໄປ.
• ເພີ່ມ: ອອກແບບທາມລາຍກິດຈະກຳຜູ້ຕິດຕໍ່ໃໝ່: ການເຮັດວຽກຂອງ flow ແລະ ຮອບການເຂົ້າຊົມ (browsing sessions) ຈະຖືກຈັດເປັນກຸ່ມທີ່ສາມາດຫຍໍ້ໄດ້ ແລະ ການເປີດອ່ານ ແລະ ຄລິກອີເມວຈະຖືກຊ້ອນຢູ່ກ້ອງອີເມວທີ່ກ່ຽວຂ້ອງ.
  • ເຫດການ flow ທີ່ລົ້ມເຫຼວຕອນນີ້ຈະສະແດງໃນທາມລາຍພ້ອມກັບຂໍ້ຜິດພາດທີ່ເປັນສາເຫດ.
  • ກອງທາມລາຍຕາມ Flow, ອີເມວ ຫຼື ບຣອດແຄສສະເພາະ ຫຼື ຕາມປະເພດກິດຈະກຳ ໂດຍໃຊ້ຕົວເລືອກຕົວກອງໃໝ່.
  • ປຸ່ມ “ໂຫຼດກິດຈະກຳກ່ອນໜ້າ” ເພື່ອເບິ່ງປະຫວັດຜູ້ຕິດຕໍ່ຍ້ອນຫຼັງໄປຕື່ມອີກ.
  • ມີຫົວຂໍ້ວັນທີແບບສຳພັນ (Relative date) ແລະ ຊ່ອງຫວ່າງວັນທີ/ເວລາໃນທາມລາຍເພື່ອໃຫ້ສະແກນຫາໄດ້ງ່າຍຂຶ້ນ.
  • ທາມລາຍຜູ້ຕິດຕໍ່ຕອນນີ້ຈະໂຫຼດໃນການຮ້ອງຂໍພຽງຄັ້ງດຽວ, ດຶງຂໍ້ມູນຕາມຊ່ວງວັນທີແທນການກຳນົດຈຳນວນລາຍການແບບຕາຍຕົວ. ການໂຫຼດໜ້າຈໍໃໝ່ (Refreshing) ແລະ ການປ່ຽນໜ້າ ຈະໂຫຼດສະເພາະສ່ວນໃໝ່ ແລະ ອັບເດດໜ້າຈໍໃນບ່ອນນັ້ນເລີຍ ແທນທີ່ຈະສ້າງມັນຂຶ້ນມາໃໝ່ທັງໝົດ.
• ເພີ່ມ: ບຣອດແຄສຕອນນີ້ຈະເປີດໃນຮູບແບບປະຕິທິນລາຍເດືອນແທນແບບຕາຕະລາງ, ເພື່ອໃຫ້ທ່ານສາມາດເຫັນໄດ້ທັນທີວ່າມີຫຍັງຈະສົ່ງອອກໄປ ແລະ ເວລາໃດ. ຄລິກທີ່ບຣອດແຄສເພື່ອເບິ່ງເວລາສົ່ງ, ຂະໜາດຜູ້ຊົມ ແລະ ສະຖິຕິການເປີດ ແລະ ຄລິກ, ພ້ອມກັບລິ້ງໄປຫາລາຍງານ, ການເບິ່ງຕົວຢ່າງ, ຜູ້ຮັບ ຫຼື ເພື່ອຍົກເລີກມັນ.
  • ຄລິກມື້ໃດກໍໄດ້ຕັ້ງແຕ່ມື້ນີ້ເປັນຕົ້ນໄປເພື່ອຕັ້ງເວລາບຣອດແຄສສຳລັບມື້ນັ້ນ, ໂດຍທີ່ວັນທີຈະຖືກປ້ອນໄວ້ລ່ວງໜ້າແລ້ວ.
  • ກອງຕາມສະຖານະຈາກຄຳອະທິບາຍສັນຍາລັກຂ້າງເທິງປະຕິທິນ: ສົ່ງແລ້ວ, ກຳລັງສົ່ງ, ຕັ້ງເວລາແລ້ວ, ລໍຖ້າດຳເນີນການ ຫຼື ຍົກເລີກແລ້ວ.
  • ເດືອນທີ່ທ່ານກຳລັງເບິ່ງຢູ່ຈະຖືກເກັບໄວ້ໃນແຖບທີ່ຢູ່ (address bar), ດັ່ງນັ້ນການອອກຈາກໜ້າ ແລະ ກັບມາໃໝ່ຈະພາທ່ານກັບຄືນສູ່ບ່ອນທີ່ທ່ານຢູ່ກ່ອນໜ້ານັ້ນ.
  • ຕາຕະລາງເດີມຍັງຄົງຢູ່ເບື້ອງຫຼັງລິ້ງ “ເບິ່ງແບບລາຍຊື່”, ສຳລັບການຄົ້ນຫາ, ການຈັດລຽງ ແລະ ການດຳເນີນການແບບກຸ່ມ. ບໍ່ວ່າທ່ານຈະປ່ຽນໄປໃຊ້ອັນໃດໃນສອງອັນນີ້ ມັນກໍຈະກາຍເປັນຄ່າເລີ່ມຕົ້ນຂອງທ່ານໃນຄັ້ງຕໍ່ໄປທີ່ທ່ານເປີດໜ້ານີ້.
• ເພີ່ມ: ແຖບຕັ້ງຄ່າໄລເຊັນຕອນນີ້ຈະສະແດງແຈ້ງເຕືອນເມື່ອສ່ວນເສີມທີ່ຕິດຕັ້ງໄວ້ບໍ່ມີໄລເຊັນທີ່ເປີດໃຊ້ງານ ຫຼື ໄລເຊັນໝົດອາຍຸ, ພ້ອມກັບມີລິ້ງໄປທີ່ groundhogg.io ເພື່ອຊື້ ຫຼື ຕໍ່ອາຍຸ.
• ເພີ່ມ: ຜູ້ຕິດຕໍ່ທີ່ບໍ່ມີຊື່ ຕອນນີ້ຈະສະແດງຊື່ທີ່ອະນຸມານຈາກທີ່ຢູ່ອີເມວຂອງພວກເຂົາ (ເຊັ່ນ: “jane.doe@example.com” ຈະສະແດງເປັນ “Jane Doe”) ໃນຕາຕະລາງຜູ້ຕິດຕໍ່, ຫົວຂໍ້ໜ້າ ແລະ ບັດໂປຣໄຟລ໌.
• ປັບປຸງ: ລາຍການແບບເລື່ອນລົງ (Dropdowns) ໃນໜ້າແອັດມິນຕອນນີ້ໃຊ້ຕົວເລືອກລາຍການພື້ນຖານຂອງ Groundhogg ແທນໄລບຣາຣີ select2 ທີ່ມາກັບຕົວ, ເພື່ອໃຫ້ຮູບລັກສະນະສອດຄ່ອງກັນ ແລະ ໂຫຼດໜ້າເວັບໄດ້ເບົາຂຶ້ນ.
• ຄວາມປອດໄພ: ການເບິ່ງ, ແກ້ໄຂ, ລຶບ ຫຼື ສ້າງບັນທຶກ ຫຼື ວຽກ (task) ຕອນນີ້ຕ້ອງການສິດເຂົ້າເຖິງຜູ້ຕິດຕໍ່ (ຫຼື ວັດຖຸອື່ນໆ) ທີ່ມັນຕິດຢູ່ດ້ວຍ. ກ່ອນໜ້ານີ້ລຳພັງແຕ່ view_notes / view_tasks ກໍສາມາດເປີດເຜີຍບັນທຶກ ແລະ ວຽກຂອງຜູ້ຕິດຕໍ່ທີ່ຜູ້ໃຊ້ບໍ່ໄດ້ຮັບອະນຸຍາດໃຫ້ເບິ່ງໄດ້, ທັງຜ່ານ REST API ແລະ ທຸກບ່ອນທີ່ມີການກວດສອບຄວາມສາມາດ view_note / view_task.
• ຄວາມປອດໄພ: ລິ້ງທີ່ສະແດງໃນທາມລາຍຜູ້ຕິດຕໍ່ (ເຊັ່ນ: ລິ້ງອີເມວທີ່ຄລິກແລ້ວ) ຈະຖືກກວດສອບກັບລາຍຊື່ຮູບແບບ (scheme allowlist) ທີ່ອະນຸຍາດກ່ອນສະແດງຜົນ ແລະ ລິ້ງທີ່ຍາວໆຈະຖືກຕັດໃຫ້ສັ້ນລົງພ້ອມກັບຟັງຊັນວາງເມົາສ໌ເພື່ອຂະຫຍາຍ.
• ແກ້ໄຂ: ປັອບໂອເວີ (Popovers) ທີ່ຢຶດຕິດກັບບາງສິ່ງບາງຢ່າງໃກ້ກັບຂອບເບື້ອງຂວາຂອງໜ້າຈໍ ອາດຈະຍາວເກີນຂອບອອກໄປ. ຕອນນີ້ພວກມັນຈະຖືກຈັດໃຫ້ຢູ່ພາຍໃນໜ້າຈໍສະແດງຜົນໃນແນວນອນ ເຊັ່ນດຽວກັບທີ່ເຮັດໃນແນວຕັ້ງແລ້ວ.
• ແກ້ໄຂ: ຂັ້ນຕອນ is_entry()/is_conversion() ອາດເຮັດໃຫ້ເກີດຄຳເຕືອນ “Undefined property” ໄດ້.
• ແກ້ໄຂ: ການບຣອດແຄສທີ່ໃຊ້ກຸ່ມເປົ້າໝາຍທີ່ມີຕົວກອງຈາກສ່ວນເສີມທີ່ຫຼ້າສະໄໝ ອາດຈະຕັ້ງເວລາສົ່ງອີເມວຊ້ຳກັນ, ເຊິ່ງຫຼາຍກວ່າຈຳນວນຜູ້ຕິດຕໍ່ໃນກຸ່ມເປົ້າໝາຍຫຼາຍ. ຄຳສັ່ງຊອກຫາຜູ້ຕິດຕໍ່ (contact query) ຈະບໍ່ຕົກໄປໃຊ້ລະບົບເກົ່າຢ່າງງຽບໆອີກຕໍ່ໄປ ແລະ ການບຣອດແຄສແບບນັ້ນຈະຖືກຍົກເລີກພ້ອມກັບແຈ້ງຂໍ້ຜິດພາດ ແທນທີ່ຈະຕັ້ງເວລາສົ່ງ.
• ນັກພັດທະນາ: Abilities API: ຄວາມສາມາດຊຸດທຳອິດຖືກລົງທະບຽນໃນ wp_abilities_api_init, ກວມເອົາ ຜູ້ຕິດຕໍ່ (ດຶງຂໍ້ມູນ, ສ້າງ, ອັບເດດ, ຄົ້ນຫາ, ບັນທຶກ), ແທັກ, ເຈົ້າຂອງ, ຊ່ອງຂໍ້ມູນກຳນົດເອງ ແລະ ການຄົ້ນຫາທີ່ບັນທຶກໄວ້; ອີເມວ (ສ້າງ, ສະແດງລາຍຊື່ ແລະ ສົ່ງອີເມວທີ່ບັນທຶກໄວ້, ສະແດງໂປຣໄຟລ໌ຜູ້ສົ່ງ, ສົ່ງອີເມວທີ່ບັນທຶກໄວ້ ຫຼື ຂຽນໃໝ່ໄປຫາຜູ້ຕິດຕໍ່ສະເພາະ); ບຣອດແຄສ (ຕັ້ງເວລາໃຫ້ກຸ່ມເປົ້າໝາຍ ໂດຍສາມາດເລືອກແບ່ງສົ່ງເປັນຊຸດໄດ້, ສະແດງລາຍຊື່, ຍົກເລີກ, ອ່ານລາຍງານການເປີດ/ຄລິກ); ແລະ flows (ສະແດງລາຍຊື່, ເພີ່ມຜູ້ຕິດຕໍ່ ຫຼື ກຸ່ມເປົ້າໝາຍ). ຄວາມສາມາດຕ່າງໆຈະຢູ່ໃນ includes/abilities/, ແຕ່ລະອັນຈະຂະຫຍາຍ \Groundhogg\Abilities\Ability; ຮູບແບບຜົນໄດ້ຮັບທີ່ນຳມາໃຊ້ໃໝ່ໄດ້ແມ່ນ \Groundhogg\Abilities\Schemas\Schema subclasses.
• ນັກພັດທະນາ: ວັດຖຸກຳນົດເອງ (ທົດລອງໃຊ້ — ຮູບແບບໂຄງສ້າງ ແລະ API ອາດປ່ຽນແປງ): ລົງທະບຽນປະເພດວັດຖຸນ້ຳໜັກເບົາດ້ວຍ register_custom_object( $type, $args ) ແທນການສ້າງຕາຕະລາງແຍກສະເພາະ. ແຕ່ລະປະເພດຈະຖືກສະໜັບສະໜູນໂດຍຕາຕະລາງທີ່ແບ່ງປັນກັນ gh_objects / gh_object_meta ແລະ ປະມວນຜົນຜ່ານ get_db(), create_object_from_type(), ແລະ ຕົວສ້າງ query ເໝືອນກັບວັດຖຸຫຼັກທົ່ວໄປ. ຂະຫຍາຍ (Extend) \Groundhogg\Custom_Object ສຳລັບຄລາສ runtime ທີ່ລະບຸປະເພດ. ສົ່ງ 'show_in_rest' => false ເພື່ອຂ້າມ gh/v4/objects/{type} ຕົວຄວບຄຸມ REST (CRUD, meta, ຄວາມສຳພັນ) ແລະ ໃຫ້ປະເພດນັ້ນເປັນແບບ PHP ເທົ່ານັ້ນ.
• ນັກພັດທະນາ: Contact_Query::used_legacy_fallback() ຈະສະແດງໃຫ້ເຫັນເມື່ອຄຳສັ່ງ query ຕົກໄປໃຊ້ລະບົບເກົ່າ (legacy engine); ມີ action ໃໝ່ groundhogg/contact_query/legacy_fallback ແລະ ຕົວກອງ groundhogg/contact_query/throw_on_legacy_fallback.
• ນັກພັດທະນາ: view_note / view_task (ແລະ ຟັງຊັນການແກ້ໄຂ/ລຶບຂອງພວກມັນ) ຕອນນີ້ຈະຖືກສົ່ງຕໍ່ໄປກວດສອບການເບິ່ງຢູ່ໃນວັດຖຸທີ່ກ່ຽວຂ້ອງນຳ. ຕົວກອງໃໝ່ groundhogg/roles/note_association_cap_check_types ຄວບຄຸມວ່າປະເພດທີ່ກ່ຽວຂ້ອງໃດແດ່ທີ່ຈະເຂົ້າຮ່ວມ (ຄ່າເລີ່ມຕົ້ນຄື ຜູ້ຕິດຕໍ່, ຂໍ້ຕົກລົງ, ບໍລິສັດ); ປະເພດທີ່ຖືກຍົກເວັ້ນຈະຮັກສາພຶດຕິກຳເດີມທີ່ໃຊ້ຄວາມສາມາດ view_notes / view_tasks ແບບຄອບຄຸມບວກກັບການກຳນົດຂອບເຂດຜູ້ຂຽນ.
• ນັກພັດທະນາ: ຄອມໂພເນນເບິ່ງແບບເດືອນ MakeEl.Calendar ໃໝ່. ພຽງແຕ່ສົ່ງອາເຣຂອງເຫດການ ບວກກັບ getEventDate ແລະ renderEvent ໃຫ້ມັນ, ມັນກໍຈະຈັດການຕາຕະລາງ, ການລົ້ນໃນແຕ່ລະມື້ (“+ ອີກ N ລາຍການ”), ການຄລິກມື້ ແລະ ເຫດການ ແລະ ການປ່ຽນເດືອນໃຫ້ເລີຍ; dayProps ແລະ eventProps ໃຊ້ເພີ່ມ classes ແລະ attributes ໃນແຕ່ລະຊ່ອງ ຫຼື ປ້າຍ (chip). ເດືອນທີ່ສະແດງສາມາດປ່ອຍໃຫ້ຄອມໂພເນນຈັດການເອງ ຫຼື ຄວບຄຸມຈາກພາຍນອກດ້ວຍ prop month ແລະ onMonthChange ກໍໄດ້, ເຊິ່ງເປັນສິ່ງທີ່ທ່ານຕ້ອງການເມື່ອຕ້ອງດຶງເຫດການຂອງແຕ່ລະເດືອນມາ. ນອກຈາກນີ້ຍັງມີການສົ່ງອອກ: mergeAttributes ແລະ ຕົວຊ່ວຍເລື່ອງວັນທີ toDate, startOfDay, startOfMonth, dayKey, addDays, ແລະ addMonths. enqueue_broadcast_calendar_assets() ຈະໂຫຼດສະຄຣິບ ແລະ ສະໄຕລ໌ຂອງປະຕິທິນບຣອດແຄສເອງ.
• ນັກພັດທະນາ: gh/v4/broadcasts ຮອງຮັບ context=embed, ເຊິ່ງຈະຕັດອີເມວ ຫຼື SMS ທີ່ຢູ່ເບື້ອງຫຼັງການບຣອດແຄສແຕ່ລະອັນອອກຈາກການຕອບກັບລາຍຊື່. ການປະມວນຜົນບຣອດແຄສແບບເຕັມຍັງມີການສ້າງ ແລະ ປະສົມຂໍ້ຄວາມທັງໝົດ, ເຊິ່ງກິນຊັບພະຍາກອນຫຼາຍເກີນໄປສຳລັບການດຶງຂໍ້ມູນເທື່ອລະໜຶ່ງເດືອນ.
• ນັກພັດທະນາ: ການຕັ້ງເວລາບຣອດແຄສຈະສົ່ງເຫດການ groundhogg/broadcast/scheduled ໄປເທິງ document, ພ້ອມກັບບຣອດແຄສໃໝ່ໃນ event.detail.broadcast.
• ນັກພັດທະນາ: admin.js ບໍ່ໄດ້ເພິ່ງພາ select2 ອີກຕໍ່ໄປ. ເມື່ອ $.fn.select2 ບໍ່ຖືກກຳນົດ ລະບົບ polyfill ທີ່ສະໜັບສະໜູນໂດຍ MakeEl.ItemPicker ຈະຖືກລົງທະບຽນເຊິ່ງຈະຈັບຄູ່ຕົວເລືອກ select2 ທີ່ຍັງໃຊ้อยู่ (data, ajax, multiple, tags, placeholder, allowClear) ແລະ ຮັກສາ <select> ທີ່ຢູ່ເບື້ອງຫຼັງໃຫ້ກົງກັນຢູ່ສະເໝີ, ເພື່ອໃຫ້ .select2().on('change', ...) / .val() ແລະ ການສົ່ງຟອມຍັງຄົງເຮັດວຽກໄດ້.

4.7.2 (3 ກັນຍາ 2026)

• ເພີ່ມ: ຄລິກທີ່ຮູບໂປຣໄຟລ໌ຂອງຜູ້ຕິດຕໍ່ເພື່ອອັບເດດມັນດ້ວຍຮູບພາບຈາກຄັງສື່ (Library).
• ປັບປຸງ: ປັບລະບົບໄລເຊັນ ແລະ ການອັບເດດໃຫ້ທັນສະໄໝຂຶ້ນ.
• ແກ້ໄຂ: ຊ່ອງໂຫວ່ Path Traversal ສຳລັບຜູ້ທີ່ຢືນຢັນຕົວຕົນແລ້ວ (Sales Rep+). ຂໍຂອບໃຈ @Sergei Pro ທີ່ລາຍງານຢ່າງມີຄວາມຮັບຜິດຊອບຜ່ານ PatchStack.
• ແກ້ໄຂ: ຄວາມເປັນໄປໄດ້ໃນການໂຈມຕີແບບປ່ຽນທິດທາງ (Phishing). ຂໍຂອບໃຈ @Yaswanth Reddy Sunkara ທີ່ລາຍງານຢ່າງມີຄວາມຮັບຜິດຊອບຜ່ານ WPScan.

4.7.1 (20 ສິງຫາ 2026)

• ແກ້ໄຂ: ບັນຫາໜ້າຕັ້ງຄ່າ Cron ໃນ WP 7.1
• ແກ້ໄຂ: ບັນຫາຄວາມບໍ່ເຂົ້າກັນກັບ PHP 7.4.
• ປັບປຸງ: ຍົກລະດັບເວີຊັ່ນ PHP ຂັ້ນຕ່ຳທີ່ຮອງຮັບຂຶ້ນເປັນ 7.4.
• ປັບປຸງ: ຍົກລະດັບເວີຊັ່ນ WP ຂັ້ນຕ່ຳທີ່ຮອງຮັບຂຶ້ນເປັນ 6.9.

4.7 (20 ສິງຫາ 2026)

• ເພີ່ມ: ໂປຣໄຟລ໌ຜູ້ສົ່ງແບບກຳນົດເອງໃນ Groundhogg » ການຕັ້ງຄ່າ » ອີເມວ » ໂປຣໄຟລ໌ຜູ້ສົ່ງ.
• ເພີ່ມ: ຖ້າອີເມວຖືກສົ່ງຈາກຜູ້ໃຊ້, ຜູ້ໃຊ້ນັ້ນສາມາດຕັ້ງຄ່າຂຽນທັບ “ຊື່ຜູ້ສົ່ງ” ແລະ “ອີເມວຜູ້ສົ່ງ” ໃນໂປຣໄຟລ໌ຜູ້ໃຊ້ຂອງຕົນເອງໄດ້.
• ເພີ່ມ: ເມື່ອສົ່ງອີເມວທົດສອບ ຕອນນີ້ມີຕົວເລືອກໃຫ້ກັອບປີ້ລິ້ງເບິ່ງຕົວຢ່າງເພື່ອແບ່ງປັນກັບທີມງານໄດ້ແລ້ວ.
• ປັບປຸງ: ອີເມວຕອນນີ້ໃຊ້ “ໂປຣໄຟລ໌ຜູ້ສົ່ງ” ແທນທີ່ຈະເປັນ “ຈາກຜູ້ໃຊ້” ເພື່ອໃຫ້ສາມາດເພີ່ມໂປຣໄຟລ໌ຜູ້ສົ່ງແບບກຳນົດເອງໄດ້.
• ແກ້ໄຂ: ບັດຂໍ້ມູນຂໍ້ຕົກລົງ (Deals info card) ເພພັງຫຼັງຈາກການອັບເດດຄັ້ງຫຼ້າສຸດ.
• ແກ້ໄຂ: ການຕັ້ງຄ່າຕາມຄຳແນະນຳບໍ່ໂຫຼດ.

4.6.1 (18 ສິງຫາ 2026)

• ແກ້ໄຂ: ບລັອກແບບ Global ທີ່ຊ້ອນກັນຢູ່ ບໍ່ໂຫຼດ CSS.

4.6 (15 ສິງຫາ 2026)

• ເພີ່ມ: ຂັ້ນຕອນຕັກກະ “ປ່ຽນເສັ້ນທາງ (Reroute)” ແບບໃໝ່, ຊ່ວຍໃຫ້ສາມາດປ່ຽນເສັ້ນທາງຜູ້ຕິດຕໍ່ໄປຍັງຈຸດ (node) ການກະທຳອື່ນໆໃນ flow ໄດ້, ຈາກບ່ອນໃດກໍໄດ້ໃນ flow.
• ປັບປຸງ: ກຸ່ມຍ່ອຍຂັ້ນຕອນ flow “ຕັກກະ (Logic)” ໄດ້ປ່ຽນຊື່ເປັນ “ການກຳນົດເສັ້ນທາງ (Routing)”
• ປັບປຸງ: ຂັ້ນຕອນຕັກກະ “ລຳດັບວັນທີອັດສະລິຍະ (Smart Date Sequence)” ໄດ້ປ່ຽນຊື່ເປັນ “ຊິງຄ໌ວັນທີ (Date Sync)”
• ປັບປຸງ: ຂັ້ນຕອນຕັກກະ “ຂ້າມ (Skip)” ແລະ “ວົນຊ້ຳ (Loop)” ຖືກຍົກເລີກການນຳໃຊ້ແລ້ວ (ມີໃຫ້ໃຊ້ໃນຖານະຂັ້ນຕອນແບບເກົ່າ) ເນື່ອງຈາກຂັ້ນຕອນປ່ຽນເສັ້ນທາງ (Reroute) ສາມາດເຮັດສິ່ງດຽວກັນແຕ່ເຮັດໄດ້ດີກວ່າ.

4.5.15 (27 ກໍລະກົດ 2026)

• ເພີ່ມ: ການຕັ້ງຄ່າ “ໂຫຼດໜ້າໃໝ່ (Reload page)” ຫຼັງຈາກສົ່ງຟອມ.
• ເພີ່ມ: ທາມລາຍຜູ້ຕິດຕໍ່ຕອນນີ້ຈະສະແດງກິດຈະກຳ ແລະ ເຫດການຈາກ flows ສຳລັບຕົວແທນຂາຍ ແລະ ຜູ້ຈັດການແລ້ວ.
• ແກ້ໄຂ: ບັນຫາສິດການເຂົ້າເຖິງ API ຫຼາຍຢ່າງ.
• ແກ້ໄຂ: ຕົວແກ້ໄຂອີເມວຂັດຂ້ອງຫຼັງຈາກລາກບລັອກຈາກ namespace ຂອງບລັອກແບບ Global ໄປຍັງ namespace ຫຼັກ.
• ແກ້ໄຂ: i18n ບໍ່ເຮັດວຽກໃນໄຟລ໌ JS.
• ແກ້ໄຂ: ຄຳອະທິບາຍສຳລັບນັກແປທີ່ຫາຍໄປ, ການໃຊ້ gettext ທີ່ບໍ່ຖືກຕ້ອງ ແລະ ຂໍ້ບົກຜ່ອງກ່ຽວກັບການແປພາສາອື່ນໆໃນໄຟລ໌ JS.
• ຄວາມປອດໄພ: ແກ້ໄຂຊ່ອງໂຫວ່ Cross-Site Scripting ທີ່ຖືກລາຍງານຢ່າງມີຄວາມຮັບຜິດຊອບໂດຍ @thevietronin
• ຄວາມປອດໄພ: ແກ້ໄຂຊ່ອງໂຫວ່ SQL Injection ທີ່ຖືກລາຍງານຢ່າງມີຄວາມຮັບຜິດຊອບໂດຍ @JonathanDersch

4.5.14 (20 ກໍລະກົດ 2026)

• ເພີ່ມ: ບລັອກຫົວຂໍ້ (Heading block) ໃໝ່ໃນຕົວສ້າງອີເມວ.
• ປັບປຸງ: ລຶບ www. ອອກຈາກ URLs ທີ່ໄປຫາ Groundhogg.io
• ແກ້ໄຂ: ຂໍ້ຜິດພາດ UI ໃນຕົວກອງຄົ້ນຫາວັນທີ.

4.5.13 (10 ກໍລະກົດ 2026)

• ປັບປຸງ: ລຶບການແຈ້ງເຕືອນຂໍຣີວິວທີ່ລົບກວນໃນທົ່ວເວັບໄຊອອກ ແລະ ປ່ຽນເປັນຄຳຂໍໃນໜ້າປັດ (dashboard) ທີ່ລົບກວນໜ້ອຍລົງ.
• ຄວາມປອດໄພ: ແກ້ໄຂຊ່ອງ dropdown ແລະ ປຸ່ມ radio ທີ່ບໍ່ບັງຄັບໃຫ້ກວດສອບຂໍ້ມູນປ້ອນເຂົ້າໄດ້ຢ່າງຖືກຕ້ອງ. ໃຫ້ເຄຣດິດ Artus KG ທີ່ລາຍງານຢ່າງມີຄວາມຮັບຜິດຊອບ.

4.5.12 (9 ກໍລະກົດ 2026)

• ແກ້ໄຂ: ຕົວກອງບົດບາດຜູ້ໃຊ້ (user role filter) ທີ່ເພພັງ.

4.5.11 (6 ກໍລະກົດ 2026)

• ເພີ່ມ: ລາຍງານສະຫຼຸບບັນທຶກລະບົບ (Log summary) ໃນ ບັນທຶກລະບົບ (Logs) » ຈັດການ.
• ແກ້ໄຂ: ເຄື່ອງມືລຶບເຫດການທີ່ລົ້ມເຫຼວ (Purge failed events) ບໍ່ເຮັດວຽກ.
• FIXED Dismissed notifications appearing as …