The mobile app “woo!” which allows you to access to woocommerce data (orders, clients and so on), was running slowly.
So my client decided to reinstall the app and reconfigure it, but during the configuration stage, it was not possible to login.
Why? Seems that it has something to do with translatepress and webhooks.
In fact I was able to:
1. reproduce the client issue by my own
2. use the app normally once I have deactivated translatepress.
Let me know if you need other details.
From the start, the team at MiniOrange took the time to understand our requirements thoroughly and delivered exactly what we needed. Despite our extremely tight deadlines, they remained highly responsive and ensured that we got the best results without compromising on quality.
Our goal was to have a real-time booking engine that seamlessly syncs with our PMS, keeping room availability, pricing, and reservations updated across multiple platforms. They successfully developed a system that ensures prices update dynamically, availability remains accurate, and any reservations made on our website are instantly reflected in our PMS with all the necessary details. They also ensured that bookings are only confirmed once payment is verified with our payment gateway partner, aligning perfectly with our operational requirements.
Despite facing limitations due to our WordPress theme, MiniOrange went above and beyond to overcome those challenges, delivering a smooth and efficient solution that exceeded our expectations. Their work on the backend is exceptionally clean, optimized, and reliable, ensuring long-term stability and ease of management.
A special thanks to Vidushi Gupta, Rohit Sharma, Sharshdeep Saluja, and the entire MiniOrange team for their dedication, expertise, and professionalism. Their services are also cost-effective, making them a great choice for businesses in the hospitality industry.
If you’re looking for a team that can handle complex integrations, deliver tailored solutions, and work under pressure while maintaining high standards, MiniOrange is the perfect partner. Highly recommended!
]]>The following report is from one of the clients with this issue:
System Status Report
### WordPress Environment ###
WordPress address (URL): [Redacted]
Site address (URL): [Redacted]
WC Version: 9.5.2
Legacy REST API Package Version: Il plugin API REST legacy non è installato in questo sito.
Action Scheduler Version: ✔ 3.8.2
Log Directory Writable: ✔
WP Version: 6.7.1
WP Multisite: –
WP Memory Limit: 1 GB
WP Debug Mode: –
WP Cron: ✔
Language: it_IT
External object cache: –
### Server Environment ###
Server Info: nginx/1.22.1
PHP Version: 8.1.22
PHP Post Max Size: 256 MB
PHP Time Limit: 60
PHP Max Input Vars: 10000
cURL Version: 8.5.0
OpenSSL/1.1.1w
SUHOSIN Installed: –
MySQL Version: 8.0.31-google
Max Upload Size: 256 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔
### Database ###
[REDACTED]
### Post Type Counts ###
attachment: 1653
elementor_library: 17
elementor_snippet: 9
mailpoet_page: 2
nav_menu_item: 17
page: 16
post: 2
product: 458
product_variation: 1366
revision: 312
shop_coupon: 30
shop_order_placehold: 106
wafs: 1
wp_font_face: 33
wp_font_family: 12
wp_global_styles: 1
wp_navigation: 1
wp_template: 1
wp_template_part: 2
### Security ###
Secure connection (HTTPS): ✔
Hide errors from visitors: ✔
### Active Plugins (28) ###
Activity Log: di Activity Log Team – 2.11.2
Elementor Pro: di Elementor.com – 3.26.3
Elementor: di Elementor.com – 3.26.5
Essential Addons for Elementor: di WPDeveloper – 6.1.0
Facebook for WooCommerce: di Facebook – 3.3.1
Google for WooCommerce: di WooCommerce – 2.9.4
Site Kit by Google: di Google – 1.144.0
iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more: di iubenda – 3.11.3
Jetpack: di Automattic – 14.2.1
Klaviyo: di Klaviyo
Inc. – 3.4.2
WooCommerce Load More Products: di BeRocket – 1.2.2
MailPoet: di MailPoet – 5.6.1
Meta pixel per WordPress: di Facebook – 4.0.1
Pinterest for WooCommerce: di WooCommerce – 1.4.14
PW WooCommerce Gift Cards: di Pimwick
LLC – 2.10
Temporary Login: di Elementor.com – 1.3.0
TikTok: di TikTok – 1.3.0
Variation Swatches for WooCommerce: di CartFlows – 1.0.12
Discount Rules Core: di Flycart – 2.6.6
WooCommerce Advanced Free Shipping: di Jeroen Sormani – 1.1.7
Pixel Manager for WooCommerce: di SweetCode – 1.46.0
WooPayments: di WooCommerce – 8.7.1 (aggiornamento alla versione 8.8.0 disponibile)
WooCommerce PayPal Payments: di WooCommerce – 2.9.6
WooCommerce: di Automattic – 9.5.2
Yoast SEO: di Team Yoast – 24.2
Widgets for Google Reviews: di Trustindex.io – 12.5
WP Rollback: di WP Rollback – 2.0.7
Social Chat: di QuadLayers – 7.5.0
### Inactive Plugins (1) ###
Duplicator Pro: di Duplicator – 4.5.14.2
### Must Use Plugins (1) ###
Elementor Safe Mode: di Elementor.com – 1.0.0
### Settings ###
Legacy API Enabled: –
Force SSL: –
Currency: EUR (€)
Currency Position: right_space
Thousand Separator: .
Decimal Separator: ,
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
pw gift card (pw-gift-card)
simple (simple)
variable (variable)
Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)
Connected to WooCommerce.com: –
Enforce Approved Product Download Directories: ✔
HPOS feature enabled: ✔
Order datastore: Automattic\WooCommerce\Internal\DataStores\Orders\OrdersTableDataStore
HPOS data sync enabled: –
### Logging ###
Enabled: ✔
Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2
Retention period: 30 giorni
Level threshold: –
Log directory size: 11 MB
### WC Pages ###
Shop base: #125 - /shop/
Carrello: ❌ La pagina non contiene lo shortcode [woocommerce_cart] o il blocco woocommerce/cart.
Pagamento: ❌ La pagina non contiene lo shortcode [woocommerce_checkout] o il blocco woocommerce/checkout.
Il mio account: ❌ La pagina non contiene lo shortcode [woocommerce_my_account].
Termini e condizioni: #90 - /terms-privacy/
### Theme ###
Name: Hello Elementor Customized
Version: (aggiornamento alla versione 0 disponibile)
Author URL:
Child Theme: ✔
Parent Theme Name: Hello Elementor
Parent Theme Version: 3.2.1
Parent Theme Author URL: https://elementor.com/?utm_source=wp-themes&utm_campaign=author-uri&utm_medium=wp-dash
Theme type: Tema classico
WooCommerce Support: ✔
### Templates ###
Overrides: –
### WooPayments ###
Version: 8.7.1
Connected to WPCOM: Sì
WPCOM Blog ID: 199517205
Account ID: acct_1JsNkm2EAKczHYFr
Payment Gateway: Abilitato
Test Mode: Disabilitato
Enabled APMs: card,sepa_debit,klarna
WooPay: Non idoneo
Apple Pay / Google Pay: Abilitato (product,cart,checkout)
Fraud Protection Level: basic
Multi-currency: Abilitato
Auth and Capture: Disabilitato
Documents: Abilitato
Logging: Disabilitato
### MailPoet ###
Sending Method: MailPoet
Send all site's emails with: Metodo di invio attuale
Task Scheduler method: Action Scheduler
Cron ping URL: https://exxstore.it?mailpoet_router&endpoint=cron_daemon&action=ping
### WooCommerce PayPal Payments ###
Onboarded: ✔
Shop country code: IT
WooCommerce currency supported: ✔
Advanced Card Processing available in country: ✔
Pay Later messaging available in country: ✔
Webhook status: ✔
PayPal Vault enabled: –
ACDC Vault enabled: –
Logging enabled: –
Reference Transactions: –
Used PayPal Checkout plugin: –
Subscriptions Mode: Disabled
PayPal Shipping Callback: ✔
Apple Pay: –
Google Pay: –
Fastlane: –
### Admin ###
Enabled Features: activity-panels
analytics
product-block-editor
coupons
core-profiler
customize-store
customer-effort-score-tracks
import-products-task
experimental-fashion-sample-products
shipping-smart-defaults
shipping-setting-tour
homescreen
marketing
mobile-app-banner
onboarding
onboarding-tasks
pattern-toolkit-full-composability
product-custom-fields
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
printful
shipping-label-banner
subscriptions
store-alerts
transient-notices
woo-mobile-welcome
wc-pay-promotion
wc-pay-welcome-page
launch-your-store
Disabled Features: product-data-views
experimental-blocks
coming-soon-newsletter-template
minified-js
product-pre-publish-modal
settings
async-product-editor-category-field
product-editor-template-system
blueprint
reactify-classic-payments-settings
use-wp-horizon
add-to-cart-with-options-stepper-layout
Daily Cron: ✔ Next scheduled: 2025-01-18 09:06:48 +01:00
Options: ✔
Notes: 95
Onboarding: completed
### Action Scheduler ###
Operazione annullata: 7
Oldest: 2024-12-19 12:51:30 +0100
Newest: 2025-01-16 11:32:44 +0100
Completato: 25.698
Oldest: 2024-12-17 11:30:26 +0100
Newest: 2025-01-17 11:28:17 +0100
Operazione non riuscita: 1.407
Oldest: 2024-06-06 11:49:47 +0200
Newest: 2024-10-05 09:22:39 +0200
In attesa: 9
Oldest: 2025-01-17 11:30:17 +0100
Newest: 2025-01-17 19:21:36 +0100
### Status report information ###
Generated at: 2025-01-17 11:30:06 +01:00
Thanks,
Paolo.
]]>However, when I try to add the collected data from the webhook, I only have the following options in the dropdown:
The incoming webhook data is not being processed correctly in the recipe. I cannot change the structure of the webhook data, but I need to manipulate or map it properly in the recipe to ensure the desired actions are performed.
Anyone experiencing this problem?
]]>x-wc-webhook-signature
header it doesn’t match.
Here is part of the code I’m using:
app.post('/webhook', express.raw({ type: 'application/json' }), (request, response) => {
const isWebhookValid = isWoocommerceWebhookValidated(request)
if (isWebhookValid) {
console.log('Webhook signature is valid')
response.status(200).send('Webhook signature is valid')
} else {
console.log('Webhook signature is invalid')
response.status(401).send('Webhook signature is invalid')
}
})
Here is the logic behind the isWoocommerceWebhookValidated
export function isWoocommerceWebhookValidated(request: Request): boolean {
const WC_WEBHOOK_SIGNATURE_HEADER = 'x-wc-webhook-signature'
const signature = request.headers[WC_WEBHOOK_SIGNATURE_HEADER] ?? ''
const secret = process.env.WOOCOMMERCE_WEBHOOK_SECRET ?? ''
if (!signature || !secret) {
console.log('Missing signature or secret')
return false
}
const payload = request.body
const hash = crypto.createHmac('sha256', secret).update(payload, 'utf8').digest('base64')
return hash === signature
}
These are the hash and signature result logged in console:
signature: 'QtVYdnEQDf0+lcxkjGgSXxtuAqkM/3L6GYvhgjY+DEE='
hash: 'LUsjH1Gx2DaSLHIg5NkoTx03mUsHdL7+RlPiIYF6I0c='
I’m 100% sure that both secrets in Woocommerce and in my environment variable matches. Any ideas on how to solve the issue?
I have an issue with WordPress WooCommerce and Stripe pluing
I have followed other threads and I deleted the webhook in my Stripe and reconnected my WooCommerce site to the Stripe account using the new automatic system.
I have ‘Payment: Enabled Payout: Enabled Webhook: Enabled’ but a warning saying:
Warning: The most recent live webhook, received at 2024-09-14 11:03:38 UTC, could not be processed. Reason: The webhook was not signed with the expected signing secret. (The last live webhook to process successfully was timestamped 2024-09-11 17:20:02 UTC.)
Is there any fix for this?
(WooCommerce 9.3.1 with WooCommerce Stripe Gateway 8.6.1.)
I get the error “Looks like the webhook cannot be received. Check that your website is accessible from the internet.” when using the Webhook simulation.
I’ve turned on Logs as well.
Please advise. Thank you.
]]>I am experiencing an issue with integrating data received from a webhook into a WordPress post. Specifically, the text contains double backslashes, such as \\[\\frac{\\partial f}{\\partial x}\\]
, but these backslashes are being treated as regular slashes. As a result, in the WordPress editor, the output appears as rac{artial f}{artial x}
instead of the correct format \[\frac{\partial f}{\partial x}\]
.
I have reviewed the UA logs and confirmed that the data is received correctly (with double backslashes), and the content appears correctly published (with single backslashes). However, when viewing it in the WordPress editor, the backslashes are removed, along with the first letter following each backslash.
Could you please advise if there is a way to resolve this issue? I would greatly appreciate any guidance or assistance you can provide.
Thank you very much for your help!
]]>