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

[Feature Request] Make Multisite a real multisite #2330

Closed
mattcdavis1 opened this issue Jan 22, 2018 · 2 comments
Closed

[Feature Request] Make Multisite a real multisite #2330

mattcdavis1 opened this issue Jan 22, 2018 · 2 comments

Comments

@mattcdavis1
Copy link

mattcdavis1 commented Jan 22, 2018

Description

When you save an entry in Craft using multisite it saves the entry to all of the sites which is the exact opposite of what i want, and how one would expect a multisite system to function. Please change this functionality so that, at least by default or via some configuration, when an entry is saved it is only saved for the current site.

Sample use case: A restaurant chain that has different menus (menus channel) for each location and each location is a site. I don't want to see entries from location A in location B (disabled or otherwise). I just don't want them to exist period.

@mattcdavis1
Copy link
Author

It looks like the only thing that's needed is a hook to set $propagate. Right now, the entries controller calls Craft::$app->getElements()->saveElement($entry) with no 2nd or 3rd parameters. At minimum, it would be nice to have a hook just before this that would allow setting the $propagate flag.

@mattcdavis1
Copy link
Author

Hmm - looks like i can just bind my class to the elements service and override that flag. That may work, but still seems like the default should be to save to the current site only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant