Storm with Open Atrium

Good question - it should be though. Open Atrium is really just an installation profile - a way of installing Drupal so that certain modules are enabled by default etc.

You should be able to upload and enable the module as normal and tweak to put Storm on the menus etc.

Caveat - I haven't tried it myself - please report back once you (or anyone else) have had a go.

Closing since no responses - but I'm guessing this is something which would be useful to some people, so if anyone does get it working successfully, please post back.

https://community.openatrium.com/issues/node/337#comment-1947

I've created a STORM feature inside OpenAtrium. See the links above.

Next step, learn how to create a feature server.

My integration in STORM might not be perfect, but it should work correctly for our new client OpenAtrium installation.

Question: Can I post my STORM feature files here?

That's great news.

I'd be happy for you to post the files here or on the OA site - and we can link to it on the project page (issues will get lost over time).

Here we go. This is the feature I made while playing with OpenAtrium.

This feature is generated through OpenAtrium and modified manually to add an icon.

Disclaimer: I am new to Context and Feature. Please test before using on a production OA site.

@Magnity: Maybe you could create a feature server instead of just linking to this file. :-)

That would require me learning how to create a feature server too ;-)

Pending the feature being made available elsewhere, I have linked to #5 from the Storm project page. This issue will be lost in the queue otherwise.

Closing the issue, but reopen if you feel you have more to add to this topic.

Looks like there is a community feature server now:
http://featureservers.org/

You should be able to upload it there. I'd do it myself but I've never used the Storm module and don't want to mislead people who are looking for support.

The feature server there doesn't seem to have taken off - however, I'm happy if anyone wants to take it and put it anywhere. Closing this issue again as it isn't a current issue.

Open Atrium beta 3 -> beta 4 upgraded from Spaces 2.x to 3.x. Spaces 3.x no longer enforces access control via a group space. (https://community.openatrium.com/documentation-en/node/1527). Custom features can control access through Views access settings which Storm doesn't seem to use. I haven't figured out the best way to control access. Right now in beta 4-6, any space can see all data for the site and groups can't toggle the feature on or off. Any feedback would be helpful. Thanks.

I have not update any OpenAtrium/STORM site to Open Atrium beta 4 yet. This is an interesting issue!

Does that mean that STORM must now be Spaces aware?

Looks like this is the solution with the change in the way Spaces 3.x handles access control. http://drupal.org/node/770556. I'll see if I can get it working with Storm.

Subscribing...

Suscribing.

Cool! I'm interested in this module too to get it working on OA beta6... Subscribing!

Subscribing..

subscribing...

Subscribing.

subscribing…

subscribing…

subscribing…

Note to all subscribing - the open atrium integration is not something which is part of Storm itself, and is not maintained as the main project is (basically - please do not get annoyed when I do not work on this). All open atrium integration has been contributed via this issue.

Actually, as mentionned in comment #10 and @12, Storm is not Spaces aware.

In other words, access control will fail with OpenAtrium and or Spaces.

As with any modules generating menu items, Storm must be updated to include a spaces_access_feature() in its menu items.

See : http://drupal.org/node/770556

Is this something that can be added to Storm?

subscribing

Subscribing.

If a patch is provided with suitable reviews... it will be added.

subscribing

Subscribing.

I'll roll a patch for Spaces access, still on the bottom of my todo list.

subscribing

subscribing

Ok, I was able to get Storm to be Spaces aware with Open Atrium beta 8. However, it required patching storm.module and storm.info. Some items can be put into a separate "feature" module with hook_menu_alter() so as not to affect Storm for users who aren't using Spaces. The Storm "feature" now toggles on and off per group with the proper PURL but the content is still viewable across all groups. I'm still looking at possible solutions to this issue.

@brentratliff: Would you like to publish your patches here? Maybe others will be able to enhance it and maybe obtain a spaces-aware Storm module.

Patches are here but don't really do anything other than allow the PURL to work for each group space and toggle the feature on and off. The content still doesn't have proper permissions per space.

By making all the Storm content types group posts, the content now shows up properly for each group space with the above patches since og directs spaces access. There is still an issue with users that are members of multiple groups able to see all their groups' content regardless of which group space they are actively viewing but it's usable if all your members are in only one group. I think the answer can either be using the spaces_get_space() check or through the current space views plugin since Storm does define views in code. The patches do alter Storm directly and are only for testing. Ideally, no patches to Storm will be required and a separate submodule can be created using hook_menu_alter.

Ok, I need testers. Install this feature as you would normally after placing it in /sites/all/modules/custom_features/ and enable it via /admin/build/features. In each group, you will see Storm as an option for 'Customize Features.' Also, you will need to add the following lines of code to the storm.info file:

features[menu][] = "storm"
spaces[types][] = "og"

This is not ideal as a member of multiple groups will see all his/her storm nodes under every group. We should be able to get around this by using the 'current space' views plugin since Storm uses views in code. Also, the feature alters the Storm menu via hook_menu_alter so the Storm module .info file has to be manually edited. Obviously this is not ideal, but maybe a good start and functional for simple uses.

I did not include Storm permissions in the feature via Strongarm because I didn't want to make too many assumptions. You will need to give authenticated users permission to use Storm.

Hi brentratliff,

I've been trying your file to integrate Storm with OpenAtrium (I'd never tried Storm before), and I can say it is quite working well... However, isn't it duplicating most of OpenAtrium's functionality? I mean, Projects, tasks, knowledge base etc. are features OpenAtrium already has. I think maybe working to integrate timetracking (http://drupal.org/project/bubbletimer), invoicing (http://drupal.org/project/invoice)... modules into OpenAtrium would be a more effective approach...?

I'm just asking, because as I said I had never before tried Storm. Do you see the utility in adding this Storm "feature" to OpenAtrium? I'd be glad to know!

Cheers,

Miren

@mberasategi,

I think that people wish to use the Storm framework because they are familiar with it and prefer it to the native Open Atrium / casetracker implementation.

The feature is not intended for adding to the Open Atrium build, just for people who want to use it to add it themselves.

Didn't play too much with it but it seems to work as expected.Great!! If I could add something to the wishlist, that would be to have the option to enable/disable Storm modules. Currently for the Storm Feature to work , all Storm modules are required. However people might want to use only Expenses,Projects,People, Organazation and don't want to use Ticket,Note,Timetracking,Knowledge Base. It would be nice to toggle on/off only required addons to avoid confusion to end users for things not used (duplicate usage from OA Features).

charos,

You can manually edit the atrium_storm.info file and remove the dependencies for the submodules you don't want to use. Just delete or comment out the lines you don't need; (ex. dependencies[] = "stormticket"). I included them all so that I could set the associated content types as og group posts in order for the permissions to work properly. Let me know if it works.

@mberasategi,

Currently, I don't use Storm with OpenAtrium, but I know many people wanted it and I wanted to see if I could get it working and learn the Spaces API and paradigm at the same time. Personally, I use OpenAtrium with the YATT module for timetracking but Storm is really a different product that is very well suited for other situations. Some like to use the core OpenAtrium features and cherrypick a few Storm submodules as well. Also, Storm is a little more robust but more inclined for a non-og, non Spaces intranet. I guess it just depends on what you're looking for in terms of your workflow. Although I don't use them together, hopefully someone will find it useful.

@brentratliff

Did that already , but still Tasks & Issues appear in the Storm dashboard. I guess Attributes is creating these content types or maybe something else I am not aware of.

Subscribing

subscribing

Hello,
I install the atrium_storm.zip
but when I try to enable it via /admin/build/features it is off (painted in gray) and I can't enable it, the same happens in /admin/build/modules
What I can do?

#36 This works just fine. I'm experimenting with it. So far so good.

Hello,

I am working with Open Atrium. I am pretending to use the Case Tracker as a workflow I need that:

A user send a case to another user or department, and only the users involved will be able to watch it.

I am thinking that; I have a group for each workflow, for example "room request", I add to his group all the user who can request a room and the respective deparment of this workflow.
When a user want to make a room request, open a case which only should be visible to the person who the case is assigned; "rooms deparment" and the user who make it.

Thus the user will be able to watch all the cases he make, and the "room deparment" will be able to watch all the cases of all the users for "room request" and only this.

Actually all users of a group could watch all the cases opened, this is my problem, I need that only users will watch the cases which they are involved.

I think to make a group for each pair of deparment-user, but I need workflows in wich many deparments are involved, and a search for cases of the same workflow type, (using this option I would have search cases for users, and I need for type), so this is no a solution.

I ask if there is any solution for it, with rules, permission, organic groups... or if I could do this with Storm and how...

subscribing

subscribing

subscribing

subscribing

subscribing

sub

subscribing,
And where to get the newest integrated package?

Subscribe

Hi all,

I've previously left this thread open to allow members of the community to share code etc.

Since it has been a long time since that last happened, I think it is time to close this off.