mapping to different categories possible?

[willemb2]

Describe your question

Newby here. Thank you for making this plugin available. Our foundation runs 3 news websites for slightly overlapping audiences. Some posts we publish on 2 or 3 sites. Multisite appeared to be no solution for us because you can't share a media library and some plugins don't work on multisite. So this is a great time saver for us.

Our 3 sites have different sets of categories and my editors prefer to keep it that way. But I noticed that when a category on mainsite.com is not present on remotesite.com, Distributor creates it. This results in too many categories on remotesite.com. Is there a way to set a mapping to a destination category in the pull- or push-process? I could not find anything in the documentation about this.

Code of Conduct

• I agree to follow this project's Code of Conduct

[jeffpaul]

@willemb2 there's no built-in way to do category mapping between sites, but you could customize that by extending Distributor via existing hooks to do that. If you're not able to extend that on your own, then feel free to reach out ([email protected]) if you'd like to discuss how 10up could help you with that via a consulting engagement.

[willemb2]

Thanks @jeffpaul , at least good to learn that I didn't miss something. I'm not a developer, unable to use the hooks. I'll tell my editors that if they want to use this attractive toy, they'll either have to reorganize their categories or attract more sponsors to finance paid customization.

BTW I did manage to add 2 of your snippets to our child theme's functions.php: 'Push original publication date' and 'Automatically unlink posts'. Works flawless!

[github-actions]

It has been 7 days since more information was requested from you in this issue and we have not heard back. This issue is now marked as stale and will be closed in 7 days, but if you have more information to add then please comment and the issue will stay open.

[github-actions]

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.