I created a new feature called event but it seems to be always on. See the attachment. The blocks associated with this feature are always available
I created the view:
I set Spaces: Node in current space
nodes: advanced_event, and event (which comes with atrium)
I created a content
spaces> features > mynewevent
spaces: site and group
permissions- i just set this to authenticated
I originally had this set to spaces permissions per instructions on node/449 but nothing showed up. Do I need to do something special for this permission to valid?
I originally had the event in the navigation menu. I moved it to features so that the icon might show up.
I tried to set sitewide context to false but that setting will not save.
GENERAL Questions: what does spaces permissions do on the view?
what does spaces: node by type mean in a view filter?
Is this the most upto date instructions for creating features https://community.openatrium.com/documentation-en/node/449
do I still have to modify the *.info file to add spaces, feature menu, etc? I did but wanted to know if it is necessary
| Comment | File | Size | Author |
|---|---|---|---|
| feature-error.jpg | 11.42 KB | socialnicheguru |
Comments
Comment #1
socialnicheguru commentedI chose spaces-site and spaces-group and thought that the context would only show up in one or the other.
That is not what happened.
Instead, the feature was always selected for all spaces.
I had to not select anything under the spaces option.
Comment #2
socialnicheguru commentedComment #3
steven jones commentedGiven that lots of others have context and spaces working hapilly together, I would suggest that this is a misconfiguration.
Comment #4
steven jones commentedActually looks like this is a duplicate of #544640: The Context UI doesn't display Spaces feature reaction