AjaxPress – SPA & Ajax Navigation with Persistent Audio Player for Radio

Журнал змін

2.4.2

• Fix: Opening a page in a visual builder could leave the builder blank or unresponsive. Divi, Bricks, Beaver Builder, Oxygen, Breakdance, WPBakery, Visual Composer, Zion, Thrive and Brizy all open on the ordinary front-end address of the page with a marker on the end, and AjaxPress was treating that as a page to take over. It now recognises a builder session and stays out of it entirely, on the page itself and on any link leading to one. The Customizer preview is treated the same way
• Fix: Google Analytics 4 reported “Average engagement time” as zero on every page. Analytics measure engagement against the page the visitor is looking at, and that page had never been handed keyboard focus, so no time was ever counted however long someone stayed. Engagement is measured again, for Google Analytics and for any other script that works the same way
• Fix: Cookie and consent banners could appear twice on the first page someone loads, along with anything else a script adds after the page is ready – promo popups, chat widgets, sticky bars. Only one copy is shown now
• Fix: A form could be submitted twice when the plugin behind it attaches its handler to the page rather than to the form. The entry was saved, but the plugin’s own follow-up – the confirmation message, the notification email – could be cut off part way. Forms whose plugin attaches to the form itself, which is most of them, were never affected
• New: Add data-ajaxpress-ignore-submit to a form, or to anything containing it, to keep it out of ajax submission entirely and let it submit the ordinary way
• Fix: Mini carts and other panel toggles still navigated away on 2.4.1 when the theme opens the panel from a shared click handler rather than one attached to the link itself, which is what most themes do. Tapping the cart icon opened the mini cart and then landed the visitor on the cart page anyway
• Fix: A page’s own script could stop running partway through. Where a persistent player was carried over, the copy on the incoming page was taken out before that page’s script looked for it, so the script hit a missing element and everything after it in the same block never ran, commonly other footer features like popups

2.4.1

• Fix: Media players kept on screen across navigation stopped responding – Play, Stop and open/close buttons did nothing, with no error and no sound. The player is now carried over as the live element instead of being rebuilt from its markup, so whatever script powers it keeps working
• Fix: A persistent player could be dropped mid-navigation on slower pages – the audio simply stopped. Pages that are still loading when navigation completes are no longer mistaken for pages that have no player
• Fix: Links that act as buttons now keep working – a WooCommerce or theme mini cart, offcanvas panels, mega menu and search toggles, quick view. Tapping one opened its panel and then navigated to the link’s page anyway, which on mobile dropped shoppers on the cart page. WooCommerce’s ajax “Add to cart” was affected the same way and added the product by reloading the page instead
• Changed: The plugin now ships its unminified JavaScript sources, so the code behind the minified bundles can be read and rebuilt from the download itself
• Changed: The readme now documents every external service AjaxPress can talk to, what triggers each one and what is sent: PackEdge, Cloudflare, our Cloudflare OAuth relay, and the optional deactivation feedback form
• Changed: The optional deactivation feedback form no longer sends your WordPress username. Only the reason, your comment and the site URL are sent, and only if you submit the form

2.4.0

• New: Connect to Cloudflare in one click with OAuth – no API token to create or paste (where available; pasting a token still works everywhere)
• New: “Don’t cache this page” toggle in the editor (classic and block), for pages that should always be served fresh
• New: Dynamic pages are excluded from edge caching automatically – WooCommerce cart, checkout and account, add-to-cart links, and anything that sets cookies or uses nonces
• New: Cache health readout and a Pause switch to stop edge caching instantly without disconnecting
• New: Edits appear without anyone waiting. Update a page and the next visitor gets the existing copy instantly while Cloudflare fetches the new version behind them – you publish, it appears, and nobody has to purge anything
• New: “Scan my pages” finds pages that should not be cached (cookies, security tokens, forms) and excludes them in one click
• Improved: The Cache screen is reorganised – everything about excluding pages in one place, rarely-used settings tucked behind “Show advanced settings”
• New: Optional second cache layer that keeps a globally shared copy of your pages, so visitors in regions that have not loaded a page yet are still served by Cloudflare rather than your server
• New: Exclude individual posts and pages by searching for them, and exclude whole categories, tags or other taxonomy terms
• New: Configurable edge cache lifetime and exclude-URL list
• Improved: Edge page caching now reliably caches HTML and applies changes without redeploying the Cloudflare worker
• Improved: The Cache screen shows whether your Cloudflare account is connected and how, and returning from the Cloudflare authorization screen lands back on the Cache settings with a clear result message
• New: Logging in and registering now work over ajax with no page refresh, the same as the rest of your site. This includes the WooCommerce My Account login and registration forms, and a failed login shows its error in place
• New: The WordPress login screen (wp-login.php) is now part of the SPA. Signing in, registering, and resetting a password no longer reload the page, and a failed attempt shows its error in place. If a login sends you outside the SPA, such as the dashboard, AjaxPress hands over to a normal page load. Opt out with the full page reload setting for auth forms or the ajaxpress_ajax_login filter
• New: Full Page Reload on Login & Registration setting, off by default, for sign-in flows that need a real page load
• Fixed: Logging in or registering through WooCommerce My Account did nothing when AjaxPress was active. The clicked button’s value was dropped from intercepted submissions, which WooCommerce relies on. This also affected contact forms, search filters, and admin save buttons
• Fixed: Forms containing a field named “action”, “method”, “submit”, or “target” broke form handling entirely. Nearly every WordPress admin form uses this pattern, as does any plugin form posting to admin-ajax.php or admin-post.php
• Fixed: Forms whose own JavaScript submits them, such as the classic WooCommerce checkout and most contact form plugins, could be submitted twice
• Fixed: On a freshly loaded or reloaded page, submitting a form could reload the whole page instead of submitting over ajax, while the same form worked after navigating to the page from elsewhere. The page shell’s duplicate copy of the form is now disabled, and anything reaching it is routed through ajax
• Fixed: WooCommerce notices were missing after a form submission, so failed logins showed no error
• Fixed: A persistent player kept playing on pages that do not include one. Player continuity now follows the page: added when a page has one and the shell does not, kept playing when the next page has the same one, removed when the next page has none
• Fixed: A persistent audio or video player could carry over from the frontend into the WordPress dashboard and keep playing there. The frontend and the dashboard never share a player: moving between them is always a normal page load
• Fixed: Several admin dashboard screens did not save correctly with SPA for Admin Dashboard enabled
• Changed: On WordPress 7.0 and newer the settings screen recommends leaving SPA for Admin Dashboard off, since WordPress now navigates the dashboard itself. On older versions it stays highlighted

For full changelog, see changelog.txt