Multi Problem Over Different Vendors, Helix, SP Pagebuilder, Event Booking On IOS Safari - Question | JoomShaper
Black Friday sale is live with flat 50% OFF. Sale ends soon! Grab your deal now!

Multi Problem Over Different Vendors, Helix, SP Pagebuilder, Event Booking On IOS Safari

T

Torsten.S

SP Page Builder 20 hours ago

Well, longer Text, also to Template Builder / Maintainer, Event Booking and so on

Issue: Square Card Payment field failing intermittently on iOS Safari Component: EventBooking 5.3.1 Payment Plugin: os_squarecard 4.5.0 CMS: Joomla 5.4.1 Template: LT Joyfull with Helix Ultimate + SP Pagebuilder Description of the Problem

Square’s embedded card payment fields inside EventBooking work on:

Desktop (Firefox, Chrome, Safari)

Android (Chrome)

Some iOS Safari versions (e.g., iOS 15.8.5 confirmed working)

However, on many newer iOS Safari builds, the checkout process fails in one of these ways:

A) The Square card iframe loads, but the Terms checkbox becomes unclickable

Safari WebKit appears to create an invisible overlay/hitbox above the form elements, preventing interaction with:

Terms & Conditions checkbox

Sometimes the Captcha field

The iframe is visually correct but sits on a higher z-index on iOS.

B) On certain iOS versions the payment does not complete

The user presses Register & Pay, but:

Nothing happens, OR

The page reloads back to /tickets, OR

The Square token is never generated

This only occurs on iOS Safari — Android and PC work reliably.

Technical Findings • The Square iframe loads correctly

The browser console confirms:

main-iframe.html loaded successfully Square JS v1 loaded Card Element initialized

• CSS/JS overlays from the template previously caused click-blocking

This was fixed by removing all custom CSS/JS overrides.

After cleanup:

✔ Terms checkbox works ✔ Captcha works ✔ Square iframe visible ✔ Payments succeed on iOS 15.8.5

• However, failures still occur on newer iOS Safari versions

Based on user reports and logs.

Relevant Access Log Example (Successful iOS Purchase) “POST /tickets?task=cart.process_checkout” 303 “GET /tickets/registration-complete” 200 User-Agent: iPhone OS 15_8_5 Safari/604.1

This confirms the flow works in some iOS environments.

Remaining Problem

Despite the success on certain versions, other iOS Safari builds still show:

Inability to click the Terms checkbox

Square token not generated

Payment form not completing

Random failures depending on iOS WebKit version

This suggests an issue with:

❗ Square Web Payments SDK + iOS WebKit iframe interaction

AND/OR

❗ The outdated os_squarecard 4.5.0 plugin implementation inside EventBooking 5. Request for Support For Square Support:

Please confirm whether the Web Payments SDK version that EventBooking uses (likely older) has known issues on:

iOS 17.x

iOS 18.x

Safari’s dynamic state partitioning

iframe hitbox / focus handling

token generation failures on embedded forms

We need guidance on:

Any required JS updates for iOS WebKit.

Whether Square recommends replacing embedded card forms with Web Payments SDK v2.

A fix for iframe sizing or focus issues on Mobile Safari.

For EventBooking (JoomDonation) Support:

Does os_squarecard 4.5.0 include the latest Square Web Payments SDK?

Has the plugin been updated for iOS 17–18 WebKit changes?

Are there known issues with:

iframe overlay sizes

token creation callbacks

z-index / transform handling on iOS Safari

Can you provide an updated plugin version or patch?

Users on newer iPhones are still experiencing failed checkouts, even though older iOS versions now work reliably.

Additional Information

CSP rules are correctly configured (fonts, frame-src, script-src).

No caching system is active.

The iframe loads successfully in all tests.

The issue is specific to Safari on iOS, not macOS Safari.

Your assistance is needed to verify:

Whether the Square JS implementation in EventBooking is up-to-date,

Whether known Square Web Payments issues with iOS Safari apply here,

And if a plugin update or patched SDK integration is required.

With the default Joomla 5.4.1 Template Cassiopeia these issues don’t exist.

The problem is that the templates, as well as Helix, SP Page Builder, etc., are not coded cleanly enough and repeatedly cause issues. Especially when you choose such a technology because you want—or need—to spend less time working on the template, it seems to have the opposite effect. You end up spending more time fixing the various template and plugin bugs from the various vendors than on actually building the website itself.

Certainly this won’t convince me to renew my business subscription. The websites may look nice and appealing, but once you try to adapt them to your own needs, things quickly fall apart. You soon realize that they were thrown together poorly and done in a rush .

So maybe i get a xmas gift und people start fixing some stuff. (Also went to LT Themes and so on)

0
0 Answers