adrianwackernah

Thanks Kris, it is now solved.

Hi @xue28 thanks for the answer but there is any help in there.

I have a privacy policy but need afterwards help in finding who is involved in this plugin. Who gets and saves data about transactions with WooCommerce Payments and why they collect that data. I have to inform my customers in privacy policy before the make a purchase.

If I went over to my wordpress.com account I may find few privacy policies about what wordpress.com collect from me and my customers if I use WooCommerce Payments on my site, but the infos are not for using them on / in my own privacy policy.

So please help in this case and with more details please.

I see on another site too that cart page has same issue. I have set width of search bar to 200px without submit button (only icon) but that is overwritten on pages my account, cart and checkout.

Hi @christian1983
Well, I tried with 1.0.2.

Beside after checking Woocommerce Status page, I saw a table created by plugin which did not respect table-prefix? Thats a bug too? I have set database tables prefix to something other than wp_xxx.

In the meantime I found under settings a checkmark for removing all settings from plugin and I did so: saved that checkmark, deactivated plugin and deleted plugin. But table “wp_pinterest_xxx” wha still there. Now I removed that table from database manual but did not gave plugin another try.

• This reply was modified 2 years, 10 months ago by adrianwackernah.

Sorry @danielinhou

in the meantime the product on sale had reached the date to which the sale ends.

The link is still correct and I have set another product for sale. Please take a look at given link again.

I checked behavior with Childthemes “Stationary” and “Bistro”.

Hi @danielinhou

on your page I can not see a sale badge.

Well, I created a page where I show a on sale product side by side as block and shortcode. They look different.

Hi there, it seems it was a caching problem. Sorry and Thanks.

Hi @kosiew
sorry no. It was a chat and I did not save it.

Well you are right in parts. I talked to support at woocommerce.com too and they found that at import the title and description field had content in them which broke import. This should not happen, because imported file was exported product file from another site and was not edited in any way. So, it seems that some characters are not allowed at importer within admin of WC. But file itself and its content were OK as I imported from file uploaded before by ftp to server.

Its a bit of mismatch.

Hi @kosiew
that’s not the case. I did upload csv-file by ftp and gave WC product importer the path and filename. But this way is not as it should.

I wrote this bug because few weeks before I could upload and so on import csv files.

Thank you very much. The error is gone. Good job and thanks for best plugin.

Of course @grola on page site health this shows up as critical:

Eine PHP-Sitzung wurde durch einen session_start()-Funktionsaufruf erzeugt. Dies beeintr?chtigt die REST-API- und Loopback-Anfragen. Die Sitzung sollte von session_write_close() geschlossen werden, bevor irgendwelche HTTP-Anfragen erfolgen.

Site language is german de_DE

• This reply was modified 4 years, 3 months ago by adrianwackernah.

Hi @corsonr
thanks for your response, but it is not at all as you told. I had for testing a staging website with WC 3.8.0 installed and Germanized. I deactivated Germanized and checked which tax sections I have and saw that section no tax was missing.

Than I activated Germanized again, did a upgrade on Germanized because I had a older version installed and checked tax sections again. No new tax section was added.

Than I updated WC to 4.0.1 and checked again: Now no tax (or zero tax) was added by WC at update. If I had renamed tax section of zero tax, than I would have two sections beside with zero tax, right?

So, WC has control over which tax sections should be there and install them if WC thinks there is something missing. Please check.

Ah, I remember, it was a php related issue. If I would switch back to PHP 7.2 or 7.1 the warning is gone. But that’s contraproductive isn’t it?