sunrosea

Ah ok I understand. Makes sense. ??
Would be a great feature as I am custom coding a few things for my site and would need that.
Thanks.

Scratch that. I was actually using the hook “woocommerce_checkout_fields” which is why it wasn’t reflected back into the account page.

I have figured out that it works as I intended if I change that hook to “woocommerce_billing_fields” and then changing unset($fields['billing']['billing_company']); to unset($fields['billing_company']);.

All good, marking this as solved!

Ah I see, thank you for taking your time explaining this.
It’s working now. ??

I’m not the plugin author but I thought I might be able to help.

That tag goes into newsletter emails only. You can tell by the fact it has curly brackets: {} instead of shortcode brackets: []. You can’t place it on a page as it’s not a shortcode. I do not think there’s a unsubscribe link you can send your subscribers manually.

Instead, you’d want to include an unsubscribe link or profile link into the newsletter emails so they can unsubscribe from there.

If you have a unsubscribe link in the newsletter email that the user already have recieved, I suggest you tell them to click on it to unsubscribe. If that doesn’t work then manually deleting them might be necessary.

• This reply was modified 5 years, 8 months ago by sunrosea.

Great!
Thanks for letting me know.

Cheers.

Awesome. Thanks for letting me know!
Would appreciate if you could stop by and leave another response once you have it fixed!

I’m experiencing the same thing. I looked on github and found that it apparently is a known problem. Can be read about here for anyone else who is wondering: https://github.com/woocommerce/woocommerce/pull/23739

Anyone have any inputs/updates on this?

Apparently, it’s not the gateways instance that messes it up now when I’m trying it. But something else still is. When you choose an order in the back-end and choose to send an invoice through the order actions, it still breaks the page and instead loads the email template on the page and I have to press the back button in the browser to get back to the order page.

I have the latest Woocommerce v.3.6.1 and latest WordPress v.5.1.1 installed.

Thanks.

• This reply was modified 5 years, 10 months ago by sunrosea.

Hello!

I have seen that code and tried it. Peculiar how it works for you but not for me.
When I use that code, and go to an order and select Order Actions -> Email invoice / order details to customer, it breaks the page and immediately loads the email template in the browser window instead of actually doing the action.

The specific code that seems to break it is this part:
$gateways = WC_Payment_Gateways::instance(); // gateway instance

If I remove that, the code obviously doesn’t work, but then it doesn’t break the order page.

Can you try using the code you provided me, and then go through the same steps by going to an order and select the “invoice customer” order actions option and see if it breaks your page too?

Thank you for your assistance!

• This reply was modified 5 years, 10 months ago by sunrosea.
• This reply was modified 5 years, 10 months ago by sunrosea.

Hello again!

How is it going with this bug?
I’m still experiencing problems with it. I installed the latest version 1.9.2.

Thanks. ??

Also, where can I find information regarding the retention time of the data collected for the Askimet service?

Hi!
I de-activated a bunch of plugins and re-activated them a few at a time to see if any of them was the culprit, but seems like just de-activating them fixed the problem alone so it seems to be solved.

In case it could still be useful information, it happened with JetPack v. 6.9 with WordPress 5.0.3.

Thanks.

Ok, so I decided to de-activate and activate it again. It had me prompted to activate Jetpack (which I’ve already done before I updated), and after I did that the links in the sidebar came back (Dashboard, stats etc.) but they all load blank as before (except for site stats that just keeps loading).

I decided to go with hooks instead, so I’m marking this as solved.

I followed your suggestion to test it in another browser (Chrome) and was able to re-create the problem.

Thanks for your assistance. ??

• This reply was modified 6 years, 4 months ago by sunrosea.