After updating to Bricks Builder version 1.9.7.1, a critical issue arises where customers can place orders without encountering a payment confirmation step. Despite entering credit card details on the payment page, the order is immediately marked as complete in WooCommerce orders, with a total cost of $0.00. It appears the payment gateway does not record any transaction, and the order status transitions from pending to completed without capturing customer information. This occurs even if the customer has not previously registered on the site and logs in through âGoogle Sign-Inâ during the checkout process. After confirming the order on the payment page, customers are directed to the âThank Youâ page, indicating the order has been placed successfully, despite no payment being processed.
Steps to Reproduce:
- Update Bricks Builder to version 1.9.7.1.
- Clear all caches post-update, including LiteSpeed Cache and any other caching mechanisms in use.
- Use WooCommerce tools to reset all cookies, sessions, and related settings to ensure a clean state.
- As an unregistered user, attempt to place an order on a WooCommerce site using the updated Bricks Builder.
- Be redirected to the login page when trying to access the payment page.
- Log in using âGoogle Sign-Inâ.
- Return to the payment page, enter payment information, and confirm the order.
- Be directed to the âThank Youâ page as if the order has been placed successfully.
- Observe that the order completes without a payment confirmation step, and is marked with a total cost of $0.00.
Expected Result: The order should only be marked as complete after a successful payment transaction, with the correct total cost reflected, customer information captured, and the customer receiving accurate confirmation of the order status.
Actual Result: The order is incorrectly marked as complete with a total cost of $0.00, no payment transaction is recorded, no customer information is captured, and customers are misled by being directed to the âThank Youâ page, suggesting a successful order placement.
Impact: This issue not only prevents successful transactions on WooCommerce sites using Bricks Builder, potentially leading to significant loss of revenue and customer trust but also confuses customers by suggesting a successful transaction without actual payment.
Possible Areas to Investigate:
- Integration between Bricks Builder 1.9.7.1 and WooCommerce payment gateways, especially in scenarios involving third-party login methods like âGoogle Sign-Inâ.
- Order completion workflow in Bricks Builderâs WooCommerce integration, particularly post-login redirect and payment confirmation processes, including the redirection to the âThank Youâ page without payment verification.
- The impact of LiteSpeed Cache settings on the checkout process, specifically the exclusion of certain pages, query strings, and cookies.
- The role of security measures implemented by Wordfence Security and how they may interact with the checkout and login processes.
- The effect of clearing caches and resetting WooCommerce settings post-update on the functionality.
System Environment:
- Bricks Builder Version: 1.9.7.1
- WordPress Version: 6.4.3
- WooCommerce Version: 8.6.1
- WooCommerce Social Login by SkyVerge Version: 2.15.1
- POS Integrator by GurmeHub Version: 2.6.25
- LiteSpeed Cache Version: 6.1, excluding pages and queries related to login, cart, payment, and cookies like
wp_woocommerce_session,wc-api. - Wordfence Security Version: 7.11.4
- PHP Version: 8.1.27
- Any relevant plugins/extensions that might affect the checkout process, including third-party authentication methods.
Additional Notes:
- Specific cache and security settings are configured to ensure the smooth operation of WooCommerce functionalities, suggesting an incompatibility or bug introduced with the recent Bricks Builder update.
- Post-update actions included clearing all cache types and resetting WooCommerce cookies, sessions, and related settings to mitigate potential conflicts.
- Customers being directed to the âThank Youâ page without actual payment collection adds an additional layer of complexity to the issue, potentially affecting customer satisfaction and trust.