Newsfeeds

follows

While working with Migrate and Migrate 2.6 beta 1 I stumbled upon several undocumented "surprises" which are hopefully going to be documented, but so far, you can spend lots of time trying to figure out what may be wrong. Here's roundup of my findings:

1. There is one correct way of registering migrations and handlers

You should do this in hook_migrate_info(), your register code may look like this:

Read on about Migrate Module Caveats. May Save You Some Time... and Hair

This module allows registered users to add posts to their Facebook feeds when they create new content or make a comment on your site.

It was designed to work as simple as possible for users with the minimum setup required, and it works similar to Twitter Post sub-module from Twitter module package if you are familiar with it. All that user needs to do is to add connection to his/her Facebook account in the Drupal account edit page. Connection is persistent, but there is a limitation that it stays valid for 60 days (as of writing), and user must reconnect his/her account every 60 days (this limitation is set by Facebook itself), so keep that in mind.

INSTALLATION AND CONFIGURATION

1. Install the module as usual.
2. Create Facebook application, which will be used for posting to users' feeds on their behalf.
If you don't know how to do this, go to https://developers.facebook.com/ page.
3. Go to admin/config/fb-post and enter your Facebook application credentials.
4. Go to admin/people/permissions and under 'Facebook Post' section set permissions as desired.
5. Visit content type edit page such as admin/structure/types/manage/page for each content type where you want to enable the feature of posting to Facebook, and under 'Facebook Post' tab choose your settings.
6. If you go to your user edit page you'll see 'Facebook Account Connection' tab their where you can manage your connection.

Paytrail is a new payment system from Finland that will replace the older system, Suomen Verkkomaksut. The development of the service is still ongoing. Once it's ready, Drupal integration will be provided. The plan is to create a general, API-like implementation and a commerce sub-module.

If you need to integrate the system to your Drupal-site, get in touch with us. All non-Drupal integrations are handled by Fraktio.

CREDITS

This module is developed by Roni Kantis and sponsored by Druid. Contact us for all your Drupal needs.

This Module provides a field for Accordeon within a node

An OSR approach to nonviolent RPing?

This is a feeds plugin that saves results from Feeds source to Azure table storage. Azure table is one of the services that Windows Azure offers.

Requirements:
1. Feeds
2. Ctools
3. Drush
4. Composer_vendor

Bolstered by Dries's nod to RedHen CRM in his keynote address, our RedHen code sprint at DrupalCon last Friday was a great success. This being our first community sprint, the ThinkShout team was happy to collaborate with an awesome group of development partners, including Stein Setvik from Forum One, Alan Sherry from Freeflow Digital, Chris Ward from MoatMedia (in Australia), and Jesse Longacre. Together we made progress on three fronts:

• First, we came up with a development roadmap, user interface, and stubbed out code base for a RedHen contact dedupping and merge feature;
• Second, we began work on a CiviCRM-to-RedHen migration tool;
• And finally, we completed an initial release of a RedHen Feeds module for creating RedHen contacts and organizations.

We look to keep this community momentum going into June with the help of these (and many other) partners and friends. In particular, we are focused this next month on completing the dedupping and merge feature and the CiviCRM-to-RedHen migration tool, a as well as continuing to sprint on RedHen community documentation.

Thank you to all those in the community supporting the RedHen initiative!

Tags: RedHenDrupal PlanetDrupal Give

A drupal project to allow easy entry of sourced genealogical data.

A display plugin for Views that renders like the standard table plugin, except for the case of active grouping, where this will render a single table with multiple tbody parts, as opposed to an independent table per each row of the grouping field.

I decided to try something new. I’m sharing my notes from the sessions and keynotes I attended at DrupalCon Portland 2013. This page is a hub listing all of my DrupalCon posts.

This is a copy of https://drupal.org/project/vimrc that tries to be compatible with Vundle for easy installation and updating.

Original discussion here: #2005150: Installation with Vundle

All development happens at the original module and all credit goes to the maintainers of the original module.

About Issue Reporting

Issue Reporting is a set of modules to help with Usability Testing and Feedback Aggregation.

The base module Issue Reporting provides a toolbar for users to report issues with pages or elements of pages. These anonymous reports are sent to a web service.

An administration module Issue Reporting Admin is also provided that allows for viewing submitted reports.

The Issue Reporting Server module allows for the easy creation of a Drupal based web service that can store and send information on these reports. The plan is for the default Issue Reporting Server to be hosted somewhere that the Usability group (https://groups.drupal.org/usability) can review reports periodically.

Current Status

This project is currently in development.

The user facing toolbar is almost complete and currently outputs reports to the browsers console.

Once the server is completed, we can start storing these reports. The next step will be a simple method for viewing these reports followed by more useful tools that can show issues relevant to pages as the site is viewed.

DrupalCon Portland is over and many of us left feeling excited about Drupal 8. There will be a lot of changes from Drupal 7 to Drupal 8, and if you are wondering about what is new, one of the best ways to learn is to get involved with Drupal 8 development right now. Until recently, I had tried a couple of times to get involved with Drupal core, but became frustrated when I couldn't find an issue appropriate for me or I worked on a patch that got stuck in "needs review." While there are many ways to help out with Drupal core development, I would like to highlight three areas where I think you will have success -- the first is an ongoing effort for new contributors, the second is for frontend developers, and the third is for backend developers.

1. Core Mentoring
There is an awesome, friendly, and smart group of people that want to help you get involved with Drupal and they have gone to great lengths to remove some of the most common pain points. Twice a week these folks hop onto #drupal in IRC and will do their best to add "Drupal core contributor" to your resume. Whether you prefer to work on documentation, simple patches, or dive into something more complicated that interests you, these kind folks will help. They will find an issue appropriate for you, assign you a mentor, and track it on the Drupal core mentoring website. Some of these issues are as simple as removing spelling errors, adding a doc block, or removing code. That's right, you could become a core contributor simply by removing code. Read more about core mentoring on drupal.org.

2. Mobile Initiative
You might have heard that as a result of the mobile initiative, led by John Albin Wilkins, Drupal 8 will be responsive. What you might not know is that there is an effort to make Drupal core's CSS architected to be predictable, reusable, maintainable, and scalable. There is detailed information about the plan for Drupal 8's CSS architecture and CSS file organization. To help achieve these goals, there is a "meta" issue called Architect our CSS that contains a list of related issues. At DrupalCon Portland we renamed various CSS files to match the new file naming convention, but there is still work that needs to be done. In other words, now is a great time to get involved with Drupal 8's mobile initiative because there is a plan, with action items, and a bunch a friendly folks that would like your help and would like to help you.

3. WSCCI
The Web Services and Context Core Initiative (WSCCI), led by Larry Garfield, is an effort to transform Drupal from a first-class CMS to a first-class REST server with a first-class CMS on top of it. If you can setup a local Drupal development, know how to write PHP code, and have at least a rudimentary understanding of object-oriented programming, check out the "meta" issue currently titled "Convert page callbacks to controllers." Doing these "conversion" patches is a great way to get involved in core development because there is a Conversion Guide to help you through the process. In other words, these dedicated developers have created a list of issues that are important to them, a conversion guide, and they will review your patches.

As I mentioned, there are many other ways to contribute to Drupal, so find one that works for you. If you have any other questions about contributing to Drupal, feel free to ping me (mtift) or ask a question on #drupal-contribute. I hope to see you in the issue queue!

Tags: drupaldrupal planet

The module provides a panelstyle for the Willibald theme. It allows to change the background of the panels in four different colors:

• dark blue
• light blue
• orange
• green

The text can be changed to five colors:

• white
• dark blue
• light blue
• orange
• green

Related project

• Willibald theme

Dependencies

• ctools
• panels

Maintainer

• Josef Friedrich (jos.friedrich@gmail.com)

Lists unapproved users with registration details including entity fields. The administrator can select multiple users for deletion

Overview

Studyroom is a family of modules to create an online system by which users can reserve administrator-defined spaces of an organization for set periods of time. Users can create, edit, and delete their own reservations, as well as peruse a gallery of all spaces that can be reserved at a given location(s) and view calendars of all reservations.

Its primary audience is universities/colleges and libraries.

Features

• The module make use of Drupal 7 entities, using the Entity API module to do most of the heavy lifting.
• You can configure minimum and maximum duration of reservations, and maximum days in advance a reservation can be made. This is configurable at the global level, with overrides at the location and space level.

Requirements

Drupal version 7.14 or greater.
The use of the DateInterval class means that we require PHP version >5.3.

Tutorials/Installation

• Activate all the Studyroom modules and their dependencies.
• Visit admin/studyroom/locations create a location type (e.g. Estrella Hall).
• Visit admin/studyroom/spaces and create spaces (e.g. Room 1, Lounge 3).

Credits

Current maintainers:

• Scott Worthington

This project has been sponsored by:
Estrella Mountain Community College

Recommended modules

Views Bulk Operations (VBO): Allow for bulk management of reservations (like delete all for testing)

Similar projects

Drupal Rooms - Drupal rooms requires the commerce module and is not designed to accomidate less than one day reservation, where this module can go a small as a 15 minute reservation.

Turbolinks makes following links in your web application faster. Instead of letting the browser recompile the JavaScript and CSS between each page change, it keeps the current page instance alive and replaces only the body and the title in the head. Think CGI vs persistent process.

This is similar to pjax, but instead of worrying about what element on the page to replace, and tailoring the server-side response to fit, we replace the entire body. This means that you get the bulk of the speed benefits from pjax (no recompiling of the JavaScript or CSS) without having to tailor the server-side response. It just works.

Do note that this of course means that you'll have a long-running, persistent session with maintained state. That's what's making it so fast. But it also means that you may have to pay additional care not to leak memory or otherwise bloat that long-running state. That should rarely be a problem unless you're doing something really funky, but you do have to be aware of it. Your memory leaking sins will not be swept away automatically by the cleansing page change any more.

https://github.com/rails/turbolinks

This project is the the Drupal implementation of TurboLinks, a feature new to Ruby On Rails in version 4.

New research show pigeons can make informed choices, and use a computerized touch-screen as well.

Allow your visitors to download files after publishing a tweet on his twitter account.