You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a post made also on the OA forum. However, the actual issue is really an Atrium Folder one.
When creating a new Group, you have to enter a path.
This seems logical, until other elements depend on the URL being the actual node path.
For my intranet, I have no need for nice looking URLs, and I personally think the path feature in Organic Groups is not a good idea anyway (because the node path already exists, so it is starting with a duplicate - this kind of thing should be left to pathauto, etc).
The main problem for is that Atrium Folders doesn't work correctly with the Organic Group human-made path. Atrium Folders need the node path. For example:
Create a new group called 'My friends' The Group add page requires a 'path' to be entered, which logically could be '..../myfriends' Save group (lets assume the node path for that Group is 'node/10')
Now, seems ok so far. However, straight-away we have a duplicate URL. Luckily this is intranet so forget Google concerns. However, it still seems a waste, and prone to issues.
Now try to use Atrium Folders. If you navigate to '...../myfriends' you'll see you group, but clicking on 'Folders' will lead you to an error / blank page.
If you navigate to '...../node/10' then the same group page displays, plus clicking on Atrium Folders works fine.
The text was updated successfully, but these errors were encountered:
I thnk I resolved / clarified the issue. Not so much to do with Atrium Folders. Open Atrium is forcing the creation of a path name when creating a group, rather than just leaving it as it's node path. Giving this system is intranet use mainly, then this makes little sense to me.
The issue with Atrium Folders was the view folder_folders had arguments not picking up the OA page. I don't know why this started to happen, assuming due to some other change. I just recreate everything again.
One more thing. This is a great add-on to OA. Why are you no publishing this on drupal.org and / or OA? 23 issues is not a lot giving how useful this extension to OA could be.
On drupal.org you'd have 1000s of people interested. I also think you could make more of this, and create a lot of publicity for your company from it.
(1) Went to site building > features > manage
(2) Went to "features" and clicked "recreate" under Atrium Folders
(3) Under "view" I noticed that strongarm had been overridden. I toggled strongarm so that it would return to default settings.
Everything is working fine now. I have no idea what caused the issue.
This is a post made also on the OA forum. However, the actual issue is really an Atrium Folder one.
When creating a new Group, you have to enter a path.
This seems logical, until other elements depend on the URL being the actual node path.
For my intranet, I have no need for nice looking URLs, and I personally think the path feature in Organic Groups is not a good idea anyway (because the node path already exists, so it is starting with a duplicate - this kind of thing should be left to pathauto, etc).
The main problem for is that Atrium Folders doesn't work correctly with the Organic Group human-made path. Atrium Folders need the node path. For example:
Create a new group called 'My friends' The Group add page requires a 'path' to be entered, which logically could be '..../myfriends' Save group (lets assume the node path for that Group is 'node/10')
Now, seems ok so far. However, straight-away we have a duplicate URL. Luckily this is intranet so forget Google concerns. However, it still seems a waste, and prone to issues.
Now try to use Atrium Folders. If you navigate to '...../myfriends' you'll see you group, but clicking on 'Folders' will lead you to an error / blank page.
If you navigate to '...../node/10' then the same group page displays, plus clicking on Atrium Folders works fine.
The text was updated successfully, but these errors were encountered: