Agrégateur de flux

Mark Shropshire: DrupalCamp Atlanta 2014

Planet Drupal - mer, 08/10/2014 - 20:54

As expected, I had a great time at DrupalCamp Atlanta 2014 last weekend. While I enjoy attending sessions, it is the chance to catch up with old friends and make new ones that I love.

I want to thank all of those who made this camp a great one (sponsors, ADUG, presenters, volunteers, and attendees)!

Some of my session notes can be found below (unedited):

Sessions Blog Category: 
Catégories: Elsewhere

Elena 'valhalla' Grandi: New gpg subkey

Planet Debian - mer, 08/10/2014 - 20:42
The GPG subkey I keep for daily use was going to expire, and this time I decided to create a new one instead of changing the expiration date.

Doing so I've found out that gnupg does not support importing just a private subkey for a key it already has (on IRC I've heard that there may be more informations on it on the gpg-users mailing list), so I've written a few notes on what I had to do on my website, so that I can remember them next year.

The short version is:

* Create your subkey (in the full keyring, the one with the private master key)
* export every subkey (including the expired ones, if you want to keep them available), but not the master key
* (copy the exported key from the offline computer to the online one)
* delete your private key from your regular use keyring
* import back the private keys you have exported before.
Catégories: Elsewhere

Ian Donnelly: A Comparison of Elektra Merge and Git Merge

Planet Debian - mer, 08/10/2014 - 20:02

Hi everybody,

We have gotten some inquires about how Elektra’s merge functionality compares to the merge functionality built into git: git merge-file. I am glad to say that Elektra outperforms git’s merge functionality in the same ways it outperforms diff3 when applied to configuration files. Obviously, git’s merge functionality does a much better job with source-code as that is not the goal of elektra. In that previous example, I showed that because diff3 is lined based, where Elektra is not (unless you mount a file using the line plugin). The example I used before, and I will go over again, is using smb.conf and in-line comments.

Many of our storage plug-ins understand the difference between comments and actual configuration data. So if a configuration file has an inline comment like so:
max log size = 10000 ; Controls the size of the log file (in KiB)
we can compare the actual Keys, value pairs between versions max log size = 10000 and deal with the comments separately.

As a result, if we have a base:
max log size = 1000 ; Size in KiB

Ours:
max log size = 10000 ; Size in KiB

Theirs:
max log size = 1000 ; Controls the size of the log file (in KiB)

The result using elektra-merge would be:
max log size = 10000 ; Controls the size of the log file (in KiB)

Just like diff3, git merge-file can only compare these lines as lines, and thus there is a conflict. When running git merge-file smb.conf.ours smb.conf.base smb.conf.theirs we get the following output showing a conflict:
<<<<<<< smb.conf.ours
max log size = 2000 ; Size in KiB
=======
max log size = 1000 ; Controls the size of the log file (in KiB)
>>>>>>> smb.conf.theirs

This really shows the strength of Elektra’s plugin system and why it makes merge an obvious use-case of Elektra. I hope this example makes it clear why using Elektra’s merge functionality is advantageous over git’s merge functionality. Once again I would like to stress the importance of quality storage plug-ins for Elektra. The more quality plugins we have the more powerful Elektra can be. If you are interested in plugins and would like to help us by adding functionality to Elektra by creating a new plug-in be sure to read my basic tutorial on how to do so.

Sincerely,
Ian Donnelly

Catégories: Elsewhere

Acquia: Drupal 8 - An intro field guide for front-end developers

Planet Drupal - mer, 08/10/2014 - 19:22

Drupal 8 is almost here, and it’s bringing big front-end improvements, including new methods to display data on mobile devices using breakpoints, build flexible templates in Twig and better management for tools and libraries.

Most importantly, changes to the display layer mean that Drupal has become much more agile and extendable for Front-end Developers.

The journey so far

Up till now, Front-end Developers have been working with a display layer that was originally introduced in Drupal 4.5, here’s how it worked...

Catégories: Elsewhere

Acquia: 1st DrupalCon, 1st Contribution! Meet Oliver and Victoria

Planet Drupal - mer, 08/10/2014 - 18:18

DrupalCon Amsterdam was something of a family outing for me. My wife Francesca attended all week and my kids were able to come out Thursday evening to attend Trivia Night and the Friday sprints. My daughter Victoria had sewn a dress and a cape to appear as Drupal Girl on Thursday evening. Her weeks of work on that really paid off; she was a big hit. She also got to meet her Drupal idol, MortenDK, who was the inspiration for her brand new Drupal.org and Twitter username: Drupal_Princess. There's a great photo of her meeting Webchick floating around online, too.

Catégories: Elsewhere

Appnovation Technologies: OS Initiative Community Site Launched

Planet Drupal - mer, 08/10/2014 - 17:28
The community site for our OS Initiative is now live! var switchTo5x = false;stLight.options({"publisher":"dr-75626d0b-d9b4-2fdb-6d29-1a20f61d683"});
Catégories: Elsewhere

mcdruid.co.uk: How to cleanly delete a Drupal file with drush

Planet Drupal - mer, 08/10/2014 - 16:43

This is a simple trick which (unless my googlefu simply failed me) I didn't find described anywhere when I had a quick look:

$ drush ev '$file = file_load(21749); var_dump(file_delete($file, TRUE));' bool(true)

This means all the appropriate hooks are called in file_delete so the Drupal API gods should smile on you, and you should get to see the TRUE/FALSE result reflecting success or otherwise. Note that we're passing $force=TRUE "indicating that the file should be deleted even if the file is reported as in use by the file_usage table." So be careful.

To delete multiple files you could use file_load_multiple but there's not a corresponding file_delete_multiple function, so you'd have to loop over the array of file objects.

That's all there is to this one.

Catégories: Elsewhere

EvolvisForge blog: PSA: #shellshock still unfixed except in Debian unstable

Planet Debian - mer, 08/10/2014 - 15:57

I just installed, for work, Hanno Böck’s bashcheck utility on our monitoring system, and watched all¹ systems go blue.

① All but two. One is not executing remote scripts from the monitoring for security reasons, the other is my desktop which runs Debian “sid” (unstable).

This means that all those distributions still have unfixed #shellshock bugs.

  • lenny (with Md’s packages): bash (3.2-4.2) = 3.2.53(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
  • squeeze (LTS): bash (4.1-3+deb6u2) = 4.1.5(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
  • wheezy (stable-security): bash (4.2+dfsg-0.1+deb7u3) = 4.2.37(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
    • CVE-2014-6278 (lcamtuf bug #2)
  • jessie (testing): bash (4.3-10) = 4.3.27(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
    • CVE-2014-6278 (lcamtuf bug #2)
  • sid (unstable): bash (4.3-11) = 4.3.30(1)-release
    • none
  • CentOS 5.5: bash-3.2-24.el5 = 3.2.25(1)-release
    • extra-vulnerable (function import active)
    • CVE-2014-6271 (original shellshock)
    • CVE-2014-7169 (taviso bug)
    • CVE-2014-7186 (redir_stack bug)
    • CVE-2014-6277 (lcamtuf bug #1)
  • CentOS 5.6: bash-3.2-24.el5 = 3.2.25(1)-release
    • extra-vulnerable (function import active)
    • CVE-2014-6271 (original shellshock)
    • CVE-2014-7169 (taviso bug)
    • CVE-2014-7186 (redir_stack bug)
    • CVE-2014-6277 (lcamtuf bug #1)
  • CentOS 5.8: bash-3.2-33.el5_10.4 = 3.2.25(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
  • CentOS 5.9: bash-3.2-33.el5_10.4 = 3.2.25(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
  • CentOS 5.10: bash-3.2-33.el5_10.4 = 3.2.25(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
  • CentOS 6.4: bash-4.1.2-15.el6_5.2.x86_64 = 4.1.2(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
  • CentOS 6.5: bash-4.1.2-15.el6_5.2.x86_64 = 4.1.2(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
  • lucid (10.04): bash (4.1-2ubuntu3.4) = 4.1.5(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
  • precise (12.04): bash (4.2-2ubuntu2.5) = 4.2.25(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
    • CVE-2014-6278 (lcamtuf bug #2)
  • quantal (12.10): bash (4.2-5ubuntu1) = 4.2.37(1)-release
    • extra-vulnerable (function import active)
    • CVE-2014-6271 (original shellshock)
    • CVE-2014-7169 (taviso bug)
    • CVE-2014-7186 (redir_stack bug)
    • CVE-2014-6277 (lcamtuf bug #1)
    • CVE-2014-6278 (lcamtuf bug #2)
  • trusty (14.04): bash (4.3-7ubuntu1.4) = 4.3.11(1)-release
    • CVE-2014-6277 (lcamtuf bug #1)
    • CVE-2014-6278 (lcamtuf bug #2)

I don’t know if/when all distributions will have patched their packages ☹ but thought you’d want to know the hysteria isn’t over yet…

… however, I hope you were not stupid enough to follow the advice of this site which suggests you to download some random file over the ’net and execute it with superuser permissions, unchecked. (I think the Ruby people were the first to spread this extremely insecure, stupid and reprehensible technique.)

Thanks to ↳ tarent for letting me do this work during $dayjob time!

Catégories: Elsewhere

Jan Wagner: Updated Monitoring Plugins Version is coming soon

Planet Debian - mer, 08/10/2014 - 13:27

Three months ago version 2.0 of Monitoring Plugins was released. Since then many changes were integrated. You can find a quick overview in the upstream NEWS.

Now it's time to move forward and a new release is expected soon. It would be very welcome if you could give the latest source snapshot a try. You also can give the Debian packages a go and grab them from my 'unstable' and 'wheezy-backports' repositories at http://ftp.cyconet.org/. Right after the stable release, the new packages will be uploaded into Debian unstable. The whole packaging changes can be observed in the changelog.

Feedback is very appreciated via Issue tracker or the Monitoring Plugins Development Mailinglist.

Catégories: Elsewhere

Michal &#268;iha&#345;: Wammu 0.37

Planet Debian - mer, 08/10/2014 - 12:00

It has been more than three years since last release of Wammu and I've decided it's time to push changes made in the Git repos to the users. So here comes Wammu 0.37.

The list of changes is not really huge, but in total that means 1470 commits in git (most of that are translations):

  • Translation updates (Indonesian, Spanish, ...).
  • Add export of contact to XML.
  • Add Get all menu option.
  • Added appdata metadata.

I will not make any promises for future releases (if there will be any) as the tool is not really in active development.

Filed under: English Gammu Wammu | 0 comments | Flattr this!

Catégories: Elsewhere

Drupal Bits at Web-Dev: Codit and Codit: Local Introduction Video

Planet Drupal - mer, 08/10/2014 - 08:04

This is a short screencast showing the basic concept of Codit and Codit: Local and where to place them in a Drupal site.

Catégories: Elsewhere

Don't Panic: A blog about Drupal: DrupalCon Amsterdam: &quot;There and back again&quot;

Planet Drupal - mer, 08/10/2014 - 01:01

DrupalCon Amsterdam has come to an end (well, it ended last week, buy hey, I need to catch up on some work as well). It was the biggest DrupalCon in Europe ever, 2,300 attendees! Pretty impressive. I've written a couple of blog entries, trying to capture my stay in Amsterdam and my feelings for a DrupalCon which I attended for more than three days (which has been the case with DrupalCon London and DrupalCon Munich).

Not only did Drupal 8 get a BETA during these days, but a lot of sprinting was happening (as always) and it was pure joy walking through the Berlage in the center of town and at the venue, seeing all that work being put into Drupal.

Tuesday and Wednesday was filled with interesting sessions, and both Tuesday evening with nice boat rides and pub crawl and Wednesday evening with open museums (the light installations at the EYE was spectacular!) was very nice indeed. Thursday, the day for separation for many of us, was also filled with good sessions and the closing talk with Holly and Stephanie both invited us to DrupalCon Barcelona next year, as well as presenting cool statistics about the Con.  

The good...

All of the sessions I attended was good, and, as always, I'm impressed by the time and energy people devote to making Drupal happen and spreading the knowledge and some love. Dries Buytaert's keynote ('the Driesnote') was inspiring, but I didn't agree with everything he said. He talked about the "free-riders", the ones who doesn't help out with Drupal, the ones who only take advantage of the system witouth giving something back. Such a thing is a bad thing, according to Dries. But I think that we also need those free-riders, becuase those free-riders are the ones using the system, making the statistics for Drupal go up worldwide, spreading the word of Drupal. If we don't have free-riders, are the only ones who should use Drupal the ones who code it and support it? If so, Drupal won't get far...

Amsterdam RAI, the venue, was a good venue. Apart from some sessions being very popular (which is a pain in the a** forseeing) so I couldn't get into them, the rooms and hallways were good for sessions and sprinting. The technique was good as well, sound and vision in the sessions was flawless. Big thumbs up for that. The recorded sessions was also professionally made, at least the ones I've had time to watch. Finding them on YouTube the same day or, to some extent, the next is also impressive. Big thumbs up to the techinal team who worked on that during the Con.

The evening activites was also impressive. Ingenuity, local connection and very nice people raised the bar a lot. I kind of fell in love with the architecture of Amsterdam with it's old crooked buildings, canals and the narrow streets, and the boatride on Tuesday evening was magical!

...the bad...

But there's always something that brings a frown to the face. This time I frowned upon three things. The wi-fi. The coffee. The food.

The wi-fi. It's shouldn't be that hard to calculate that if 2,300 persons gather in a closed area and at least half of them have both laptops and phones, there will be much traffic. I don't want to drag Drupal Association of the local community in the dirt here, they hired a company to manage the network and wi-fi, but it's irritating trying to get online for various reasons, and the network dies several times a day.

The coffee. Apparantely the coffee last year in Prague was bad. The worst thing about coffee this year, was that it wasn't free. It cost me 2.5 Euro. When I pay this much for a ticket to a DrupalCon I kind of expect coffee or some other drink to be free. If it's too hard to calculate, try giving out beverage tickets, two or three per day. Some will get lost, some won't be used, but at least I won't have to pay 2.5 Euro for a small cup of coffee that's not even that good.

The food. A small bowl of pasta or paella. A sandwich and some dessert. I was hungry three hours later. I had the opportunity to visit DrupalCon Munich in 2012 and the food there was out of this world. Every DrupalCon after that will always have worse food. But this one is a killer. No imagination. Lots of garbage (in a time where we try to limit our carbon footprints). No drink. (At least I couldn't find any. Or maybe I was supposed to go and buy me a drink for 2-3 Euros.) Didn't get that. Didn't do that either.

There. Now that's out of my system. I won't remember that when I', 60. But I'll remember the rest of DrupalCon Amsterdam. The sessions. The laughs. The excursions.

...and the ugly...

Well... I found an ugly statue somewhere in town, but otherwise that headline was only in it for the Clint Eastwood reference.

Special thanks to...

It takes a lot of work making a DrupalCon happen, and the Drupal Association pulled it off with a gold star I think. Sure, there were flaws, but then perhaps those won't happen next time, or there were good reasons to why there were flaws. But the Drupal Association do this for a living, so I will only give them a normal-sized 'thank you'. The big 'thank you' goes to the local community who gave the DrupalCon a Dutch feeling. I also want to say thank you to those people who were mentoring before, during and after DrupalCon. Instead of working with the code like you perhaps wanted to, you devoted your time and energy to encourage us lesser beings who want to learn more about Drupal. Also, a big hug to Annertech, who made the Quiz Night happen. It's not an easy task trying to get Morton and Bert the crowd quiet so you can present questions and answers. The man with the microphone also liked the name of our team - Fools drush in - which was nice!

You all know who you are - THANK YOU!

Catégories: Elsewhere

Chapter Three: 5 Hurdles to Adopting Drupal 8

Planet Drupal - mer, 08/10/2014 - 00:36

Drupal 8 presents major improvements to the existing Drupal ecosystem. It offers much, including a revamped Entity API that adds tremendous flexibility to content modeling, a core-level translation system for multilingual sites, responsive theming, in-place editing and the configuration management system. But with all of its improvements, Drupal 8 presents some hurdles for agencies like Chapter Three to identify and overcome.



Catégories: Elsewhere

Tyler Frankenstein: Drupal User Entity Reference Field with Custom Autocomplete that uses an Address Field

Planet Drupal - mar, 07/10/2014 - 23:24

User reference fields (aka entity reference fields) are great. As you may have guessed, we can use these fields to reference users on other entities (e.g. nodes).

Say we had a user reference field on the Article content type... by default, when selecting a user to reference, we could configure the field widget to be an autocomplete. This allows us to begin typing the user's login name as a way to reference them. This works well in most cases.

What if we had an address field on our user entities, and collected the user's first and last names? It may be more usable for site administrators to be able to search across the user's actual name instead of their user name for logging in.

We can use hook_menu(), hook_form_alter(), and a custom callback function to provide a custom autocomplete widget that searches across our address field's values instead...

Catégories: Elsewhere

Mediacurrent: Installing the Pardot Drupal Module

Planet Drupal - mar, 07/10/2014 - 22:40

Mediacurrent has made a commitment to work with the Drupal community to help maintain and improve modules for the leading Marketing Automation services. In this tutorial, we will show you how to set up the newly upgraded Pardot (a Salesforce Company) module.

Catégories: Elsewhere

Modules Unraveled: 121 The Harmony Forum Project with Alli Price - Modules Unraveled Podcast

Planet Drupal - mar, 07/10/2014 - 20:34
Published: Tue, 10/07/14Download this episodeHarmony Forum
  • What is Harmony Core?
  • What prompted you to develop it over using the core forum module?
  • Did you take a look at the Advanced Forum module?
    • What didn’t you like about it?
  • So what are some of the features?
    • Kill switch
    • Entities
    • Revisions for Post entity, integration with Diff module
    • Views provides all listings including on a thread page
    • Flag action for "Like" of posts
    • At.js
  • Does this integrate with other community related module? ie: Organic Groups
  • What are some of the sub-modules, or add-on modules that enhance Harmony Core?
    • Harmony Access
    • Harmony Forum Access
    • Harmony Search
    • Harmony Moderation
    • Harmony Migrate
Use Cases
  • Who’s using Harmony now?
  • You mentioned some upcoming events what are those?
  • How can people get involved?
  • Where should people go to find out more?
Questions from Twitter
  • Scott Wilkinson
    What kind of moderation tools will Harmony have? Like pruning posts or users? Forum Moderators?
Episode Links: Alli on drupal.orgAlli on TwitterForum development group on g.d.oGet on the email listFeatures listDemo of the frontendTags: ForumsCommunity Modulesplanet-drupal
Catégories: Elsewhere

Freelock : Importing foreign key references with Migrate

Planet Drupal - mar, 07/10/2014 - 19:04

One of our clients wanted to regularly update a list of dealers along with the parts carried at that dealer, and show them on a map. As I dug into the challenge, I was a bit surprised to find very little information on the web about how to hook up a migration that would essentially import a join table. So I had to create it myself!

MigrateDrupalDrupal PlanetERPRetailManufacturingDealersentityreferenceTechnical
Catégories: Elsewhere

Thorsten Glaser: mksh R50d released

Planet Debian - mar, 07/10/2014 - 17:54

The last MirBSD Korn Shell update broke update-initramfs because I accidentally introduced a regression in field splitting while fixing other bugs – sorry!

mksh R50d was just released to fix that, and a small NULL pointer dereference found by Goodbox on IRC. Thanks to my employer tarent for a bit of time to work on it.

Catégories: Elsewhere

Deeson: DrupalCon Amsterdam: the Deeson digest

Planet Drupal - mar, 07/10/2014 - 17:52

Last week was all about DrupalCon Amsterdam.

Deeson’s MD, Tim Deeson, sat on a panel Q&A, I rallied the community with giveaways and things to play with and our Solutions Architect John Ennew joined in hackathons. We also organised Birds of a Feather (BoF) sessions.

For those who want to know more, here is our complete guide to Europe’s biggest Drupal conference event which celebrates the community and experiences working with Drupal’s open source software.

1. The keynotes

The two main keynotes at the conference were delivered by Drupal founder, Dries Buytaert, and science fiction author, activist, journalist, blogger and co-editor of Boing Boing, Cory Doctorow. They were very different in style and approach, but both were fascinating and highly informative.

Dries Buytaert

Dries’ keynote focused on the maturity of Drupal as a platform and community. He touched on the inevitable growing pains and the tough choices we all face as Drupal expands its reach and influence.

He drew on proven growth principles, such as the Tragedy of the Commons, to illustrate Drupal’s ‘journey’. He highlighted how Drupal's reach can grow with community support, from local leadership initiatives to rewarding Drupal contributors.

Watch Dries' keynote

Cory Doctorow

Cory discussed the significance of free and open source software, highlighting the challenges and issues which impact us all.

As a tech evangelist, he shared his expert insight into the importance of software transparency in an age where tech and devices infringe on our everyday lives. It was pretty sobering.

2. Drupal 8: the beta release

Dries announced the beta release of Drupal 8. The Drupal community will now be working together to find and fix bugs before the full release of Drupal 8. 

3. The sessions

Tim took part in a business-focused panel session entitled: 'Life in the fast lane - achieving sustainable growth'.

The hour-long session went through issues and challenges faced by Drupal agencies, shops and freelancers trying to achieve growth. Read the key takeaways here or check out the video:

4. Mentoring

John signed up as a sprint mentor for the first time and taught new contributors to Drupal Core how they can set up contributing tools. 

Mentoring the Drupal community builds confidence and empowers developers to become regular contributors to Drupal Core.

5. Swag demand

The event may focus on code but t-shirts feature heavily. 

Our designer, Rachael Case, created a stunning Deeson DrupalCon tee which flew off our stand. They were so popular, people even nabbed the display tees off the wall!

6.Frame of Fame

As you might understand by now, community is at the core of Drupal. 

We wanted to celebrate the community who worked on Drupal 8 with our Frame of Fame. Check out the faces behind the code, contributes and commits…

We took the Frame of Fame into the digital world with The Drupal8r...

7. The Drupal8r

Our developer, Chris, created an amazing data visualisation tool, The Drupal8r shows who in the Drupal community developed Drupal 8 during the last 5000 commits. Give it a whirl yourself!

 

8. The Dries interview

It’s not everyday you get to interview the founder of Drupal, Dries Buytaert. But we did.

We’ll be sharing our conversation with Dries soon, so sign up to our newsletter at the bottom of this page to find out about the successes and failures in Drupal 8 delivery. 

We’ll also be publishing our #AskDries video where Dries answers questions from DrupalCon attendees. Watch this space!

9. The BoFs

John and I ran BoFs at DrupalCon Amsterdam. John focused on experiences of integrating Customer Relationship Management (CRM) systems with Drupal while I explored the need for personas in the site build process.

You can read the full write up of John’s session here. My session summary is here in a shareable Google Doc which highlights the basic persona questions, plus links to a few resources for persona newbies.

10. Nos vamos a Barcelona para DrupalCon 2015!

DrupalCon Europe 2015 is in Barcelona. So we're going to brush up on our Spanish. ¡Vamos!

Catégories: Elsewhere

Digett: Product Review: New Relic APM for Drupal Performance Tuning

Planet Drupal - mar, 07/10/2014 - 17:36

New Relic APM (Application Monitoring) is an amazing tool to help you tune the performance of your Drupal website.

read more

Catégories: Elsewhere

Pages

Subscribe to jfhovinne agrégateur