Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating bi-directional manual post connection #181

Open
benjaminpick opened this issue Feb 22, 2023 · 2 comments
Open

Creating bi-directional manual post connection #181

benjaminpick opened this issue Feb 22, 2023 · 2 comments

Comments

@benjaminpick
Copy link

Is your feature request related to a problem? Please describe.
I am using manual related posts a lot. And I realized that 95% of the times I also would like to create a manual post in the other direction, i.e. "1 is related to 2", and "2 is related to 1". (The remaining 5% is when 1 post has more related posts than would be shown anyway.)

Describe the solution you'd like
I would love a way of making the manual post connections bi-derectional. Two ideas:

  1. Either automatic
  • adding it as a setting
  • when active, the text in italics on the post edit screen will say so (e.g. adding "That post IDs will also get a manual related post to the current post.")
  1. Or semi-automatic
  • creating a button under the CRP tools
  • when clicked, it gives a notice "Added 14 manual post connections."

Both options would add the ID at the end of the manual related post list, if it is not already in that list.

What do you think?

@ajaydsouza
Copy link
Contributor

I like the idea. And, I've just marked it for implementation.

The option 1 is likely what I'd explore with a checkbox in the metabox that will allow a user to push the current post ID to the manual related.

@benjaminpick
Copy link
Author

Thanks! One more idea - in the 1% of the cases where I do not want a bi-directional linkage, I could add the ID on the list of "exclude POST ids".

Oh, currently this doesn't work, when the ID is in both lists the link is shown. Is this intended behaviour?

@ajaydsouza ajaydsouza added the pro label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants