Introduction
When checking the logs of a Woosa plugin, you might notice entries labeled as "WooCommerce" alongside the plugin's specific data. We intentionally include these logs because our plugins act as a bridge between WooCommerce and external platforms. To understand why a synchronization might be failing, we need a complete overview of what is happening within your entire webshop environment.
Problem / FAQ
"Why am I seeing errors that don't seem related to the plugin?"
"Where can I find the logs specifically generated by the Woosa plugin?"
"Does the plugin cause these WooCommerce errors?" (Usually not; the plugin simply reports what WooCommerce is experiencing).
Troubleshooting
To effectively solve synchronization or technical issues, follow these steps to access the correct information:
View logs within the plugin: You can view the logs generated specifically by our plugin directly in the settings. Go to the Plugin Settings (e.g., Bol.com or VidaXL plugin) and click on the Logs tab.
Identify the files: In the list of log files, you can recognize our logs by the standard prefix:
woosa-(plugin-name). Examples includewoosa-vidaxlorwoosa-bol-com.General WooCommerce logs: General system errors can be found under WooCommerce > Status > Logs. If a log entry starts with "WooCommerce", it often points to an issue with server configuration, the database, or another plugin.
Check for Server Issues: Many errors in the logs are server-related (such as memory limits or timeouts). In these cases, we recommend contacting your hosting provider first.
Share logs with Support: When contacting Woosa support, please copy the relevant lines or provide a screenshot. This helps us quickly determine whether the root cause lies within the plugin or the server environment.
Can’t figure it out? You can always send a message to the support team via the chat bubble at the bottom right 🎈 Support to the rescue 👨💻 👩💻