Closed (fixed)
Project:
Marketplace
Version:
6.x-1.x-dev
Component:
Transactions
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
26 Jul 2009 at 22:47 UTC
Updated:
28 Aug 2009 at 17:13 UTC
I just installed dev and it shows on every screen this:
No roles have permission to start any transactions.
I looked at the permissions and there is no "Create transaction content" nor anything about starting transactions under the transactions section.
Comments
Comment #1
matslats commentedon admin/marketplace, name the transactions you want to use.
Each named transaction appears on the permissions page with it's machine name
e.g. start incoming_confirm etc
Each permitted transaction type will appear on the transaction form.
Comment #2
JoshSharp commentedI checked that there are names in for all of these. Nothing in permissions starting with "start" though. Also, I have noticed three new blank menu items in the create content menu. They point to nothing. I upgraded this to prod after deleting the module folder and untarring dev. Seems like something is amiss. I will try to totally uninstall it and reinstall it again.
Comment #3
JoshSharp commentedI have uninstalled the module and reinstalled it with the same problem coming up. On the mass payment form, there are no payees in the payee list.
Comment #4
JoshSharp commentedI'm digging all around the code and I found the problem. If you don't have permissions in the permissions table to the transaction types, they never show up on the permissions list to turn them on.
As I am not at all comfortable, nor even able to submit this to cvs I will post it here. I have included the original code and the changed code (with line numbers) and bolded the changes.
./transactions.module
Original:
With Changes: (In line 215, sent TRUE as parameter)
Original:
With Changes: (In line 876, added showall parameter and line 888, added bool logic to show all if asked)
Let me know what you think.
Comment #5
JoshSharp commentedOne other thing to note. I was not logged in as root, but as my ID and am using the "Admin Role" module to assign admin rights to an "Administrator Role". If I had been root, it would have probably worked without the change.
Comment #6
matslats commentedSorry josh, for not getting to this sooner, it was a bit messy!
I have fixed it in a different way. There are now 2 functions,
_permitted_transaction_types()
and
_named_transaction_types()
Comment #7
matslats commentedYes and this mistake could only happen if you were developing not as admin