Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
This is the first release of the daily twitter module. It's entirely possible that it would work with Drupal 5.x, but I have not tested it with that. If you test it with Drupal 5.x, it works, and you would like me to support it, just let me know and I'll set up something where i can test it easily. (in other words, I'm looking for "demand" for it under 5.x before I support it ;) ) Anyway, please let me know of any issues you run into and anything you'd like to see out of the module!
- #255375 by Dave Reid: fix Gravatar default picture url if default user picture is a relative url
- Coding standard fixes (no trailing spaces or blank lines with spaces) and bringing core hooks in line with core standards
- Removing package detail from .info file. Since we're not a huge module-set like Views, CCK, etc., Gravatar should not specify a module package.
- Followup for #255375: Don't use url() to create absolute url for default user picture.
- Don't validate e-mail in _gravatar_get_gravatar. It is unnecessary since e-mails are already validated before they get to this function call.
- Simplify admin settings, collapse into one settings page. Merge gravatar_imagedefault and gravatar_default_type setting.
- Coding style cleanups (we now pass all Coder checks! yay!)
- Removed constant GRAVATAR_SERVICEURL. Best used a variable.
- Major simplification to gravatar_get_gravatar()
- Removed _gravatar_translate_type and added _gravatar_get_default_image() for better code re-use
- Major overhaul to gravatar_preprocess_user_picture
- Remove '0' option from maturity filter option.
- Replace variable_get calls with gravatar_var.
- Fix discrepancy between gravatar_displayrating and gravatar_imagerating
- Change default display rating to 'G' (same as Gravatar.com)
- Change default image size to 80 (same as Gravatar.com)
This is a relatively simple module being used in production on at least one site, but lacks a README.txt file.
Note also that this is a completely new version of the user_quota module. People interested in the way that the user_quota module used to work should visit the project page to find alternatives.
Share drupal block setting with all installed and active themes
1. “Fixed” blockregion options selector position in Administer > Site building > Blocks page
2. The module now tries to guess where the block is most likely to be set in other thems (eg: “left section” matches to “Left Sidebar 1″ more than “Footer”)
3. Right or not, the module makes its choiche and places the block. You still can edit its position manually from the same admin page, after switching to the problematic theme.