Open Atrium feature broken

I found that after downloading the feature from http://community.featureservers.org/content/filedepot-6x-11 that I couldn't get it to show up in the features list.
I found that the the _filedepot_feature_menu_default_items() function doesn't appear to be triggered, so I created a new menu item under the "Features" menu called "Documents" with a path of "filedepot" and now everything appears to run OK.

subscribing

I too though this did not work, but after a bit of systematic testing found that the permission structure does work, just probably not as expected.
Things to note:

• You must manually create a folder for each group that you wish to have a folder.
• You must manually set the permission on each folder so there is access for that group, and remove access via roles.
• If user A is a member of Group 1 and Group 2 then they can see the Group 1 and 2 folders from within Group 1 and from within Group 2.

I think this mode of opperation is counter intuitive and should be changed so that:

• When the file deopt feature is enabled for a group then a folder is created for that group (with the name of the group)
• When the group is renamed, so is the folder (This will require a mapping between filedepot CID to organic group GID mapping to be maintained - maybe in a drupal variable??)
• When the group is deleted, so is the group folder
• The folder which is created should automatically have the permissions for the group applied to it as per the defaults (an admin interface would need to be added so that defaults could be set).
• Each groups folder should only be visible from within the group.

subscribe

The original issue description was changed since OA9 was not available in Sept 2010.

Initial integration and testing as well as building a OA feature was done in May/June 2010 on what was likely OA7. I suspect it should not take someone too long that knows OA to use my initial feature and update it for OA9.

For now, I will wait until OA RC1 or Final is available unless someone has a client project they need this for, in which case, feel free to contact me.

I've been spending some time on the OA feature and have sorted out the menu/icon issue and there is a related fix in issue http://drupal.org/node/798220#comment-3302554 that I will role into the next release shortly.

I wanted to get some feedback on aaron's #4 comment above. I like the idea of auto-create of a top level folder when a group is created and setting the folder permission for that group. Changing the folder name when group name is changed also not an issue. The new CVS code already has HOOK_OG support now.

I don't think deleting the group folder(s) automatically is a good idea. The admin can delete that content or may want to re-assign it. Not all site admin's would expect the auto-delete to occur and may be very surprised to find out when all those files are gone.

If a user is in the sales group, they also may need to see common company folders and files so isolating a user to just their top level group folders may not be best. This would lead to content being copied just so all groups have access to it. Thus if a user is a member of more then one group, they will see those group related folders.

One solution I see is having a 'Group Private' option that is set at the top level folder only when the folder is automatically created. Any folders created under this top level folder would also then be hidden unless the user was in that group. A site admin can still then create top level folders that should be shared by more then one group or accessible by all site members.

Looking for comments / feedback.

Is this feature still available for download somewhere?
It seems that none of the features hosted on community.featureservers.org are available for download :(
Also no responses to similar problems posted on the forums.

Thanks in advance for any help, and have a great day!
Johan.

I've been working on a new version of the OA Feature for Beta 9 but it depends on the current DEV release or GIT branch 6.x-1.1 of the filedepot project and I want to complete my dev release changes so that I can get the 1.1 version released. Then I will update the filedepot feature on the OA community server.

subscribe

Since filedepot got a 1.1 version , is there any update on OA feature?

Subscribing!
Thanks for your work!

subscribe

Don't know where this has gone form the last couple of posts but here's my two cents on what folders should be available in Open Atrium. Open Atrium is setup without a concept of "Global" in terms of having a piece of content available across multiple groups. For example, we use OA for our client collaborate tool. It would be great to create a set of documents that are the user manual and have them automagically show in every client group but that's not the way it's designed. (There are specific overrides in the code that prohibit folks from multi-selecting groups on content creation).

While it's debatable if this is a good approach, I think the intent was to preserve the mental model. What we instruct folks is that when you enter a specific group, you see only the stuff for that group. The groups are "firewalled" from one another so that the documents that you upload to your group don't accidentally bleed out to the other groups. This puts our clients at ease and helps them understand the way OA works.

For the things that are intended to be "global," we have a "Clients" group to which we grant everyone access. We can link from their groups to the "Clients" group and all is still ok. The reason I bring this up is that my suggestion would be when I click on the FileDepot icon in a particular group, I expect that it's a file area private to that group. The folders should be specific to that group just like the blogs or documents or cases are specific to that group. It fits the mental model.

My 2 cents...Thank you for a GREAT module and feature

Not sure why blainelang isn't posting the link here as well , but anyways here's the post : https://community.openatrium.com/issues/node/2503#comment-6862

Sorry if I missed something but I'm not sure if the functionality to create a group folder along with a new group is available already.
Did anyone try this feature http://www.nextide.ca/downloads/filedepot_feature-6.x-1.2.tar posted on the OA community with another D6 non OA install? I use commons and would like this function in D6 on commons as well but really unclear to me if that was released or not. doesn't look like it's part of the last dev version. I can be wrong though...

I have just committed to the 6.x-1.x-dev "master" branch, changes to support better integration with Organic Groups as per my comment #8 above. This required quite a few changes so I'd like to get some users to try out the latest dev which is going to be version 6.x-1.3 of the module. You will need to run update once you have the new module code installed.

Once the DB update as been run, visit the settings page for the module and assuming that you have og and og_access enabled, you will see the new OG settings.

Filedepot will now create a new Top Level 'Root' folder for groups when they are added and if you enable the option, the users group context will be detected and only folders and files under that group folder will be displayed.

Hi Blaine,

I installed the latest 6 dev version (dd 5 Feb 12) but don't see any difference compared to the previous dev version.
I run Commons, and have OG and OG access enabled.
I did run update.php; first without version selection. No OG settings showed up on site config/filedepot
No new folder was created upon creating a new group

Then ran update.php again, selecting the latest version 6002. Got the attached error messages.
No OG settings showed up on site config/filedepot
No new folder was created upon creating a new group

Blaine, can/shall we use this version along with this OA Feature or there will be a new Feature soon?

@jandekezel: what version of filedepot where you running because update 6002 is quite old (RC4 version). It may have been a timing issue before the updated 6.x-1.x-dev was generated but just checked now and it has the lasted committed code. Update 6301 is the update that needs to be run and adds a new field group_nid to the filedepot_categories table.

@charos: I would expect it to work but I've not done any testing with OA