Closed deltafactory closed 1 year ago
@deltafactory are the items you're changing in post content or meta?
I suppose it could be either but post content would be the most important to pull back to the origin. In our scenario we have some custom post types with specific meta values that we exclude through the appropriate filter so that they never leave their environment.
@deltafactory seems that perhaps the way in which you're editing the remote post meta isn't the best approach as you should be able to leverage hooks to edit that without making the post content itself unlinked
I'm not sure what you're referencing as far as post meta. My primary concern is post content but a solution should probably address meta as well.
Back to the original issue: I would prefer not to unlink the post in the first place, but we need the option to temporarily and immediately alter the live/target content so that it's different from the source. Ideally, we would be able to pull those changes back to the origin by finding the article from the external connections list.
@deltafactory the only way to support that flow currently would be to unlink the remote post to make those changes to post content. Getting that updated on the origin, currently, would be a function of replicating those changes on the origin post. Then updating the remote post so its linked again should get things all back in sync.
This issue has been automatically closed because there has been no response to our request for more information. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. See this blog post on bug reports and the importance of repro steps for more information about the kind of information that may be helpful.
Is your enhancement related to a problem? Please describe.
In our use-case we need to leave ourselves the option to make a change on one of the targets, putting it temporarily out of sync with the origin. The current workflow includes unlinking that post, making the change, and at some point re-linking the post so that it is subscribed to future updates.
We also expect that we'll want to pull the changes into the related post on the origin. On the origin side of the experience, this seems like it could fit within the Pull UI. Currently the only entries listed to be pulled for a given External connection/content type are ones that have never been associated.
I am using v2.0.0-rc1
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct