Resolving Missing OpenCart Delivery Locker Data After Online Payments: A Sameday, LibraPay, and Journal 3 Investigation

An OpenCart community forum topic recently highlighted a critical issue where selected Sameday Easybox locker details disappear after customers complete online payments via the LibraPay module, while Cash on Delivery (COD) payments work flawlessly. This scenario, reported by Cristina12 on the OpenCart forum, points to a common type of extension conflict often encountered in complex OpenCart setups involving custom themes and multiple third-party modules.

The Problem: Lost Locker Information After Online Payment

Cristina12's post clearly outlines the problem: on an OpenCart 3.0.3.8 store running the Journal 3 theme, the Sameday Easybox delivery option works perfectly with COD. The selected locker is saved, visible in the admin, and in the Sameday extension section. However, when customers use the LibraPay card payment module, the Easybox locker information is not saved to the order, nor is it present in the database after the transaction is completed. This suggests a specific interaction breakdown during the online payment processing phase.

Why Does This Happen? Common Causes of Data Loss in OpenCart Checkout

Such issues typically arise from conflicts in how different modules handle session data, order processing, and redirects during the checkout flow. Here are the most common culprits:

• Payment Gateway Redirects: Online payment modules often redirect the user to an external gateway and then back to the store. During this round trip, session data might be lost, cleared, or not properly re-initialized if not handled correctly by the payment module or other extensions.
• Order Confirmation Timing: The Sameday extension might be attempting to save its locker data at a stage in the checkout process that occurs *before* the online payment module finalizes the order, or before the session data is properly re-established upon return from the payment gateway.
• Session Management Differences: COD typically finalizes an order directly on the site without external redirects, preserving session data more consistently. Online payments introduce complexities that can expose weak points in session handling.
• Journal 3 Checkout Overrides: Journal 3 extensively modifies the OpenCart checkout. It's possible its custom checkout logic interferes with how the Sameday extension injects or retrieves its data, especially when combined with a specific payment gateway like LibraPay.
• Missing Database Fields or Incorrect Saving Logic: While Cristina12 verified the data was missing from the database, the root cause could be that the Sameday extension's saving logic isn't triggered or fails silently when the LibraPay module completes its process.

Actionable Troubleshooting and Debugging Steps

To resolve this, a systematic debugging approach is crucial. As khnaz35 suggested, a test store is invaluable for this process.

1. Pinpoint When Sameday Data Disappears

• Session Inspection: Before redirecting to LibraPay, check if the Sameday locker data is stored in the session (e.g., $_SESSION['sameday_locker_details'] or similar). After returning from LibraPay, check the session again. This will tell you if the data is lost during the redirect.
• Order Object Inspection: During the checkout/confirm and checkout/success stages, inspect the $this->session->data['order_id'] and the order data array being saved to the database. Look for where the Sameday data is expected to be attached.

2. Examine the LibraPay Payment Module

• Success Callback/Return Logic: Focus on the LibraPay module's controller files (e.g., catalog/controller/extension/payment/librapay.php). Look for methods like callback(), confirm(), or success(). These are where the order is typically finalized after a successful payment.
• Data Clearing: Check if the LibraPay module explicitly clears or unsets session variables that might be holding the Sameday data. Sometimes payment modules aggressively clean up session data to prevent duplicate orders or ensure a fresh state.
• Order Update Hooks: Does LibraPay use standard OpenCart models to update the order status and data (e.g., $this->model_checkout_order->addOrderHistory())? Ensure it's not bypassing or overriding standard data saving mechanisms.

3. Investigate the Sameday Journal 3 Extension

• Data Saving Logic: Review the Sameday extension's files (likely in catalog/controller/extension/shipping/sameday.php and catalog/model/extension/shipping/sameday.php). Identify where and how the locker information is saved to the order or database.
• Journal 3 Compatibility: Many extensions provide specific compatibility patches or instructions for Journal 3. Double-check if the Sameday extension has any Journal-specific settings or requirements that might be missed. Journal 3 often uses its own AJAX-based checkout, which can change when and how session data is processed.

4. Debugging Tools and Techniques

• OpenCart Error Logs: Enable detailed error logging in OpenCart and check for any related warnings or errors during the LibraPay checkout process.
• var_dump() and exit(): Strategically place var_dump($_SESSION); exit(); or var_dump($order_data); exit(); at various points in the LibraPay and Sameday module code to inspect variable states.
• XDebug: For more advanced debugging, use XDebug to step through the code execution flow, especially around the payment confirmation and order saving stages.

Potential Solutions and Next Steps

Given that the developer of the Sameday extension has not responded, the immediate path forward involves either deeper self-investigation or hiring a specialized OpenCart developer.

• Custom Code Modification: The most likely solution will involve modifying either the LibraPay module's success callback or the Sameday module's data saving logic. The goal is to ensure that the Sameday locker data is explicitly saved to the order object *after* the LibraPay payment is confirmed and *before* the order is fully finalized in the database. This might involve hooking into OpenCart's event system if available, or directly modifying the module files.
• Journal 3 Integration: If Journal 3 is heavily customizing the checkout, ensuring that the Sameday data is correctly passed through Journal's custom checkout steps to the final order confirmation is key.
• Contacting LibraPay Support: While the Sameday developer is unresponsive, it might be worth contacting LibraPay support to inquire about their module's session handling during redirects and its compatibility with other shipping extensions.

This issue highlights the complexities of integrating multiple third-party extensions in OpenCart, especially with heavily customized themes like Journal 3. Thorough debugging and understanding the checkout flow of each component are essential for a robust solution.