this module is a nice addition to Drupal's default log stats, it would be also nice if settings options to limit what site 'roles' can view what stat types
also extention of the summary block that what other stat/log type summaries also the block may include
thanks for the module
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | drupal-xstats-settings-perm.png | 8.97 KB | ica |
Comments
Comment #1
Bèr Kessels commentedxstatstistics only has power over the permissions of the pages it makes itself. So we cannot introduce permissions for Drupals core stats pages.
Can you make a list with what you'd like permissions for?
Comment #2
ica commentedActually, good question , i should define better,
What actually I mean is
just for the cases to hide 'admin' access logs from other roles i.e default authenticated user or/and anonymous use and customised 'Editors' role similar to block can be hide from other users i.e Who is online block
thanks for your reply
Comment #3
Bèr Kessels commentedI guess its because of the English, but I really don't get what you are asking.
Can you not come up with an actual case? So that I can read the examples you provide and define a real feature request from that?
Comment #4
ica commentedHi Ber, to clarify and revisit my point i have put the idea to a visual mock up attached
basically to give a user view permission for each stat type
currently it can be done customised blocks for each individual stat type to a block and give user permission to each block by picking up the individual $count_'s for each stat item and putting it a block
http://mydrupal.com/display_useful_site_statistics_combine_site_summary_...
but i though it would be also done better with a Xstatistics user permission settings addition to your module - something like on the attached mockup screenshot
thanks
Comment #5
duaelfrThis version of Xstatistics is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.