Did make.com change something about the way the “WordPress - Create a post” module works?
I have an automation which has been running for months without issues.
Then it suddenly did not format elementor pages correctly anymore.
How it works
The automation takes the content and meta data of an existing WordPress (Elementor) page.
Then it modifies the content and elementor meta data a little bit (different links and text).
Finally it creates a new Elementor page, using the new content and elementor meta data.
Issue
Suddenly the automation doesn’t format the WordPress pages for elementor properly anymore.
I get a page without the actual elementor styling.
First I thought that this issue could be caused by updates on my WordPress page.
But (1) I didn’t do any updates and (2) I’ve tried the same on a different elementor page and it also doesn’t work on this page.
So I assume that make changed something about the way it formats and sends data in the “Wordpress - create a post” module (probably in the meta fields. Elementor wants the `_elementor_data` in a pretty weird format).
Anyone with similar issues/fixes?
And if anyone from the make team listening: Did you change something about the way the “Wordpress - create a post” module works?
I’m in touch with the make support team (via ticket) and to me it seems very clear that the issue is in the make plugin for wordpress.
However I haven’t received a reply from the make support for about one month.
Would be great to get this issue fixed.
Hi Samuel,
That’s very frustrating, and I’m sorry that you’ve had such a hard time getting a response. I’ve raised this issue internally, so hopefully someone should get back to you very shortly
Hi again @SamuelHartmann – I just wanted to update you that the issue is now definitely being dealt with, and has been escalated on the priority scale by the dev team. We will notify you the minute that there is a concrete update. Thank you so much for your patience.
Thank you @Marina.
I also got the following feedback inside the support ticket 9 days ago:
Thank you for your patience and for following up on this issue.
The current status of this issue is that it is on the To-Do stage with High priority. As soon as there is capacity to work on this, they will work on it, and we will inform you as soon as there is any meaningful feedback from the dev team.
Hi Samuel – thanks for flagging. I will check on this internally now and get back you you ASAP. I’m sorry that you’re having such a hard time getting a response.
My sincerest apologies again for the delay on this. I just heard back from the dev team, who have informed me that they have just released the fix. They asked me to advise you to update the WordPress Plugin to the latest version 1.6.6 – would you please be able to do that and check if the problem is resolved?
