myworksdavid
Forum Replies Created
-
Hi! As a reminder from your last thread, we don’t provide official support here, as we handle support on our support site so our team can best review your account / connection / settings with us based on your site.
Based on your screenshot, it seems you haven’t yet mapped your WooCommerce and QuickBooks products together in MyWorks Sync > Map > Products?
As a reminder, the best and fastest way for our support team to give you a hand with any ongoing questions/issues is by emailing our support team at support@myworks.software or on our Help Center at https://support.myworks.software. We are available there 24/7 via email and do an excellent job at responding quickly / helping resolve any questions.
Hi there, glad to help! As a reminder, the best and fastest way for our support team to give you a hand with any ongoing questions/issues is by emailing our support team at support@myworks.software or on our Help Center at https://support.myworks.software. They are available 24/7 via email and do an excellent job at responding quickly / helping resolve any questions, and they’d be happy to help you!
From what you’re describing, it does indeed seem like they may have the the QuickBooks product SKU mapped to the WooCommerce product name – in MyWorks Sync > Settings > Product in our sync on their store? Our support team can certainly help dig in further!
Thanks for sharing this with us! Our team is working on this, and we’ll have this resolved shortly!
As a reminder, we officially handle support at https://support.myworks.software; where you can also get a pre-release version of our plugin with the above solved, if helpful!
Thanks for reaching out! As a reminder, we provide support primarily at support@myworks.software – or https://support.myworks.software
This error can appear when a page request runs while WooCommerce itself isn’t fully loaded — most commonly right in the middle of a WooCommerce update (while WordPress is swapping the plugin files), or if the update was interrupted and WooCommerce didn’t come back up cleanly afterward. In that state, WooCommerce’s
WC_ABSPATHconstant doesn’t exist yet, and our plugin happens to be the first thing to reference it — which is why the error message points to our file even though the sync itself is working fine.To get back up and running:
- On the Plugins page, confirm WooCommerce is active and shows version 10.9.3. If the update was interrupted, re-install WooCommerce from the Plugins page (your data/settings are safe — they live in the database).
- Re-activate MyWorks Sync. Once WooCommerce is loading normally, this error won’t recur.
We’re also adding extra safeguards in an upcoming release so that even during a mid-update window like this, the plugin will quietly stand down instead of showing an error.