techedge

The import/export function is the right one. You should export what is relevant for you to transfer to the new site, since the products will be created with those properties.

Permission error, however, is a different problem. Have you opened/modified the csv? Sometimes manipulating the file (with excel/calc especially) breaks its formatting and cause import errors. Use a text editor to open it (like Notepad++ or the standard Windows notepad).

You could also quickly try to add

define( 'ALLOW_UNFILTERED_UPLOADS', true );

to wp-config.php and retry the upload. Just remember to delete the line after finishing.

Try and let us know.

The error seems just one and not “a lot”. It’s related to array_filter function called on a NULL first argument from row 463 of ShippingController.php

The reason why first argument is passed as NULL, though, it’s not clear from your post and it’s not possible to investigate more without further informations.

Please refer to this post for guidelines on how to post a thorough support request.

Ok, then you simply need to export your existing products into a .csv file. The file will contain a column labeled “image” with the media url (the first one will be the featured and the others will be the gallery).

Now you you have two paths:
– the new website is using a different domain and/or path -> import the .csv to the new site wihile keeping the old website up and running, so the new site will create products and pull images from the old site.
– the new website is using the same domain and path -> before you go online with the new website, move your old medias to a different path (e.g. wp-content/uploads/temp), then modify the .csv “image” column urls accordingly (since it’s a .csv it will be a quick find and replace matter, i.e. find wp-content/uploads/ and replace with wp-content/uploads/temp/ – remember to use the same number of slashes). At this point just import the .csv file, woocommerce will pull the right medias from the temporary folder. At the end of the process, you’ll have to just delete the /temp folder with all the medias inside (since woocommerce will recreate its standard path folders with the correct medias inside).

I hope I’ve been clear, ask for any help.

• This reply was modified 1 year, 7 months ago by techedge.

I think it’s working exactly as intended.

You can find more information here: https://developer.www.ads-software.com/themes/basics/template-hierarchy

You can try to delete all past imports and make an import again. This has fixed the issue for me in some cases.

Keep in mind that some reports don’t include taxes and gateway commissions, so your gross revenue may differ from the net revenue displayed.

Ok, now I understand. Based on the currency I see:

I assume it may be the same issue of this post.

It seems you are using WooCommerce Multilingual & Multicurrency plugin, maybe you should open a support request on https://www.ads-software.com/support/plugin/woocommerce-multilingual/ ?

• This reply was modified 1 year, 7 months ago by techedge.

Can you please post a link to the search or at least screenshot of the issue?

Sorry but I don’t get what you mean by “Google browser” (is it Chrome? Is it Google Shopping?).

Yes, it is possible but you should explain the scenario better.

Are the products you intend to show already online on the old website or they need to be created (or uploaded by a .csv file) in the new website?

There are many ways you can achieve what you need, but we need to know the starting point.

What you posted seems to be the log of the ERP, which just logs the failed call, but not the reason (tip: avoid posting key/secret pairs; you think you hid the website, but the link you posted is full of informations – website url and many personal data).

You should send a debug log for the website, since the error is happening there and we need to understand what’s causing the server error (maybe a deprecated function?).

You said you tried to revert WC version, but maybe your server PHP version was automatically upgraded and some functions got broken (this is happening lately with 7 to 8 PHP upgrade)?

Have you double checked Google Merchant Center settings?

It is probably related to the high number of variations.

WooCommerce by default will hide unavailable product variations regardless if you use Variation Swatches plugin or without (the limit seems to have been 30 in 2020, as per this article: https://superstorefinder.net/support/knowledgebase/fix-woocommerce-not-hiding-disabled-unavailable-variations/).

You could use:

function custom_woocommerce_ajax_variation_threshold( $qty, $product ) { return 1000; // Set 1000 to another number to load faster } add_filter( 'woocommerce_ajax_variation_threshold', 'custom_woocommerce_ajax_variation_threshold', 10, 2 );

in your child theme functions.php, as suggested in the article.

I tested it with 300 variations and it works as intended.

I’ve examined the plugin and I can confirm it is very light and it does almost the same than it was suggested in the stackoverflow discussion.

About feature request I think this should be the right place:
https://woocommerce.com/feature-requests/woocommerce

• This reply was modified 1 year, 7 months ago by techedge.

Oh, I see what you are trying to achieve, there is not an “out of the box” solution for that.

I suggest you also disallow account creation during checkout (third option from top on the same page Woocommerce>Settings>Account and Privacy).

The stackoverflow solution should do, but I’m sorry I cannot try it now to confirm it’s working as intended.

Keep us posted in case of need.

It depends on the theme but the standard path for not logged in is the same as logged in: Cart > Checkout. In the checkout page there is an option to login for already registered users (top square) and a form for the registration (bottom square).

See attached image:

https://1drv.ms/i/s!Aqh4xu_sLJlvhcdQUs1Tv2T_ukqnpQ

If you disallowed guest orders in Woocommerce>Settings>Account and Privacy (first option on the page), users will be forced to either login or create a new account (by filling the form directly in the checkout page).

Probably not a woocommerce issue, since it seems you are using other plugins which manipulate orders. You sure you are using the standard woocommerce form? If so, something is removing field checks on submit.