Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalWith OG, I have created my own switch by using file_field_paths and entering [node:group_content_access]/[node:nid] as the path to store files. In my case every node published should be in an OG. Depending on the visibility of the node published, the files are put into a public or private section.
Note however, that this heavily depends on the contents of the group_content_access or Group Visibility field.
See https://www.drupal.org/node/1919154
With OG, I have created my own switch by using file_field_paths and entering [node:group_content_access]/[node:nid] as the path to store files. In my case every node published should be in an OG. Depending on the visibility of the node published, the files are put into a public or private section.
Note however, that this heavily depends on the contents of the group_content_access or Group Visibility field.
See https://www.drupal.org/node/1919154
With OG, I have created my own switch by using file_field_paths and entering [node:group_content_access]/[node:nid] as the path to store files. In my case every node published should be in an OG. Depending on the visibility of the node published, the files are put into a public or private section.
Note however, that this heavily depends on the contents of the group_content_access or Group Visibility field.
With OG, I have created my own switch by using file_field_paths and entering [node:group_content_access]/[node:nid] as the path to store files. In my case every node published should be in an OG. Depending on the visibility of the node published, the files are put into a public or private section.
Note however, that this heavily depends on the contents of the group_content_access or Group Visibility field.
See https://www.drupal.org/node/1919154
With OG, I have created my own switch by using file_field_paths and entering [node:group_content_access]/[node:nid] as the path to store files. In my case every node published should be in an OG. Depending on the visibility of the node published, the files are put into a public or private section.
Note however, that this heavily depends on the contents of the group_content_access or Group Visibility field.
With OG, I have created my own switch by using file_field_paths and entering [node:group_content_access]/[node:nid] as the path to store files. In my case every node published should be in an OG. Depending on the visibility of the node published, the files are put into a public or private section.
Note however, that this heavily depends on the contents of the group_content_access or Group Visibility field.
See https://www.drupal.org/node/1919154
With OG, I have created my own switch by using file_field_paths and entering [node:group_content_access]/[node:nid] as the path to store files. In my case every node published should be in an OG. Depending on the visibility of the node published, the files are put into a public or private section.
Note however, that this heavily depends on the contents of the group_content_access or Group Visibility field.
