rikofert

Hi,

I guess that when a new product is added to woocommerce, it has all meta keys created in the database, “_regular_price”, “_price” – “_sale_price”.

Everything should work fine until “_sale_price” is set and then removed, as far as I see in fact woocommerce decides to completely remove the field instead of setting it to NULL.

I think that this behaviour is not what users exactly expect because woocommerce, doing like this, is not restoring the initial state of the db for the product.

Do you think we can open a bug for this?

Hi,

it finally works starting from version 2.8.7.

Thanks.

Hi zorem,

very sorry for that, but I have been just notified by TNT account manager that in order to track Italy shipment they recommend using the following URL:

https://www.tnt.it/tracking/getTrack.html?wt=1&consigNos=%number%

Apologies for the wrong indication.
Thanks for support.

Hi zorem,

thanks for support, I saw your update and the new URL is working well, but feel free to correct my typo:

https://www.tnt.com/express/it_it/site/shipping-tools/tracking.html?searchType=con&cons==%number% (double ‘=’)

very sorry for that.
Regards and thanks again.

Hi,

any feedback? From my side there is no way to let your plugin process emails in language user used to fill in his order.

Thanks.

Hi,

yes, you are right, I can edit (but not create) language strings with WPML string translation, based on “.mo” files shipped with your plugin, nevertheless all the emails sent from woocommerce are not translated by WPML according to customers’ languages (always EN), and even if I try to add a custom ‘Subject’ to email, using your customizer, I never succeed in finding custom strings in admin page; if I manually rescan woocommerce and your plugin, nothing changes.

Have you ever tested your plugin with WPML in sending email?

Thanks for support.

• This reply was modified 4 years, 11 months ago by rikofert.
• This reply was modified 4 years, 11 months ago by rikofert.

Hi Oliver,

thanks for support, resetting all related string translations fixed the issue.

Best Regards.

Hi Oliver,

any findings about this issue? Did your developers succeed in replicating the duplication of woocommerce “Processing order” email ?

Thanks.

You are right, I am using the Italian Add-On. It is my fault, sorry.

Hi,

I enabled ‘Reset invoice number yearly option’ (via WooCommerce > PDF Invoices > Documents > Invoice), and ‘Reset receipt number yearly option’ (via WooCommerce > PDF Invoices > Documents > Receipt), but in my case it has worked just for invoices and not for receipts.

Regards.

Hi Oliver,

I can confirm that I found out the following solution to fix this issue; removing line :1357 from file ‘angelleye-includes/angelleye-utility.php’

do_action('woocommerce_order_status_pending_to_processing', $order_id);

just one (1) “Processing order” email notification is triggered to customer when a “DoCapture” Payment Action is made on “OnHold” state order.

I did some tests and everything seems to be working fine, even if the order is already in a “Processing” state.

I think you should review the code.
Regards.

Please talk to the plugin support which is putting the order at hold and see if they make any adjustments in the process of putting order at hold and that will sort this.

I think I did not get the point. It is actually this plugin (PayPal for WooCommerce By Angell EYE) that is putting orders in an OnHold State.

• This reply was modified 6 years ago by rikofert.

Hi,

from my side I still need to replace line #156 in file classes/wc-gateway-paypal-express-angelleye.php from:

$this->checkout_button_label = $this->get_option('checkout_button_label', __(Proceed to PayPal, 'paypal-for-woocommerce'));

to

$this->checkout_button_label = __($this->get_option('checkout_button_label'), 'paypal-for-woocommerce');

If I do not, even with last update (1.5.3), WPML is not going to translate checkout button label .

Hi Oliver,

yes, you right! Once the order is placed by customer , plugin puts it on hold if paypal authorizes transaction.

Thanks for support.

Hi,

do you have any update, warnings are still there even with the last plugin update: 3.1.6.

Regards.

• This reply was modified 6 years, 5 months ago by rikofert.