I've been working on a Storm helper module dubbed "Storm User Link" over the past month or so.

Dependencies:
storm [duh], stormattribute, stormorganization, stormperson, profile, user [duh++]

I've finally finished a fairly rough merge with the latest 6.x-1.x-dev version off CVS which I'm marking as alpha2. I really need to do some more testing so will update this issue once I've tested it more thoroughly. :) I've only tested this on drupal 6.13.

Have attached:

* a .patch against the latest 6.x-1.x-dev version from CVS
* a zipfile containing just the stormuserlink subdirectory (which goes under the modules/storm directory of course, like a good little helper module!)
* will try to upload a prepatched 6.x-1.x-dev version but drupal.org is giving me grief!

Here's what it does: (but your mileage may vary :P)

* Adds an option to the Storm admin settings tab to let the user rename all instances of the word "Storm" to something else. (in my case, "Helpdesk"). At the moment not all instances of Storm are replaced, and there's certain areas where I think the word Storm should never be replaced (ie. module page of course), but that's another story.

* Adds an option to Storm admin settings tab to make filter options always expanded or collapsed by default. (not sure if something like this has been done already, or if it's even needed)

* Adds more detail to the vanilla Drupal User List (admin/user/user/list) page. The filter now includes "stormlink" > yes or no, and the Update Options includes two extra options: "Link to Helpdesk/Storm Person" and "Unlink from Helpdesk/Storm Person" which can be applied to whoever is ticked in the user list.

* In the admin page for Storm User Link there's options to map User fields to Storm fields.

There's still a long way to go to ensure the module works flawlessly. Feel free to post feedback on this Issue with any errors/problems you encounter.

Thanks,

anodyne.

P.S. To install on the latest 6.x-1.x-dev from CVS, you'll need to apply the patch to the latest CVS and then create a "stormuserlink" folder underneath the main storm folder and put the files from the zipfile inside. Or you can just unpack the ~400kb zipfile I've attached, upload it to your modules folder and install the easy way. :P

CommentFileSizeAuthor
#5 storm-6.x-1.x-dev-userlink-alpha2-unix_line_endings.patch66.01 KBanodyne
#1 storm-6.x-1.x-dev-with-userlink-alpha2a.zip355.65 KBanodyne
stormuserlink-6.x-1.x-dev-alpha2.zip63.7 KBanodyne
storm-6.x-1.x-dev-userlink-alpha2.patch67.72 KBanodyne

Comments

anodyne’s picture

anodyne commented
StatusFileSize
new storm-6.x-1.x-dev-with-userlink-alpha2a.zip355.65 KB

Here's the full zipfile with storm+userlink for anyone who wants to give it a shot.

juliangb’s picture

juliangb commented
Status: Active » Needs review

Hi @anodyne,

Setting CNR so that the testbot looks at the patch.

Thanks for posting this code. However, it looks like (at least from the patch) that there are multiple changes here, not just for the userlink functionality. Therefore, it is going to be hard to review this, simply because we'll be talking about several topics at once.

Could I encourage you to post some of the changes as distinct issues / patches? I think that way, we're more likely to be able to properly review.

Thanks.

Status: Needs review » Needs work

The last submitted patch, storm-6.x-1.x-dev-userlink-alpha2.patch, failed testing.

anodyne’s picture

anodyne commented

Hi Julian,

You're right - but I have no idea how to split the patch up into functionally discrete pieces! (any ideas for a n00b?)

Essentially the changes can be broken down into:
- Aesthetic: Changing all references to "Storm" to an admin-provided string throughout all modules in the suite
- Usability: Make all filter fieldgroups expanded or collapsed by default (this needs to be discussed more)
- Visibility: Ability for the admin to hide/show certain fields [see Note #1 below]
- Userlink: The meat and potatoes of the userlink module, confined to the /userlink subfolder.

So I'll list the above as separate issues and try to submit incremental patches for each so they can be reviewed individually.

Please bear with me! Thanks.

[Note #1]:
I'm currently in the process of working on changes to most of the modules that would give admins greater control over field visibility for each storm object type from the storm settings area.

anodyne’s picture

anodyne commented
StatusFileSize
new storm-6.x-1.x-dev-userlink-alpha2-unix_line_endings.patch66.01 KB
juliangb’s picture

juliangb commented
Status: Needs work » Needs review

CNR for bot to look at #5.

juliangb’s picture

juliangb commented
Status: Needs review » Needs work

Needs the stuff covered by #744694: Cosmetic: Give admin ability to rename Storm in UI to something else more appropriate taken out of this patch here.

JGonzalez’s picture

JGonzalez commented

Subscribed to this. Ability to link users would help with workflow nicely.

Some possible settings for storm admin on this:
Link by default?
Link by role? (select roles which need to be also storm persons)

any other options for linking users?

JGonzalez’s picture

JGonzalez commented

Cross-reference with: #659924: Add options for dynamically adding drupal users for storm persons (and vice versa)

I knew this thread looked familiar.

bunset-temp’s picture

bunset-temp commented

subscribing

juliangb’s picture

juliangb commented
Status: Needs work » Closed (won't fix)

This is an old issue, and I think the way that we'll be handling this going forward is to merge Storm Persons with Drupal Users.

This will prevent needing workarounds like this - and will be conceptually simpler.