I have a custom post type which needs to be in sync between two different websites housed in different servers. If either site edits, inserts, or deletes, the other database will also have to update its database for the change. The issue I see is, the ID's will be offset between the two databases.
So my rationale is, why can't I create a custom post type to be housed in a different database table and just sync that one table between the two installations?
The issue I see is I need to take into consideration the conflicts such as URL's. Page slug "hello-world" and custom post type slug "hello-world" when accessing the URL site.com/hello-world .
Anyone point me in a direction?
Edit : Looking into it more and thinking about it. How about on save_post, check if it's THE custom post type, connecting to the other database, and doing a last insert ID, store it locally, and then update the external database with the internal ID of the post?