Hi @zakblack,
Thanks for reaching out.
I understand you’re facing an issue as the one described here.
I tried replicating the issue on a local host, but was unable to replicate the issue. Are you able to try the installation on a test host like this one and let us know if you still face a similar issue?
I have tested a new installation I was also not able to reproduce locally
I forgot to mention I’m testing from Algeria country, currency DZD
my guess is that there’s a restriction limit somewhere from hosting
I tried reinstalling the plugin but same problem. please check the logs provided I need to know what they’re trying to access
Hi @zakblack,
I have tested a new installation I was also not able to reproduce locally
Thanks for confirming this for us.
I forgot to mention I’m testing from Algeria country, currency DZD
I can confirm that we do not limit installations based on currencies or Country of origin.
my guess is that there’s a restriction limit somewhere from hosting
It is possible the issue is with your host, could you try reaching out to their support team and share the logs with them as well?
please check the logs provided I need to know what they’re trying to access
Based on the shared logs, there’s a TypeError occurring within the WooCommerce plugin files on your website. This error, specifically ‘Cannot read properties of undefined (reading ‘is_store_country_set’)’, typically happens when the script tries to read a property or call a method on an undefined object.
Are you able to confirm the WooCommerce and WordPress version you’re using in your installation?
Hi,
I’m using WordPress version 6.6.1 and Woocommerce 9.1.4
I have contacted the ultahost hosting support as well I’m waiting for their feedback I will get back to you shortly.
Thanks again for getting back to us @zakblack,
While you await on feedback from your host, could you try installing a previous version of WooCommerce to see if you’ll be able to install WooCommerce without encountering the error. You can download a previous version here.
Let us know how it goes.
@ckadenge Update :
- I have replicated/migrated my entire website (including DB) to localwp.
I can confirm I was not able to reproduce issue. Therefore we can assume the issue lies somewhere in hosting permission. - I have also tested with previous version 9.1.3 on my live server I can confirm it’s the same problem.
Note : Tested with PHP v8.3 and v8.2
Hi @zakblack,
Thank you for taking your time to make the different tests.
In this case, I recommend reaching out to your host with the findings and ask for assistance from their end.
Thank you for your patience and understanding.
It would be helpful to know what kind of permission or function the plugin is requesting
for example is there some module php that needs to be enabled …etc
Hi @zakblack
I tried reproducing the error using a new WordPress and WooCommerce installation on my Hostinger hosting account but was unsuccessful.
However, as mentioned on the GitHub issues, can you please check whether the API end is being blocked due to “mixed content” i.e. HTTPS? Can you install SSL and check whether the issue persists?
In the meantime, since you didn’t encounter the same issue on a local installation, it’s possible that this could be related to your hosting environment. I recommend reaching out to your hosting provider and sharing these logs with them. They may be able to provide more insight into any potential restrictions or configuration issues that could be causing this problem.
Looking forward to hearing from you!
Solved. The issue was because of .htaccess file permission
reseting it solved it.
Hello @zakblack,
Glad to know that the issue has been resolved now and thank you for sharing the solution and contributing to the WooCommerce Community.
I will mark this thread as resolved. Should you have further inquiries, kindly create a new topic here.
Meanwhile, if it isn’t too much to ask for – would you mind leaving us a review here? It only takes a couple of minutes but helps us tremendously. It would mean so much to us and would go a long way.
Thanks!
