I am tab content. Click edit button to change this text. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.
What Has Been Improved
1. Performance Improvements (Faster Module)
The Problem Before:
Every time you opened the module settings page, it would scan ALL your module folders. If you have 100 modules installed, it would check every single one. It also contacted the PrestaShop marketplace website on every page load. This made the module feel slow and unresponsive.
What Changed:
The module now stores results in a temporary cache for 24 hours. It only scans for new files once per day instead of every time you open the page. Marketplace data is also cached.
Result:
The module loads 5 to 10 times faster than before.
2. Order Webhooks with Customer Email
The Problem Before:
When a customer placed an order, the webhook only sent the customer ID number. You could not get the customer's email address directly. This made it impossible to create contacts in external systems like your CRM or email marketing tools.
What Changed:
Two new webhook triggers were added: actionValidateOrder and actionValidateOrderAfter. These hooks send the complete customer information including email, first name, last name, and address.
What you can do now:
In your webhook body, you can type @customer.email and it will automatically insert the customer's email address.
Example comparison:
Before you received: { "id_customer": 123 }
Now you receive: { "customer_email": "john@example.com", "customer_firstname": "John", "customer_lastname": "Doe" }
3. Cross-Object Field Access (Dot Notation)
The Problem Before:
You could only use fields from the main object that triggered the webhook. For example, with an order webhook, you could not access customer information directly even though the order is linked to a customer.
What Changed:
You can now use dot notation to access related objects. Think of it like folders on your computer: customer is a folder, and email is a file inside it.
Examples of what you can type:
@customer.email - gets the customer's email
@customer.firstname - gets the customer's first name
@customer.lastname - gets the customer's last name
@cart.total - gets the cart total amount
@address.city - gets the delivery city
@order.reference - gets the order reference number
Available connections:
Main Object What you can access
Order customer email, customer name, delivery address, cart total
Cart customer email, products list, cart total
Product manufacturer name, category name
Address customer email, country name, state name
4. Order Status Change Tracking
The Problem Before:
You knew that an order status changed, but you did not know what it changed from. You could not tell if an order was shipped, refunded, or cancelled because you only saw the new status.
What Changed:
A new webhook called actionOrderStatusPostUpdate sends BOTH the old status and the new status. It also sends the status name and color.
Example of what you receive:
Order ID: 123
New status ID: 4
New status name: Shipped
New status color: Green
Old status ID: 2
Old status name: Processing
This is useful for:
Sending a "your order has shipped" email
Updating inventory when order is cancelled
Triggering refund processes
Syncing order status with external systems
5. Async Mode (Fire and Forget)
The Problem Before:
Every webhook was sent synchronously, meaning your store waited for a response from the external system. If that system was slow, your checkout became slow. If that system was down, the order process could fail completely.
What Changed:
A new Async Mode option is available. When enabled, the module sends webhooks without waiting for a response. Your checkout continues immediately.
How to enable:
You need to add a configuration setting in your PrestaShop database. Set OPWEBHOOKS_ASYNC_MODE to 1.
Result:
Your checkout speed will never be affected by webhooks again, even if the external system is having problems.
6. Automatic Retry for Failed Webhooks
The Problem Before:
If a webhook failed because of a network issue or because the external server was down, that data was lost forever. You had no way to recover it unless you checked logs constantly.
What Changed:
Failed webhooks are now saved in a queue and retried automatically. Each webhook gets up to 3 retry attempts. Each retry waits 5 minutes before trying again.
Example scenario:
Your CRM server goes down for maintenance at 2:00 PM. An order is placed at 2:05 PM. The webhook fails. The module tries again at 2:10 PM. Your server is back up, and the webhook succeeds. No data is lost.
Result:
Temporary network issues or short server outages will not cause data loss.
7. Better Debug Logging
What changed in the logs:
Logs now show how many milliseconds each webhook took to complete. You can see which webhooks are slow.
Response data is limited to 10,000 characters. This prevents the log table from becoming too large.
Database indexes were added so searching through logs is much faster.
Logs are automatically cleaned up after 30 days. This prevents your database from filling up.
8. Database Improvements
What changed:
New indexes were added on frequently searched columns: webhook_for, active, recorded_at, response_code
The character set was changed to utf8mb4, which supports emojis and all special characters
Table structure was optimized for faster queries
Result:
The webhook list page loads faster. Searching through logs is much quicker.
9. Security Fixes
What was improved:
Better URL validation prevents invalid URLs from being saved
Fields containing asterisks are automatically removed (these are considered sensitive)
Override file path validation prevents directory traversal attacks
Better error handling throughout the module
Quick Summary
Feature Before Version 1.4.0 Now in Version 2.0.0
Module speed Slow because of file scanning Fast with caching
Order webhooks Only customer ID number Full customer data with email
Getting customer email Not possible Yes using @customer.email
Accessing related data Not possible Yes using dot notation like @customer.email
Status change tracking Only new status Old status AND new status
Failed webhooks Lost forever Retry up to 3 times
Checkout speed Slowed by webhook responses Async mode keeps checkout fast
