cant create post with tags in UA, tags are deleted after creation

Any solutions for this problem ? Why Uncanny Automator while creating a post is deleting structure of post and delete (html, body, head, style) tags ? And also delete inline styles I create in post structure.

Hi @mwekierowca ,

Sorry to hear about the issue.

I wonder if you can potentially include a screenshot of the current recipe so that we can see your trigger and action, and especially how you’re populating HTML. Depending on what it is, we should have filters you can use to disable sanitization and leave your content intact.

If this is related to creating the post alone, you can use this filter:

add_filter( ‘automator_create_post_sanitize_meta_values’, ‘__return_false’ );

Note the double underscore for the second parameter of the add_filter function call.

If this is for post meta, try this:

add_filter( ‘automator_wp_set_post_meta_should_sanitize_fields’, ‘__return_false’ );

Please let us know if that addresses the issue you’re having.

https://ibb.co/hXDSVZp
https://ibb.co/0sRqL1x
https://ibb.co/pwbPdRS
https://ibb.co/SdX6CgR
https://ibb.co/pnGGgHw

As you can see I even tried to use meta keys to simulate html structure. I tired as metakeys, and as normal html (as you also can see in images), but at the end Automator makes this structure disappear and I can’t send all styling etc. to this post. What I should do ?

Hi @mwekierowca ,

Can you confirm first that you did add the filters to your child theme’s functions.php file, or how did you do it?

Having said that, you will still have issues with the content that you tried to use. Since this does use a TinyMCE editor, it does check for valid HTML for a post and will remove anything that’s invalid.

For this action, Automator is effectively creating the body of the post, not the content of the whole document. This means that HTML elements like DOCTYPE, html, head and body tags would be invalid; duplicating these tags in your post content could break the page layout.

We re taking a look at potentially support style and script tags with a filter override, but there is still a lot in your example that could not be properly supported.

It will take us a few days to potentially implement a way to support additional tags, but hopefully the feedback above is helpful for now.

Since it has been over a month, and the last release included support for new CSS and JS fields during post creation, we’ll go ahead and close this ticket.