Peter Fabian
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] parse errorIf this is a new hosting account, then I would encourage you to check with your hosting company. You can tell them that you are seeing syntax error messages in the logs for return type declarations in PHP and they should be able to check if everything is in order. We test our code on PHP 7.0 – 8.0 on different environments from Windows to Linux to MacOS and haven’t seen this error yet, so it seems unlikely that it would be a problem with WooCommerce.
Another option would be that the code was corrupted somehow (e.g. incomplete installation), but since your site works now, I think the syntax error can’t be happening anymore, otherwise, you would just see an error message/blank screen.
If you find out more, please let us know. Thanks!
- This reply was modified 1 year, 7 months ago by Peter Fabian.
Forum: Plugins
In reply to: [WooCommerce] parse errorHi @dideto
I’m just guessing here, but maybe this error comes from earlier when you ran a different version of PHP (PHP 5, most likely).
Since PHP 7.0 (which was released 5 years ago), the language supports declaring return types for functions, which is what we’re doing on that line in the PHP script.
My assumption, since you could send us your System Status Report is that currently, WooCommerce runs and works for you, is that correct? Because if you faced a syntax error in the main WooCommerce file and WC was active, you wouldn’t be able to visit any WordPress page on your website.
Therefore, I think you can ignore this error, unless it appears again.
Hope it helps!
- This reply was modified 1 year, 7 months ago by Peter Fabian.
Forum: Reviews
In reply to: [WooCommerce] i can not install woocommetrceHi @nader2020 , sorry to hear you’re having problems. Were you able to identify any errors in the logs/on the screen that might help us fix the issue? Thanks!
Forum: Reviews
In reply to: [WooCommerce] They bait and switch, ruin businessHi @aksutah, what features are you missing from WC? I don’t remember us removing any recently, so would be happy to help if possible. Thanks!
Forum: Reviews
In reply to: [WooCommerce] Update affecting display of other types of imagesHi @bizm8tech , thanks for your review. Have you had a chance to try and [troubleshoot to see which plugin WC might be conflicting with](https://docs.woocommerce.com/document/how-to-test-for-conflicts/)? It would help us to know which ones we should test with. Thanks!
Forum: Reviews
In reply to: [WooCommerce] 4.4 – Website CrashedApologies for the problems! The error mentioned by @abuguda should be fixed in WC 4.4.1 we released on August 19th.
Forum: Reviews
In reply to: [WooCommerce] Does Not Work – Works NowHi @Pyxis2025, please reach out to our support folks who can help you with your problems: https://woocommerce.com/contact-us/
Forum: Reviews
In reply to: [WooCommerce] Completely crashed my website…Sorry to hear that, can you please be more specific so that we can undo the crashing in the next release?
Forum: Plugins
In reply to: [WooCommerce] Fatal error update 4.4 – Jquery!!!Hi, we’ll be releasing 4.4.1 shortly that adds some additional safeguards to this code, so this should be resolved then.
Forum: Plugins
In reply to: [WooCommerce] wp_2_wc_reserved_stock’ doesn’t existHi @nick7766
WooCommerce itself should work without the table fine, but if you want to take advantage of the new functionality that improves stock reservation, you can check with your hosting if you have permissions to create new database tables and either create the table for you.
If you have the permissions, you should be able to run the database fixing code by going to WooCommerce > Status > Tools > Verify database–this is a new tool we’ve added in WooCommerce 4.3.
Please let us know if you have any problems fixing it, thanks!
- This reply was modified 1 year, 11 months ago by Peter Fabian.
Forum: Plugins
In reply to: [WooCommerce] Wrong JS Translations loadingHi @krut1
Thanks for reporting the problem. We’re using a script to translate the text domain from woocommerce-admin to woocommerce during our build process, so you should not see any “woocommerce-admin” strings unless we have a bug somewhere. Can you please share what version of WooCommerce you are running, as I can’t see this string in WC 4.2 in the file you mentioned (packages/woocommerce-admin/dist/app/index.js)
- This reply was modified 2 years ago by Peter Fabian.
Forum: Plugins
In reply to: [WooCommerce] “WooCommerce database update done” not fixed in 4.2.0Hi,
apologies for the problems. We’ve done some changes in 4.1.1 to get rid of the problems, but it seems like there are more edge cases.
You should be able to deactivate the notice by executing the following SQL query:
UPDATE wp_wc_admin_notes SET status='actioned' WHERE name='wc-update-db-reminder';If that does not help, it might be that the request to retrieve the notices gets cached and it returns the same notice even though you already dismissed it.
If you know how to work with the Network tab in Dev tools of your browser, you can check the response of the request itself and how the database of your store looks and see if the notice is set to
actioned(e.g. by runningSELECT status FROM wp_wc_admin_notes WHERE name='wc-update-db-reminder') or if there is something else at play here.Forum: Reviews
In reply to: [WooCommerce] I love WooCommerce but…Hi, hurri500,
Sorry to hear you don’t like the new dashboard. If you prefer to disable it, you can do it by using a filter
add_filter( 'woocommerce_admin_disabled', '__return_true' );or there are small plugins that do it for you as well e.g. https://wordpress.org/plugins/disable-dashboard-for-woocommerce/.
Forum: Plugins
In reply to: [WooCommerce] Fatal Error on last version (4.0)Thanks for reporting on your progress and apologies for the late reply, we’ve been busy preparing the fixes for WooCommerce 4.0.1.
Forum: Plugins
In reply to: [WooCommerce] Coupon failed on checkout after upgrading to WC 4.0.0Hi,
Apologies for the trouble. We think this might happen for some coupons that are missing usage count information. We’re going to release a fix in 4.0.1 for this soon. Hope it helps.