Re: [development] development Digest, Vol 88, Issue 36
I think you'd do it with a hook_form_alter... set maxlength in the hook based on your roles. On 28/04/2010 10:00 PM, development-request@drupal.org wrote:
Message: 1 Date: Tue, 27 Apr 2010 09:49:01 -0600 From: Karyn Cassio<karyn@karyncassio.com> Subject: [development] Character limit on body textarea To:development@drupal.org Message-ID:<4BD7076D.90404@karyncassio.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Good day Drupal Devs,
I have an issue where I need to set a character limit on a content's body_field. I found maxlength, which is great, unfortunately it isn't everything I need since this is a per role situation. Some roles would have a limit, others unlimited.
Has anyone successfully been able to apply an alter to the maxlength module to have it work for specific roles only?
Thanks,
-- Karyn
I'm going to be writing an OG analytics package for a medium sized non- profit and contributing it back to the community, and would like some guidance on specific technologies. First, some background. The site traffic is almost entirely OG-based and requires a login to access. There are a few dozen public pages as well. Other than a lot of custom content types, the OG install is similar to GDO. The site is currently D5, with plans to upgrade to D7 in the fall (yes, I realize D5 is going to be a lot of extra work). The goal priorities are (in descending order of importance): * Capable of providing the needed metrics * Quality reports and graphing * Expandable with later module integrations (not just OG) * Scalable * Reasonably installable * Compatible with shared hosting (requiring SSH access is probably fine) Metrics desired: * Session length * Nodes viewed (aggregated by content type) * Searches made (query and number of results returned) * Eventually also taxonomy integration Each would be stored with uids, and each Group would provide an aggregate total based on group membership. In addition to data collection and processing, I'm also going to need a reporting framework that will provide results as HTML and CSV export of table results (one day resolution). There have been many posts on the subject, but nothing that provides an obvious starting point: * http://groups.drupal.org/node/20452 * http://groups.drupal.org/node/20889 * http://groups.drupal.org/node/21563 * http://drupal.org/project/nagios The underlying technologies I've seen thrown around are Google Analytics, Cacti, Munin, RRDtool, and Nagios. Open source is desirable but not at the expense of critical features. If anyone can provide guidance about approaches or eliminate some of the technologies, it would be greatly appreciated. I want to avoid a solution that is great for a small number of people but won't ever reach wide adoption. Thanks, -------------------------------------------------------------------------------------------- Ken Winters Coalmarch Productions LLC
The underlying technologies I've seen thrown around are Google Analytics, Cacti, Munin, RRDtool, and Nagios. Open source is desirable but not at the expense of critical features.
I don't know much about this, but I can at least add another OS tool to consider: http://piwik.org/ that we use for one site. HTH
On Apr 28, 2010, at 11:23 AM, Fred Jones wrote:
The underlying technologies I've seen thrown around are Google Analytics, Cacti, Munin, RRDtool, and Nagios. Open source is desirable but not at the expense of critical features.
I don't know much about this, but I can at least add another OS tool to consider:
that we use for one site.
HTH
That one seems to have promise. It's more oriented towards GA-type stats than server load. - Ken Winters
Fred Jones wrote:
The underlying technologies I've seen thrown around are Google Analytics, Cacti, Munin, RRDtool, and Nagios. Open source is desirable but not at the expense of critical features.
I don't know much about this, but I can at least add another OS tool to consider:
I've used it but prefer http://awstats.org since it is server log driven rather than JavaScript driven. The less JS the better. -- Earnie -- http://progw.com -- http://www.for-my-kids.com
I think the most straightforward thing to do would be to use Google Analytics. It has an API now (and Drupal module<http://drupal.org/project/google_analytics_api>) that you could use to pull in data and build custom reports. The biggest downside I know is that you're prohibited per terms of use on tracking individual users so all data is aggregate. --Kyle Mathews kyle.mathews2000.com/blog http://twitter.com/kylemathews On Wed, Apr 28, 2010 at 8:53 AM, Ken Winters <kwinters@coalmarch.com> wrote:
I'm going to be writing an OG analytics package for a medium sized non-profit and contributing it back to the community, and would like some guidance on specific technologies.
First, some background. The site traffic is almost entirely OG-based and requires a login to access. There are a few dozen public pages as well. Other than a lot of custom content types, the OG install is similar to GDO. The site is currently D5, with plans to upgrade to D7 in the fall (yes, I realize D5 is going to be a lot of extra work).
The goal priorities are (in descending order of importance):
* Capable of providing the needed metrics * Quality reports and graphing * Expandable with later module integrations (not just OG) * Scalable * Reasonably installable * Compatible with shared hosting (requiring SSH access is probably fine)
Metrics desired:
* Session length * Nodes viewed (aggregated by content type) * Searches made (query and number of results returned) * Eventually also taxonomy integration
Each would be stored with uids, and each Group would provide an aggregate total based on group membership.
In addition to data collection and processing, I'm also going to need a reporting framework that will provide results as HTML and CSV export of table results (one day resolution).
There have been many posts on the subject, but nothing that provides an obvious starting point:
* http://groups.drupal.org/node/20452 * http://groups.drupal.org/node/20889 * http://groups.drupal.org/node/21563 * http://drupal.org/project/nagios
The underlying technologies I've seen thrown around are Google Analytics, Cacti, Munin, RRDtool, and Nagios. Open source is desirable but not at the expense of critical features.
If anyone can provide guidance about approaches or eliminate some of the technologies, it would be greatly appreciated. I want to avoid a solution that is great for a small number of people but won't ever reach wide adoption.
Thanks,
--------------------------------------------------------------------------------------------
Ken Winters Coalmarch Productions LLC
I think the most straightforward thing to do would be to use Google Analytics. It has an API now (and Drupal module) that you could use to pull in data and build custom reports. The biggest downside I know is that you're prohibited per terms of use on tracking individual users so all data is aggregate.
Does anyone else really NOT want to use GA just because you don't want to give Google even more information about your business? Or is it just me? Fred
+1 to this. I've been gradually getting more uncomfortable with the amount of data google posesses about me, both business-wise and personally. I would love to see non-Google implementations.
This now off topic, but we already knew that you agree with me, Bryan. See this article: "Google even knows what you're thinking": http://blogs.zdnet.com/security/?p=6291 Fred
On Apr 28, 2010, at 11:35 AM, Brian Vuyk wrote:
Fred Jones wrote:
I think the most straightforward thing to do would be to use Google Analytics. It has an API now (and Drupal module) that you could use to pull in data and build custom reports. The biggest downside I know is that you're prohibited per terms of use on tracking individual users so all data is aggregate.
Does anyone else really NOT want to use GA just because you don't want to give Google even more information about your business? Or is it just me?
Fred
+1 to this. I've been gradually getting more uncomfortable with the amount of data google posesses about me, both business-wise and personally. I would love to see non-Google implementations.
In this particular case, the connection between uid and any other personal information shouldn't really be accessible by Google, so I don't see it as a major stumbling block. However, there are other reasons I'd like to avoid GA if there is a reasonable open source alternative. My biggest concern is that I won't be able to accomplish my goals because of some arbitrary restriction put in place by Google, or otherwise being at the whim of what they're willing to provide in the API. There is also the issue of data ownership, and the difficulty in retrieving your data from a proprietary system. - Ken Winters
participants (6)
-
Anth -
Brian Vuyk -
Earnie Boyd -
Fred Jones -
Ken Winters -
Kyle Mathews