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

FR: Disable propagation of entries on structures #2386

Closed
riasvdv opened this issue Feb 1, 2018 · 21 comments
Closed

FR: Disable propagation of entries on structures #2386

riasvdv opened this issue Feb 1, 2018 · 21 comments
Labels
content modeling 📓 features related to content modeling enhancement improvements to existing features

Comments

@riasvdv
Copy link

riasvdv commented Feb 1, 2018

Description

The propagate entries toggle that was introduced in a3cc52f seems to only be available when using channels, is it impossible to have this for structures?

Steps to reproduce

  1. Have a multisite
  2. Edit a structure section
  3. See no toggle :(

Additional info

  • Craft version: 3-RC8
  • PHP version: 7.1
@riasvdv riasvdv changed the title Propagate entries only on channels? FR: Disable propagation of entries on structures Feb 1, 2018
@brandonkelly
Copy link
Member

In order to get this working, Structure sections will need to start managing entry hierarchies on a per-site basis (when site propagation is disabled). Which means moving the structureId out of the sections table and into the sections_sites table, etc.

@brandonkelly brandonkelly added the enhancement improvements to existing features label Feb 1, 2018
@mattcdavis1
Copy link

@brandonkelly - any chance we can do this pre-3.0? The current state pretty much renders structures useless for multisite installations.

@brandonkelly
Copy link
Member

@mattcdavis1 We don’t have the resources, so no unless you want to submit a PR.

@lenvanessen
Copy link

Absolutely a must for Craft 3!

@jcherniak
Copy link
Contributor

Any chance this might make it in soon? I'm working on a big multi-site project and can't use Structures without this.

@brandonkelly
Copy link
Member

@jcherniak it’s on the 3.1 list – so in the next 2 months or so.

@craftcms craftcms deleted a comment from naboo Aug 14, 2018
@craftcms craftcms deleted a comment from FrankZwiers Aug 14, 2018
@craftcms craftcms deleted a comment from miro94 Aug 14, 2018
@craftcms craftcms deleted a comment from bfopma Aug 14, 2018
@craftcms craftcms deleted a comment from estebancastro Aug 14, 2018
@craftcms craftcms deleted a comment from aaron-dotdev Aug 14, 2018
@michaelhue
Copy link

@brandonkelly Are you still taking pull requests on this? I'd like to give it a shot. :)

@Raabye
Copy link

Raabye commented Aug 28, 2018

ETA on this? Multisite will be next level with this feature.

@brandonkelly
Copy link
Member

@michaelhue No need, but thanks anyway :)

@Raabye Soonish.

@jerome2710
Copy link

@brandonkelly Would be nice to communicate a date to our paying Craft Pro clients hear what 'soonish' is, as this issue already exists since February.

@brandonkelly
Copy link
Member

@jerome2710 As said it’s coming in 3.1. Not ready to give a release date for that so let’s just say by the end of the year.

@brandonkelly
Copy link
Member

Just got around to implementing this for 3.1, and realized that I was drastically overcomplicating it in my head, and there’s no real reason that each site can’t just share the same nested set tree (“structure”) behind the scenes. So it’s now added for the next 3.0 release.

@narration-sd
Copy link
Contributor

good on ya ;)

@naboo
Copy link

naboo commented Oct 20, 2018 via email

@richhayler
Copy link

This is friggin awesome!! Thanks amazing CraftCMS team 👌😊

@naboo
Copy link

naboo commented Nov 2, 2018

Would it be possible to extend this to categories as well? (since categories are just structures, right?)

@brandonkelly
Copy link
Member

@naboo We’re planning on adding this and other multi-site features to categories in 3.1.

@naboo
Copy link

naboo commented Nov 2, 2018

Thank you sir!

@jcherniak
Copy link
Contributor

Did this make the cut for 3.1? I don’t see it in the release notes. Are we kosher to use structures on a per site basis now?

@brandonkelly
Copy link
Member

@jcherniak This has been implemented for Structures since 3.0.28 (see #2386 (comment)).

We weren’t able to implement it for category groups yet as we originally hoped to do in 3.1, but that’s on the short list for 3.2, which won’t be more than a few months out.

@jcherniak
Copy link
Contributor

jcherniak commented Jan 18, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content modeling 📓 features related to content modeling enhancement improvements to existing features
Projects
None yet
Development

No branches or pull requests