Yesterday, October 15, Drupal 7.32 was released, addressing a critical security flaw in Drupal 7 core. This flaw was as critical as it gets: it allowed anyone to do almost anything on almost any Drupal 7 site. There were no known exploits running before yesterday, but by this morning automated scripts were peppering the internet with attacks meant for Drupal 7 sites.
Doing some review of D7 code today, detailing how the primary links are made and how they can be altered in modules or themes.
Media module is a popular tool for embedding video from providers like YouTube and Vimeo on a Drupal 7 site, and it works like a charm when people come to your site to view those videos. However, if you want your visitors to be able to share your pages on social networks with the appropriate images and video players, it's a little tricky.
A few years back, when Drupal 6 was gearing up for showtime, one of the major working points was making the install profile system easier to navigate for developers. A Drupal install profile, also known as a distribution, allows you to specify an initial setup for Drupal, including both core and contributed modules, and setting up configurations for them.
Today there is a new release of the Community Website Incubator, and lots of new features made it into this version! After your site is updated, you'll enjoy the following benefits:
If you enable the "Social integration" module, you'll now have the web's ubiquitous social sharing buttons, including Facebook's "like" button, Twitter share, and Google +1.
We're very happy to announce some major new features for the Incubator install profile. These features should be available to all sites using versions 1.0-beta17 and up.
You can enable the "Private Content" module by going to the "Modules" page in the administrative toolbar.
Once it's enabled, you will see a new checkbox on the form whenever you create or edit content entitled "Make this content private". Selecting that option will restrict access to that piece of content across your entire site.
Maintaining install profiles I am constantly having to maintain drush make files of contributed modules. Drupal.org used to display which modules were out of date on the dev release node, which made it easy, but that's gone now. I asked another distribution maintainer at Drupalcon a few weeks ago, and he just used the update status list. That works, but it's annoying to wait for the updates locally, sometimes having to run cron, and a little tedious to go through all the list of modules.
The United States Bahá’í community numbers in the hundreds of thousands of members in almost 10,000 localities around the country, and the national office wanted a website to highlight local Bahá’í communities.
The new version of the directory of Baha'i communities in the United States has just been released, built on the Community Directory install profile on Drupal.org. Install profiles bundle together Drupal core with contributed modules and external libraries, enabling new sites to provide some functionality out of the box while still allowing the customization for which Drupal is famous.
DNotes.net has now been migrated to the Local Community Website Incubator install profile. Drupal install profiles, often called distributions, package together Drupal core with pre-configured contributed modules and external code libraries. This enables new sites to be useful out-of-the-box while still allowing the customization for which Drupal is famous.
