Missing Hook After Cornerstone finished saving

Hey there,

I was currently searching for a hook that fires after cornerstone is saving his data to its postmeta values and to the post content section.
Unfortunately I was not able to find a action or a filter who fires especially just for the saving of cornerstone.
In the end I tried the default wp_insert_post hook, but this is also not possible in my case, because I use the wp_update_post hook inside the custom wp_insert_post function wich triggers a loop.

At the moment there is no possibility to have a specific hook regarding to that.

It’ll be cool if someone can include an action to the end of the ajax_handler function in the following file:
/wp-content/themes/pro/cornerstone/includes/classes/builder/class-save-handler.php
after line 65.

Hey,

This article should help you: https://theme.co/apex/forum/t/customizations-actions-and-filters-in-x/208

Indeed I know what a hook is haha
But thanks for mention this again.
If you check the file I’ve mentioned above, you’ll see that there is no hook available for saving the page in cornerstone.

Hi There,

We can add this as feature request but before we proceed to do that, would you mind discussing what you are trying to achieve and you need this hook?

Hi Lely,

thanks for your answer.
One of the many examples I’m needing this is the duplication of the cornerstone post_content to it’s wpml translations. They should synchronize after every saving process of cornerstone.
In my case this should happen just with cornerstone sites.

Best regards
Jannis

Hi Jannis,

The following articles might help to achieve that instead of waiting for a feature request:

Hi Lely,

thanks for the update. I know that there is the possibility to duplicate the sites programmatially with wpml, but I don’t want, that the other values of the site gets changed. I really just want to affect the post_content and the cornerstone meta values.
Currently I’m using the wp_insert_post hook and in that I’ll check against a global set value to make sure that the hook doesn’t fire again after calling it through itself via the wp_update_post hook.

Best regards
Jannis

I understand that, Jannis. Regretfully, this would be getting into custom development which is outside the scope of our support. If you have a tight deadline, please consider hiring a third party developer. My colleague has submitted a feature request but please not that it could not be instantly added nor we promise it will be added at all most certainly for negative reasons.

Thank you for understanding.

Hey buddy,

thanks for your update. I don’t need support at all with the current solution I’ve made. It’s kind a workaround but it works pretty well.
At all the action wouldn’t be a security issue, because you just trigger a function, if you use a simple do_action.
You can see this topic as completed.

Cheers
Jannis

You’re always welcome Jannis!

Cheers.