Bartek

Hi @oxomgt!

We have looked into this issue. Our findings are – it can only occur in admin UI, when editing automation. Nevertheless, it has to be improved!

Could you describe when do you experience this issue? Are there any steps to reproduce?

Best regards!

Hi @attila73!

Just wanted to mention that we hear you, and along with some patches, we introduced your suggestions back to ShopMagic v3!

Take a look at a changelog: https://ww.wp.xz.cn/plugins/shopmagic-for-woocommerce/#developers

Hello!

Despite the fact, the issue occurs within one of ShopMagic’s hook, it’s solely related to WooCommerce PayPal Payments plugin.

Feel free to open an issue on their support forum with stack trace you mention @frixor.
To add more details to it, WC PayPal uses hook woocommerce_email_before_order_table (which isn’t modified or reused in ShopMagic itself) with strong typing on last (4th) parameter as WC_Email class. It results in TypeError as parameters passed to this hook are declared in WC_Emails::order_details method, and you can see, it expects the last argument to be string.
Related line of code: https://plugins.trac.ww.wp.xz.cn/browser/woocommerce/trunk/includes/class-wc-emails.php#L403

Hope it will help with resolving their issue!

Hello @ivanjacek!

Let me rephrase your topic, to make sure, I understood it correctly.

You’ve created custom order status in your website, assigned to your orders. From now on you’d like to use this status in ShopMagic automations. The issue, you encounter is the fact, that you’d like to have it available in event triggers, like from select list.

If that’s what you’d like to achieve, it’s easy to do, yet not direct in it’s solution. You can select event Order Status Changed. There you can configure, which status transition suits your business. If you just want to target any order having your custom status, you can select transition from any order status to your custom order status.

Let me know, if this is clear enough to help you configure ShopMagic properly.

Best regards,
Bartek

Hello @jaho92!

What you show, looks troubling as there’s no issue indicator, yet the problem exists. Did you check our troubleshooting guide on our support website? Maybe there you would find better answers for your questions?

Otherwise, check any possible fatal log errors and WooCommerce > Status > Scheduled Actions page. In scheduled actions you can look for those with name ‘shopmagic’ to see if any produced an error.

Best regards,
Bartek

Hello @gilles24!

We’ve examined this issue and have come to conclusion that may surprise you. The fact, that user is registered to all opt-out lists is not a bug – it’s been designed this way, and now I’ll try to explain to you, why we’ve decided this way.

ShopMagic offers two types of communication lists – opt-out and opt-in, which is standard in general (there’s also double opt-in, but it’s not type of list itself). Both of those types serve different purposes. When you are using opt-in list you want your customers to be aware of signing up – it’s their decision. For opt-out you decide not to inform your customers about signing them up on the list. On this basis, ShopMagic tries to sign up your customer whenever possible, that is when customer creates an account or submits an order – those actions triggers signup process. At the moment there’s no possibility to change this behavior (but it’s not said, it will not be changed in the future). From here, customer is only able to resign from email subscription for specified list.

Alternatively, if you do want not to inform your customers about signing them up on your list and have more fine-grained control about which customer is signed up to which list, you can create opt-in list and uncheck option to show it in the checkout. This way you will be able to sign up only those customers you actually want, keeping the opt-out functionality. I am aware, this may by counterintuitive, but as I mentioned, for the time being it’s the only way because of our current design decisions.

Nevertheless, stay tuned for possible upcoming changes!

Best regards,
Bartek

Hello @skus!

The database option is old way to link to unsubscribe page, so there’s no need for that element.

I assume, you’ve been trying to attach unsubscribe link with action settings checkbox, right? Could you try to use plain placeholder {{ customer.unsubscribe_url }}? This way we would ensure if placeholder generates problem or it’s the automation config.

Additionally, you can try to go into WordPress settings -> Permalinks and just his “Save” button to refresh links (unsubscribe page is now sort of virtual one).

Best regards,
Bartek