Uncanny Automator

Hi @whichtransfers ,

We have a few Automator sites using that plugin without issue, though we don’t have explicit support for its fields. What you can do though, assuming records are being stored in post meta, is to use our post meta tokens (https://automatorplugin.com/knowledge-base/post-meta-tokens/) to look up values by order ID.

What we might suggest here is to check the post meta table in PHPMyAdmin (or however you access your database), look for all records for the order ID of a recent post, then identify the meta keys there that you want to target in your recipes. Based on what we’ve seen with that plugin, custom fields generally have this prefix: _billing_.

Here’s an example we have from another user mapping several custom checkout fields in a Google Sheet action, so you can see how the post meta tokens are set up: https://cln.sh/pBXtWzNr

Thanks @condraw , we really appreciate the review and the kind words!

Hi @dmorgan20 ,

Sorry to hear about the issue.

It would really help if you could send over a screenshot of the recipe with everything expanded, especially so we can see what tokens you’re using and how the image is being set. If you’re using our Pro plugin, maybe you could try adding a delay of a few seconds to the action in case the image isn’t available at the exact moment the post is published (perhaps it’s being added a split second later).

Our team also wondered if you have OG meta tags enabled, which can help social media platforms identify which featured image to use. If you can share the URL of the post that triggered the recipe it would help if we could examine that too, but if you can’t for privacy reasons then we certainly understand.

Hi @kaklappen,

The trigger you are requesting support for (in your screenshot) is only available in the Pro version of Uncanny Automator: https://automatorplugin.com/integration/rafflepress/

I’m not a developer, but you’d probably need to look at the file uncanny-automator/src/integrations/rafflepress/helpers/rafflepress-helpers.php.

If you need additional help, we’re happy to provide it via your account page. Providing support to verified customers is something we do to ensure we’re building a sustainable business.

• This reply was modified 2 months, 4 weeks ago by Uncanny Automator.

Hi @kaklappen, thanks for reaching out!

You’re right, those tokens don’t seem to be available currently. ?? I’ve added a note to our Uncanny Automator Pro feature request board to add them to that trigger. I can’t offer an ETA, but we’ll certainly reach out when they are available.

If you shoot us an email at [email protected] we’ll make sure that request gets linked with your license so you can get follow-ups through our help desk system.

Thanks!

Hi @disilbax, thanks for the feedback. We discovered two other sections of code that required an update. They will be included in the next release, which does not yet have a scheduled date. Here they are if you want to start using them now:

wp-content/plugins/uncanny-automator/src/core/lib/utilities/class-automator-input-parser.php

wp-content/plugins/uncanny-automator/src/integrations/wp/actions/wp-createpost.php

You’ll also need to use this updated snippet in your functions.php file:

// 1. Fix in the recipe editor.
add_filter(
'automator_wpcpostcontent_should_wp_slash',
function( $data ) {
return true;
}
);

// 2. Fix the parser.
add_filter(
'automator_parse_token_parse_text_autostripcslashes',
function( $text ) {
return false;
}
);

// 2. Fix wp_insert_posts
add_filter(
'automator_create_posts_should_wpslash',
function( $action_data ) {
return true;
}
);

Hope this update finally gets you up and running. Sorry for the inconvenience!

Hi @marccitroen, thanks for confirming! I’ll mark this closed for now, but feel free to update it if you run into any issues.

-Ken

Hi @paveldohnal, just wanted to confirm an update for this was included in version 5.10, released yesterday.

Hi @marccitroen, thanks for your patience as we investigated this issue.

What we think happened here was a combination of issues. We weren’t able to replicate the initial error you reported, but we were able to replicate the second, which was fixed in the release that went out moments ago (version 5.10.2). We believe the first issue you encountered was actually due to a corrupt installation, while the second due to a bug that we fixed.

Can you try updating to 5.10.2 and let us know if that resolves the issues you were seeing?

Hi @disilbax, thanks for your patience. We’ve added a filter that should give you the results you’re looking for. That update will be available for download later today (version 5.10.2).

Once you’ve installed that update, you’ll need to add this snippet to your theme’s functions.php file:

add_filter( 'automator_wpcpostcontent_should_wp_slash', function( $data ) { return true; } );

Then give it a try and let us know if it works!

Hi @disilbax, got it. I understand completely now. Sorry for the back and forth!

Being able to use the content of a webhook response in a recipe is a feature of Uncanny Automator that I think is really great…and using the webhook response to create a post is quite a clever usage of that feature!

I’ve assigned our developer to take a look at the JSON you provided earlier and I hope he can come up with a solution for you tomorrow. If we need any additional info I’ll reach out here.

Hi @disilbax, got it…thanks for clarifying! I misunderstood your original message.

Since incoming webhooks are a Pro feature and in case we need additional site-specific information to troubleshoot, can you please open a ticket from your account page? https://automatorplugin.com/my-account/tickets/ You can also send an email to [email protected] if that’s easier. ??

I’ll keep an eye out for it and make sure it gets assigned a developer as soon as it comes in.

Hi @disilbax, thanks for the update.

You mentioned that when you view the published post after it’s created by Automator, it looks fine, but when you open it in the WordPress editor, that’s when the issue appears. So it seems as though the sanitization is being applied by the editor.

I’m not sure that’s an issue we can resolve, but perhaps you could tell us what editor you’re using. Could you also try a different editor to see if that resolves the issue? For example, if you’re using the block editor, try the classic editor, and vice versa?

Hi there, the site appears to be working now; is Uncanny Automator still active?

If not, can you try deleting Uncanny Automator and reinstalling it? This error is likely caused by an incomplete or corrupted installation.

Please let us know if that fixes the issue for you.

Hi @disilbax ,

Sorry to hear about the challenges.

We explored this with our dev team and they wondered if you could possibly provide a sample of the full data set (maybe cross out anything sensitive) for their review. It would also help if you could go to the list of all Automator recipes, hover over the recipe in question here, then click the Export link. It would really help if we could see the JSON file. You could post a link to it here or send it to us via our website.

Thanks