-
Notifications
You must be signed in to change notification settings - Fork 116
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
Cannot add new block inline with subsites #526
Comments
If I don't use the elemental subsites compatibility module it works fine for me. I'm not sure what the compatibility module is doing to be honest. It's putting |
I'm not really sure either. I think it's there to support the elemental-virtual module functionality, where you could use a block on multiple pages via an unversioned many many. Since SilverStripe Ltd doesn't support that module, perhaps we could remove the subsites compatibility module from the content blocks recipe and CWP kitchen sink, and add a note to the virtual module suggesting you install the subsites compat module if using virtual elements on a project with subsites |
Yeah I didn't get a chance to check out that module today or play around with this some more to figure out its purpose. I'll try to get some time before the beginning of next week. Otherwise I agree with removing it. Currently it works better without it than with it (in the context of subsites). |
Given that initial investigations seem to imply that this issue is being caused by the
Edit: investigation issue captured here: dnadesign/silverstripe-elemental-subsites#7 |
Cool - so then our fix for this issue is largely internal, and would amount to removing the module from the CWP kitchen sink |
We've removed it from the recipe - closing |
Version: CWP 2.2.x-dev
Expected: should add a new content block
Actual: nothing happens
GraphQL response returns successfully (it would seem) but with no records in it.
The text was updated successfully, but these errors were encountered: