Location. Cck. Permalink. What is a "permalink"?
Wikipedia defines permalink as: A permalink, or permanent link, is a URL that points to a specific blog or forum entry after it has passed from the front page to the archives. Because a permalink remains unchanged indefinitely, it is less susceptible to link rot. Most modern weblogging and content-syndication software systems support such links. Other types of websites use permanent links, but the term permalink is most common within the blogosphere. This module allows you to add a permalink to any node type. Features of the Permalink module Drupal 6.x version The 6.x branch of Permalink includes a number of new features.
I started off with the GeoUser module - this had all of the required operability with MaxMind's GeoLite City database . The GeoUser module has the ability to look up the user's location whenever they login, then display the location on the user's profile page. $thelocation = GeoUser::getGeoCity(ip_address()); CDN integration. Support this module by tipping on Gittip!
This module provides easy Content Delivery Network integration for Drupal sites. It alters file URLs, so that files are downloaded from a CDN instead of your web server. It provides two modes: "Origin Pull" and "File Conveyor". In Origin Pull mode, only "Origin Pull" CDNs are supported. (These are CDNs that only require you to replace the domain name with another domain name.)In File Conveyor mode, this module integrates with File Conveyor, which allows for much more advanced setups (e.g. optimize images, transcode videos, and so on, before syncing to the CDN). Note: It is essential that you understand the key properties of a CDN, most importantly the differences between an Origin Pull CDN and a Push CDN. The CDN module aims to do only one thing and do it well: altering URLs to point to files on CDNs.It does as much as possible to make CDN integration frictionless & performant: Any sort of CDN mapping!
Live sites History. Facebook Connect. Newsletter Module For Drupal. I’ve had a few clients ask me recently for newsletter functionality in their Drupal theme that I am building out for them.
So that got me started on some research that took me a few hours before I finally came across a solution I could work with. I was particularly looking for a Newsletter functionality that would allow users and anonymous users to sign up. Much of what I was originally finding had to do with registered users only able to sign up for the newsletter. But for many that defeats the purpose. Most sites need a newsletter that is easy for all visitors of the site to join. Permit own permissions. Permit own permissions provides a new permission, share permissions, and anyone given this permission can add or remove any permission she has from any role.
They will be able to access admin/people/permissions Problem: A site is beautifully set up and guards against catastrophic user error (blowing things up) while giving the person you made it for as much flexibility and power to add to it as is possible... almost. He can't change what permissions other roles have or even what roles another user has... unless you give him administer permissions. Now Mr. Before his assistants can use their delegated permissions, on the day of his Superbowl ad announcing the site he puts it into offline mode, the smiling blue Druplicon becomes that much more (in)famous, and he sues you for a half-million dollars.
Don't let this happen to you! Solution: Permit own permissions provides the share permissions permission, and the share permissions through roles. Activity Stream API. Scaling drupal step four - database segmentation using mysql pro. If you've setup a clustered drupal deployment (see scaling drupal step three - using heartbeat to implement a redundant load balancer), a good next-step, is to scale your database tier. in this article i discuss scaling the database tier up and out. i compare database optimization and different database clustering techniques. i go on to explore the idea of database segmentation as a possibility for moderate drupal scaling. as usual, my examples are for apache2, mysql5 and drupal5 on debian etch. see the scalability overview for related articles. deployment overview this table summaries the characteristics of this deployment choice servers in this example, i use: first steps first - optimizing your database and application.