wundermatics

Hi

This plugin doesn’t have a settings page. It really only adds a Formula field when you are editing a field on the standard ACF Field group edit page.

Here’s a short intro including a screen shot of that it should look like in ACF:
https://www.wundermatics.com/doc/calculated-fields-for-acf/basic-usage/

Hi Markus,

Sorry to hear that. Could you perhaps send us using a screenshot of your workflow, it’s so much easier to get the full context of what you are doing.

If you’re more comfortable with sending it privately, please email us at [email protected]

@opicron,

Thanks for reporting this. I think I’ve mentioned earlier that we’re preparing another patch / bug fix release. We’re aiming to get to the bottom of these issues in that release.

For reference. Do you see these issues in the same workflow that you sent screenshots of earlier?

Ok great to hear!

We will get a bug fix out asap to make sure the roles work as intended.

Hi opicron,

I can confirm that we have a bug with the roles. We’re preparing a bug fix release within the next few days.

I’ve recreated your workflow on a fresh stock WordPress 5.7 install. It works as intended but I may have missed something in recreating your workflow. Have a look at these images including the log output.

WunderAutomation sample workflow + log

Could you set your log level to DEBUG (under settings) and grab a screenshot of the log after a simple post publish?

Hi,

Just to confirm we have received your message here and over at support.wundermatics.com. We are working with trouble shooting this, we’ll get back to you as soon as we can.

Hi @infohouse25 ,

Thanks for geting back to report this issue, even if it wasn’t the feedback we hoped for.

A bit of background:
The plugin uses meta data (a hidden custom field) on the post/order object to remember if that post/order had triggered that workflow id previously.

Before the upgraded version was installed, our plugin didn’t write the correct meta data to the affected post/order, so no “memory” of previous workflow execution would be written to the database.

After 1.6.3 was installed, the post meta field is correctly written to the database. But because of the bug, no memory of previous executions exists. So for any given post/order, a workflow with run-once will be effectively run one more time.

So just to clarify before we dive back into this issue:

When you say that you still see the same bug. Is it possible that you’re seeing the effect of “no memory” for an existing post or order. Or can you reliably reproduce the error for a new order and have a workflow run over and over again even if run-once is set?

Hey @opicron, would you mind posting a screenshot of your workflow settings? Either here or over at https://www.wundermatics.com/support/contact/

Hi shalarmd,

We’ve tracked down a couple of issues that caused problems with updating custom fields. We released version 1.6.3 with fixes for these issues. Please have a go at upgrading to that version, I think it will fix your issue.

If not, please reach out to us again.

Hi,

Update. We’ve just released 1.6.3 that has a fix for the runonce issue. We’d be very interested in hearing your feedback on the new version. Either here in the .org forum or on our support page:
https://www.wundermatics.com/support/contact/

Hi there,

So this isn’t really within what we can do with WunderAutomation, I’ll explain why.

When WordPress prints to the Dymo printer, the actual print command is sent from your Mac/PC sitting in the same office as the label printer itself. To make it work your Mac/PC needs to have the Dymo printer drivers installed and it needs to be connected to the printer. Technically speaking it’s not really WordPress that sends the print command, it’s rather your browser.

The kind of automations that WunderAutomation deals with is executed on the web server, often installed in a cloud server somewhere far from your office. The web server typically don’t have the Dymo drivers installed and is rarely connected to the Dymo printer. It’s perhaps possible, but not easily.

What you are looking for is client side automation or just “RPA” as people call it these days. I found this blog post about a few different available options:
https://www.maketecheasier.com/extensions-automating-repetitive-browsing-tasks/

Hi,

Thanks for reporting this.

We’re aiming to release a bugfix update within a few days, we have a few issues sorted in cooperation with other users. As with them, we’ll try our best to replicate your issue in our test environment based on your input and have a fix in the next release.

If you want to contribute to our efforts to with additional details, screenshots etc. you’re more than welcome!

Hi @infohouse25,

Can you share what your workflow looks like. Which object type is your workflow triggering on?

PS. If you’re not comfortable doing it in public you can get in touch over here: https://www.wundermatics.com/support/contact/

Hi @shalarmd,

Thanks for reaching out and reporting this issue. We can confirm you have found a bug in this release. If it’s not too much trouble for you, we’d like you to help us by contacting us via our support page.

What we will do is:

1. Send you a patched version of the plugin with a fix for this bug
2. Have you test it and hopefully you can confirm that the bug is fixed
3. Release the bug fix in the next version (1.6.3) next week. You can continue using the patched version in the mean time

To get started, just contact us here: https://www.wundermatics.com/support/contact/

If you’re not too keen on the above process You *should* be able to get rid of this error by just lowering the log level to “INFO” in the plugin Settings. And then just wait for the 1.6.3 version to come out.

Hi,

We’ve fixed an issue concerning filter evaluation and released version 1.6.2 of the plugin. Please upgrade as soon as possible. Don’t hesitate to reach out if you’re having further issues.

Sorry for the inconvenience.