First off, thank you for all the hard work on Storm. I have been using it for several years and am impressed with all the great work that the community has done and I have Storm running on two other instances of Drupal 6.22 running 6.x-2.x-dev, though they were brought up to 6.x-2.x-dev via an update from 6.x-1.36.
Now, the details of my..... problem:
The organizations drop down select menu does not populate with any organzation data when creating an Expense record ONLY.
The issue occurs when attempting to create an expense record via Storm dashboard, Project or Task nodes.
My environment
I am working with a fresh copy of Drupal 6.22.
I have replicated this issue with versions 6.x-1.36, 6.x-1.x-dev & 6.x-2.x-dev, each on clean installs of Drupal 6.22.
It is my intent to build my solution utilizing 6.x-2.x-dev
I believe the issue is permissions related, but I can not determine the cause. Your advice is GREATLY appreciated.
I have two organizations created:
- The Host Organization is designated "Customer", "Provider" and "Active". (I have also tried Customer only and Provider only).
- Client Organization designated as "Customer" & "Active" (I have also tried as "Customer" & "Provider")
I created two "person" records:
- OrgUser1: A member of the Host Organization and assigned to a role with all the Storm related modules access, add, edit & delete priviledges.
- ClientUser 2: A member of the Client Organization and assigned to a role with all the Storm related modules view of Client organziation, etc.
(If a complete listing of the assigned permissions matrix is required in order to properly debug the issue I will produce it. Please reply requesting the information.)
I created two "teams" records:
- Host Team (person record created referencing OrgUser1 is a member)
- Client Team (person record created referencing OrgUser1 is a member)
I have created four projects:
- 2 projects under the Host Organization: Assigned "OrgUser1" as both "Project Manager" and the "Assinged to" fields.
- 2 projects under the Client Organization: Assigned "OrgUser1" as "Project Manager" and "Client Team" as the "Assinged to" fields.
I am able to create Projects, Tasks, Tickets, Timetracking, Notes & Invoice records without issue - with the "Organization" drop down select lists populating properly as both user1 (the super user) as wall as the OrgUser1.. The organization drop down menu populates as designed.
Usage scenarios
- When attempting to create an expense record via the Storm Dashboard no organizations, projects or tickets populate in the drop down lists.
- When attempting to create an expense record from one of the active project, or task nodes there are no organizations available via the organizations drop down list, but both active projects are viewable/selectabe via the drop down list as well as the tasks created related to the projects. This holds true for both the host org projects and the client projects. In other words, the visible projectsand tasks on the drop down lists are associated with the organization they were created under, SO, it stands to reason there is some organization related visibility rules being passed to the node. This occurs while logged in as either User1 (the drupal super user) and OrgUser1.
I have performed the above test scenarios via all three versions of the Storm modules: 6.x-1.36, 6.x-1.x-dev & 6.x-2.x-dev, each on clean installs of Drupal 6.22 with the modules listed below installed (see list below).
Please let me know if you require any additional usage scenarios, screen shots, logs or configuration information.
Any insight into why the heck this is happening is greatly appreciated.
List of installed modules:
color
comment
dblog
filter
help
locale
menu
node
path
profile
search
statistics
syslog
system
taxonomy
tracker
trigger
update
upload
user
admin_menu
advanced_help
help_example
content
content_copy
content_multigroup
content_permissions
nodereference
number
optionwidgets
text
userreference
bulk_export
ctools
ctools_access_ruleset
ctools_ajax_sample
ctools_custom_content
ctools_plugin_example
stylizer
views_content
date
date_api
date_locale
date_popup
date_timezone
date_tools
filter_perms
image_attach
image_gallery
image_import
image
jquery_ui
module_filter
panels
panels_ipe
panels_mini
plugin_manager
skinr
storm
stormattribute
stormexpense
storminvoice
stormknowledgebase
stormnote
stormorganization
stormperson
stormproject
stormtask
stormteam
stormticket
stormtimetracking
tokenSTARTER
token_actions
views_export
views_ui
actions_permissions
views_bulk_operations
pathauto
fieldgroup
token
views
panels_node
page_manager
jquery_update
Comments
Comment #1
CirruZZ commentedI can confirm the above mentioned problem. I'm on Drupal 6.22 and Storm 6.x-2.x-dev (2011-May-19). Installed modules (except Storm) are
Administration menu 6.x-1.8
Masquerade 6.x-1.6
Secure Site 6.x-2.4
I earlier tested Storm on a old "sandbox"- installation I had, so I checked if the issue was present there also, but that sandbox didn't have the same issue, the only difference is that there the Drupal core is 6.13.
Comment #2
juliangb commentedReclassifying as a bug (haven't confirmed myself though).
Comment #3
ibartol commentedSince you can't use Expense until its fixed, here is a little "way around" (read: disabling the required field).
edit following file: stormexpense.module
what to edit: line 374
from '#required' => true,
to '#required' => false,
As long as you use Storm for only 1 organization, this should work perfect, since the "Organization" part in the storm/expenses will automatically be filled with your organizations name.
Hopefully it'll be fixed soon or with next stable release :)
Comment #4
kfritscheI did a quick look into the code. Looks fine to me.
Then I created a sandbox after your good description :)
Even this works for me as OrgUser1 with ClientProject and HostProject.
Whats wonders me is that this even happens to user1, because he should have access to everything.
I'm using the latest storm 2.x dev from the repository, which is the same as the dev 2011-Aug-20 from drupal.org
Please report the permission matrix for the host role, best would be the perm string from the drupal {permission} table (so i can add this string quickly to my environment)
You could try to comment the line 357 and 358 in the stormexpense.module, this should fix it, when there is something wrong with the permissions: (all users have should then select all organizations)
Comment #5
ibartol commentedhm, for now ill just post the perm string (find in attach) . still havent tried commenting the lines, but will do it in the next few days... kinda busy month :)
edit:
i just had to try it out :) but, it didnt turn out great... once i've commented it, i couldnt list out organizations and projects .. once i returned it to original form (without comments), i just got a list of expenses which didnt have nor an organization nor a dedicated project ...
Comment #6
kfritscheIn the picture is only the table structure, but not the permission. Please click on view and then on edit by the entries, then you can copy the content of perm. Do not copy the string from the table view, because it is cut after some characters.
To the other Problem, is it still present? It should be working if you reset the filter.
Comment #7
juliangb commentedNo response since Sept. @kfritsche previously said he couldn't reproduce the problem.