Bartek

Hi @2alexazar, @attila73 and @pierremichaux!

I am deeply sorry for the inconvenience caused by our plugin after recent release.

With 3.0.2 update, everything should be back in order!

@2alexazar thanks for confirmation!

@attila73 and @pierremichaux, please, update ShopMagic and check if the issue is gone already!

Apologizing for troubles,
Bartek

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.www.ads-software.com/browser/woocommerce/trunk/includes/class-wc-emails.php#L403

Hope it will help with resolving their issue!

Hi @victor307!

Options you mention are good to delete, except the one you have doubts – this one is set by WordPress and displays the date of plugin activation. Nonetheless, it’s not our option, I don’t think it could be harmful to delete that one as well.

Best regards,
Bartek

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 @victor307!

Actually, it might be a good idea to allow users seamlessly delete plugin with data. For the time being, to remove whole plugin, start with standard deactivation. Then, you may delete all database tables who start with name $prefix_shopmagic_. If you’d like to be totally precise, there may be some options set in wp_options table. All of those are prefixed with shopmagic as well.
Lastly, if you don’t use any other WP Desk’s plugins, you might also want to look in your server for wp-content/uploads/wpdesk-logs folder.

By this point, you will delete completely ShopMagic from your website.

Best regards,
Bartek

PS
Let me know, is there any specific reason for removal of ShopMagic? Was it underperforming for you?

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 @snerbalu!

We’ve been trying to reproduce your issue in our environment, but ShopMagic works properly, when creating custom status and trying to trigger on such status change. It’s been tested with free version of plugin you mention.

Colud you describe the way to trigger the bug in more details, possible for us to reproduce?

Maybe the issue is somewhere else – you might debug your website for WP Cron functionality with WP Crontrol plugin – maybe some events just doesn’t trigger at the time they should. Additionally, there are possibilities that some info would be logged in WooCommerce status, possibly in fatal errors log. Try to provide more info about the issue you experience, this will help solving the bug.

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 @devbd!

I’m sorry for the issues caused. Could you tell me, which version of ShopMagic do you use? We’ve been trying to solve this issue in 2.37.10 release, so I need to know if we failed to do that properly.

If you actually run 2.37.10, let me know what are the steps to reproduce the error? The issue you describe is related to emails sent from ShopMagic and possibly attachments, so if you could find out which precise automation causes the issue and send the configuration to us, it would be very helpful. (You can share configuration either through screenshots or ShopMagic function to export automation as JSON file).

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

Hi @niexukang!

I just wanted to let you know that upcoming release will feature both {{ order.billing_company }} and {{ order.shipping_company }} placeholders!

Keep an eye for it!

Best regards,
Bartek

Hi @beflanet!

Sorry for the late response.

For what you suggested, data in “_op_order” is an array, so you have to do two following things – firstly call to retrieve actual meta value (not dynamic property, as you’ve tried with $this->get_order()->_op_order), then get the value from array.
I assume that you should create method body similar to:

public function value( array $parmeters ) {
  return $this->is_order_provided() ? $this->get_order()->get_meta('_op_order')['note'] : '';
}

This may not be fully functioning, and you have to tailor it to your needs basing on your knowledge.

Best regards,
Bartek

Hello @abbasspacetap!

We do actually have a placeholder for billing phone (named {{ order.billing_phone }} ), but it’s only available in order context events, meaning that if you use such events as Order New, Order Status Changed, etc. it will be visible to you. On the contrary, customer based events (Customer – Account Created, Added To List) don’t have access to order context (order can contain customer, but customer cannot contain single order to fill this context), meaning you can’t use (and it’s invisible) billing phone placeholders.

Best regards,
Bartek

Hi @beflanet!

I see. In such case it would be the best to write a custom placeholder yourself which will be able to get a value from array returned in _op_order meta value.

You can look up how to create placeholders in our documentation: https://docs.shopmagic.app/article/174-adding-custom-placeholders

Hi @beflanet

Is it something that placeholder {{ order.meta }} can handle? If it’s stored in postmeta table related to the order, I guess it would be possible to use {{ order.meta | key:’_op_order’ }} to get the value.

Let me know if this helps.

Best regards,
Bartek