CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Version 4.3.0 - a few cosmetic issues
Pages: 1 [2]

Author Topic: Version 4.3.0 - a few cosmetic issues  (Read 1950 times)

SarahG (FountainTribe)

  • Ask me questions
  • ****
  • Posts: 782
  • Karma: 29
  • CiviCRM version: 4.4.7
  • CMS version: Drupal 6, Drupal 7
  • MySQL version: 5.5
  • PHP version: 5.3
Re: Version 4.3.0 - a few cosmetic issues
April 18, 2013, 09:16:18 pm
If you really want to make sure the most people see the "community message/gimme money" message, you could add it to the default report footer for any exported/scheduled report.   I know of many situations where the people who control the wallet of the organization never login to CiviCRM directly, instead they get scheduled reports in their mailbox or they get a report prepared by a low-level staff person.
Did I help you? Please donate to the Civi-Make-It-Happen campaign  CiviCRM for mobile devices! 

Aahar

  • I post occasionally
  • **
  • Posts: 79
  • Karma: 3
  • CiviCRM version: 3.4 and 4.0
  • CMS version: Drupal 6.17, 6.x and Drupal 7.x
  • PHP version: 5.2
Re: Version 4.3.0 - a few cosmetic issues
April 26, 2013, 01:47:46 am
A little different question:
Is there a way in which I can configure availability of "Civicrm News" dashlet? I would want it to be available to some users and not available to others.

Mark Tompsett

  • I post frequently
  • ***
  • Posts: 143
  • Karma: 9
    • QualityTime Services Ltd
  • CiviCRM version: 4.3.4
  • CMS version: Drupal 7.22
  • MySQL version: 5.5.30-cll
  • PHP version: 5.3.23
Re: Version 4.3.0 - a few cosmetic issues
April 26, 2013, 02:21:38 am
Do you mean by permissioning it to so that some users have access to it but others do not?  If the dashlet was creaetd from a Report then I reckon you could do it that way, but I don't think this dashlet was creaetd from a report so I doubt that it is possible to control access by permissions.

The only other way that you could control who sees it and who doesn't I guess would be by fiddling around with the civicrm_dashboard_contact table in the database which seems to control which contacts have wghich dashlets in their dashboard (and in which column, etc).

Hope that helps?
Mark

Pages: 1 [2]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Version 4.3.0 - a few cosmetic issues

This forum was archived on 2017-11-26.