I have set permissions to allow only a certain group to read the locations module output.
Controllers || locations:: || .* || Read access
I've also tried it as:
Controllers || locations:: || :: || Read access
The problem is that the Controllers group is only able to see the locations data, not the map. Otherwise the permissions rule is working fine.
Any help would be appreciated.
Thanks!
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
- rgasch created topic »Using PageUtil::addVar() to load script code« 11:48 AM
- michiel responded to »password problem« 10:01 AM
- mazdev responded to »Hide "Register new account" and change template to 3 col« 07:50 AM
- mesteele101 created topic »Zikula 1.3.3 - Site Search 1.5.2 - Unable to turn off plug-ins« 07:48 AM
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
locations module and permissions problem
-
- Rank: Registered User
- Registered: Apr 03, 2010
- Last visit: May 11, 2010
- Posts: 16
-
- Rank: Developer
- Registered: Feb 17, 2005
- Last visit: May 21, 2010
- Posts: 684
I have no experience with the locations module but I might have a few tips:
- The first option look correct, the second one not.
- If, in the 'Permission rules manager', you click 'Permission rules information' you get an overview of the various permissions per module. You can check the permissions available for the locations module.
If you don't come right please post your complete permission rules here. -
- Rank: Developer
- Registered: Feb 17, 2005
- Last visit: May 21, 2010
- Posts: 684
I checked: the locations module has a very simple permission schme.
Code
$modversion['securityschema'] = array('locations::' => '::',
'locations:Location:' => 'LocationID::');
If you don't see the map there is perhaps a problem with the Google maps key. Have you checked if there are any JavaScript errors? -
- Rank: Registered User
- Registered: Apr 03, 2010
- Last visit: May 11, 2010
- Posts: 16
Hello dits... thanks for your response.
I had checked in the 'Permission rules information' and that is where I got the :: rather than .*
In the past, with older versions of Zikula I had always used .* but this latest install (v1.2.2) referred to :: in the "Permission rules information". In any case, neither worked to solve my problem.
Here is what I have:
Controllers | locations:: | .* | Read Access
All groups | locations:: | .* | No Access
The Controllers group IS able to see the locations module data which gives name, address, phone number, etc. However, they are not seeing the map. So only one part of that module is showing up after applying the permissions rules.
The map itself DOES work for the admin, so my Google maps key and all that is functioning correctly, it's just when I apply some permissions to it does it not work.
The locations module also had crpTag listed as a recommended dependancy...but as I went to go double check the dependances, I see that that in the couple of weeks I've been away from this, there are two more versions of "locations"!
I'll upgrade and then see where I'm at. I'm using 1.1.0 and in the next version (2.0.0) it says it fixed permission issues, there's a version 2.0.1 even after that...so maybe I'm in luck.
I'll post my results here.
Thanks for your help!
Anita -
- Rank: Registered User
- Registered: Apr 03, 2010
- Last visit: May 11, 2010
- Posts: 16
Ok, upgrading is becoming a problem. How do I upgrade from v1.1.0? I didn't see any documentation on how to do so.
What I did was backed up my data, disabled and removed v1.1.0. Installed v2.0.1, dumped my previous data back in which gave me a column count/value count error.
So then I uninstalled v2.0.1 thinking I should have upgraded from v1.1.0 to 2.0.0 first in the hopes that following the module's natural version progression would eliminate my difficulties, or rather, make the necessary changes to the database.
So I reinstalled v1.1.0, dumped my data back in, then removed the v1.1.0 files, put in its place v2.0.0, went to the modules admin panel and regenerated the list hoping to see it say "upgrade" or something, but nothing changed and the version still said 1.1.0 and I'm still out of luck and getting quite frustrated.
I have quite a lot of data and don't want to have to add all that in again manually with a new clean install of 2.0.1.
I don't know what I'm doing wrong.
Thanks,
Anita -
- Rank: Registered User
- Registered: Apr 03, 2010
- Last visit: May 11, 2010
- Posts: 16
wow, ok, that was stupid. Complete user mess-up.
Everything is good, locations works beautifully, upgrade went without a hitch and now it's working completely (data AND map!) with permissions applied to it.
My dumb mistake was that it wasn't the 2.0.0 module I had unzipped but the 1.1.0 again. So after doing 2.0.0 I went to 2.0.1 seamlessly and everything is perfect.
Thanks for helping and sorry for the dumb mistake! -
- Rank: Team Member
- Registered: Jul 15, 2004
- Last visit: May 27, 2010
- Posts: 277
- Moderated by:
- Support
