Agrégateur de flux

I

Although I don’t mean to brag… I have an really great scarf-hood-combination garment.

I was wearing said awesome scarf in a rather cold apartment during my remote participation in the Learning Creative Learning class.

I would like to think that I said some interesting and insightful things. But if I didn’t, I’m glad to hear my scarf — which now has its very own sub-reddit — was able to impress and entertain.

Hi guys,

I spent a chunk of my sunday updating the initiatives for us, go check out the latest news post-feature freeze and all the top issues here:
http://drupal.org/community-initiatives/drupal-core

Thanks to Ashleigh Thevenet and Shyamala for your help with these :)

Happy Monday!
Shannon

Start:  2013-03-20 (All day) America/New_York Sprint Organizers:  David_Rothstein

The monthly security release window for Drupal 6 and Drupal 7 core will take place on Wednesday, March 20.

This does not mean that a Drupal core security release will necessarily take place on that date for either the Drupal 6 or Drupal 7 branches, only that you should prepare to look out for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).

There will be no bug fix release on this date; the next window for a Drupal core bug fix release is Wednesday, April 3.

For more information on Drupal core release windows, see the documentation on release timing and security releases, and the discussion that led to this policy being implemented.

In this video tutorial we look at how to add infinite scroll (endless pages, load more) to pages of your website in drupal. The infinite scroll is sometime also referred to as endless pages. In other to achieve this in drupal, I decided to create two videos using two different modules.

 

1.  Views infinite scroll: The views infinite scroll does not use the views Ajax support. It makes use of its own Ajax request.

http://drupal.org/project/views_infinite_scroll

2.  Views Load more: The Views load more on the other hand, supports the views Ajax feature. If the Ajax feature on views is enabled, the load more add content to the bottom of the page without refreshing.

 http://drupal.org/project/views_load_more

 

To follow this tutorial you should have at least some knowledge of the views module. As both require you to be using views 3.x

By the end of this tutorial, you will be able to install and configure the views infinite scroll and views load more module on a views listing.

 

Part 2 of the video

In this video tutorial we look at how to add infinite scroll (endless pages, load more) to pages of your website in drupal. The infinite scroll is sometime also referred to as endless pages. In other to achieve this in drupal, I decided to create two videos using two different modules.

 

1.  Views infinite scroll: The views infinite scroll does not use the views Ajax support. It makes use of its own Ajax request.

 

http://drupal.org/project/views_infinite_scroll

 

2.  Views Load more: The Views load more on the other hand, supports the views Ajax feature. If the Ajax feature on views is enabled, the load more add content to the bottom of the page without refreshing.

 

http://drupal.org/project/views_load_more

 

To follow this tutorial you should have at least some knowledge of the views module. As both require you to be using views 3.x

By the end of this tutorial, you will be able to install and configure the views infinite scroll and views load more module on a views listing.

 

Part 2 of the video

With many people coming to visit this year, both for DebConf13 and holidays, I'm going to start sharing some Swiss travel tips here in the blog.

One of Switzerland's most popular tourist promotions is the Glacier Express railway. Here are the facts and a cool video.

Avoid tickets/itineraries with fixed dates for visiting the mountains.

The full Glacier Express journey is about 6 hours, and if it is cloudy or foggy, it is 6 hours in a train just like any other train.

Some days really are cloudy and you won't see a single mountain. Try and make sure you have several flexible days in Switzerland so you can go up the mountains when the weather is optimal.

Check the weather using the live webcam service

Below is a typical webcam image for a bad day (I was up there Saturday skiing and it was perfect, Sunday was every tourist's nightmare). Compare this picture with the video further down:

You can find a live feed like this for most Swiss mountain destinations with a web search

Regular passenger trains run on the same route

You don't need to buy an expensive `Glacier Express' ticket. A regular passenger train does the same route every hour. No fixed reservation is necessary either and you can hop off and back on again along the way at many little stops. Oberalp Pass, at 2000 meters, is a good place to stop and hike (up to the peaks if you are keen, down to Andermatt if you want an easy walk with breathtaking views)

What's more, the expensive trains are fully sealed and you can't open the windows. The regular trains do let you open the windows, so you can fully immerse yourself in the experience like this riding down from Natschen to Andermatt (1,500m):

<video controls="" height="340" poster="http://danielpocock.com/sites/danielpocock.com/files/train-poster.png" width="560">
<source src="http://danielpocock.com/sites/danielpocock.com/files/DSC_1776.mp4" type="video/mp4"></source>
<source src="http://danielpocock.com/sites/danielpocock.com/files/DSC_1776.webm" type="video/webm"></source>
</video>

To plan an itinerary, you can check Swiss train timetables at the official web site http://www.sbb.ch/en

& another week has gone by where I tried to work on RC bugs. here's the overview:

• #656090 – ocsinventory-server: "ocsinventory-server: prompting due to modified conffiles which where not modified by the user"
  ping bug, provide a package for piuparts testing, later upload to DELAYED/2
• #702753 – src:spandsp: "spandsp: Downloads external files at build time (through xsltproc) -- missing Build-Depends?"
  confirm and prepare patch, later upload to DELAYED/2
• #702769 – bup: "FTBFS: bup.git.GitError: no such commit '75cd2b98c52d29ba5d510b37d7c9adb01553bd1f'"
  add some information
• #702790 – service-wrapper-java: "FTBFS: local changes detected"
  investigate and send a possible cause of the problem to the bug log, add a patch later
• #703094 – owncloud: "owncloud: multiple vulnerabilities (oC-SA-2013-009, oC-SA-2013-010)"
  prepare patch from upstream commits

For anybody in Cyrpus right now, it should be relatively easy to spot those residents who keep their wealth in physical gold, silver or Bitcoin. Why? They will be the only people smiling this week, as everybody else has just had 6-10% of their bank account gouged by a once-off tax.

What is really scary is that Cyprus is a Eurozone country.

Will we now see the panic spread to Italy and Spain as citizens fear a copy-cat raid on their funds in the coming days or at some uncertain moment in the future?

This latest development should not be seen as a `small country' issue. The US did similar things with gold confiscation in the 1930s. Australia has decided to prop up the stock market by raising forced pension contributions on 1 July. What is different in Cyprus is that people will feel the pain immediately, and that modern technology will let the shockwaves spread.

We have just released shogun 2.1.0. This release contains over 800 commits since 2.0.0 with a load of bugfixes, new features and improvements (see the changelog for details) that make Shogun more efficient, robust and versatile. In particular, Christian Montanari developed a first alpha version of a perl modular interface, Heiko Strathmann did add Linear Time MMD on Streaming Data, Viktor Gal wrote a new structured output solver and Sergey Lisitsyn added support for tapkee - a dimension reduction framework. Read more at http://www.shogun-toolbox.org

On Monday, I was a visitor and guest speaker in a session on “Open Learning” in a class on Learning Creative Learning which aims to offer “a course for designers, technologists, and educators.” The class is being offered publicly by the combination — surprising but very close to my heart — of Peer 2 Peer University and the MIT Media Lab.

The hour-long session was facilitated by Philipp Schmidt and was mostly structured around a conversation with Audrey Watters and myself. The rest of the course materials and other video lectures are on the course website.

You can watch the video on YouTube or below. I thought it was a thought-provoking conversation!

<iframe allowfullscreen="" frameborder="0" height="315" src="http://www.youtube.com/embed/l9HM80cv160" width="560"></iframe>

If you’re interested in alternative approaches to learning and free software philosophy, I would also urge you to check out an essay I wrote in 2002: The Geek Shall Inherit the Earth: My Story of Unlearning. Keep in mind that the essay is probably the most personal thing I have ever published and I wrote it more than a decade ago it as a twenty-one year old undergraduate at Hampshire College. Although I’ve grown and learned enormously in the last ten years, and although I would not write the same document today, I am still proud of it.

Via twitter I just discovered that Pcwizz have done a video review on Youtube of Skolelinux / Debian Edu version 6. He installed the standalone profile and the video show a walk-through of of the menu content, demonstration of a few programs and his view of our distribution.

There is also some really nice quotes (transcribed by me, might have heard wrong). While looking thought the Graphics menu:

"Basically everything you ever need in a school environment."

And as a general evaluation of the entire distribution:

"So, yeah, a bit bloated. It kept all the Debian stuff in there, just to keep it nice and GNU. So, I do not want to go on about it, but lets give it 7 out of 10. I am not going to use it. That is because I am not deploying a school network. There may be some mythical feature to help you deploy Skolelinux on a school network."

To bad he did not test the server profile, and discovered the PXE installation option. It make it possible to install only the main server from CD, and the rest of the machines via the net, and might be considered the mythical feature he talk about. :)

While looking through the menus, there is also this funny comment about the part of the K menu generated from the Debian menu subsystem:

"[The K menu] have a special Debian section for software that no-one is going to look at, because it contain lots of junky stuff that you actually don't need in the education distribution, but have just been included because it isn't stripped out for some reason."

I guess it is yet another argument for merging the Debian menu and Gnome/KDE desktop menu entries into one consistent menu system instead of two incomplete and partly inconsistent menu systems.

The entire video is available below for those accepting iframe embedding:

<iframe allowfullscreen="allowfullscreen" frameborder="0" height="315" src="http://www.youtube.com/embed/wPzTZ61Pcuc" width="560"></iframe>

DPSX got off to a rocking start on the 14th of March, though the first hour was more of a rocky start given the chaos on the Central and Victoria lines that evening!
To keep things short and simples! all DPSX posts will get straight to the point, none of my usual verbosity! for that you’ll have to go to shirazee.com!

Speakers at the first DPSX event on Open Councils:

Richard Pope - Government Digital Service
Steve Purkiss – Drop.coop
Robert Miller – Lambeth Council
Michael Lenahan – Lambeth Council
Paul Mackay  – NESTA

Key points shared and discussed:

“..Open Source, Open data and Open by default is the ethos at Lambeth…” @RobMiller31

+ Current govt. is sorting its act out and the mentality is changing.
+ The govt. recognises that its a big undertaking and top down will to deliver value for our taxes and set the guidelines and a path for the local bodies to follow.

“Key to current successes has been lowering boundaries” @richardjpope

+ The govt. Digital service its not just about Drupal of course but the bigger picture, its about setting guidelines for central and local govt. bodies on harnessing Open Source, delivering services for the end users as well as digital services for the govt. and saving billions on the tech budgets!

“for any council to be undertaking this transformation in isolation is crazy” @mcaleaa
+ There is a shift in policy: internalising development

+ Making sure selection of OS suppliers is screened for OS too is open to abuse so watch out for the OS cage!

+ Procurement is opening up to smaller suppliers in a flexible accessible manner….and yes G-cloud is making a difference but not every one is sourcing form the g-cloud either! and there is much room for improvement

“..use your data to unlock yourself from proprietary contracts…” @kubair

+ Workflows at the local govt. level need improvement

 + Lambeth is looking to strengthen its team by working with other councils

+ Open data (via APIs) is the key to building a modular evolutionary/re-usable infrastructure – this also opens up the ability for developers to create ‘Apps’ for consumption by councils and potentially central govt.
+ NESTA is soon to launch Code for Europe modelled on Code for America that would improve collaboration across Europe for solutions built upon OS platforms.

 “..Lambeth has gone from the dark ages to star wars in 2 years..” ‏ @socialtechno

“most applications are still tied up in contracts, OS occupies a very small space within local government at his point..” @stevepurkiss

A few useful links:
Lambeth Council
Made in Lambeth
Government Digital Service
GDS design PrinciplesGDS Digital Strategy blog
Code For Europe Project

The next event for Drupal Public Sector Exchange will be held at the end of May 2013 and we will be going for a venue location a tad bit more centralish!
If you are interested in speaking at the next event, attending or have suggestions on speakers or topics you would like to see covered please drop us a tweet or an email…

DPSX is @Alanpeart @Calert @Greenman @Kubair @MarcDe_ath @shaunwilde

#Drupal #PublicSector #Innovation #G_Cloud_UK #NESTA #GovUK

So, over the few days I've been in New Zealand, I've seen a lot of technologically backwards Internet solutions -- hotels that expect you to pay, “24 hour packages” that are limited to 500 MB (1 GB for the 7-day packages), private networks still using WEP, and so on. However, the free Internet at Queenstown airport sets some kind of record; after the first hop, they seemingly have one with a 1.2 second delay!

So guys, I understand that you are a small island state, and I understand that your run-off-the-mill solution for Internet might not have fq_codel or something similarly fancy, but the rest of us figured out how to run 100gig over a normal single-mode fibre (plus DWDM on top of that) a while back.

Seen on Slashdot

https://www.gov.uk/service-manual/making-software/open-source.html

UK Government appearing to suggest a preference for developers that they should use open source where feasible for future UK Government projects for "Digital by Default" deliveries to UK Government and citizens.

This _is_ a beta version, but it is interesting to see this.

I've just pushed out the release files for Obnam version 1.4, my backup application, and Larch, my B-tree library, which Obnam uses. They are available via my home page (http://liw.fi/). Since Debian is frozen, I am not uploading packages to Debian, but .deb files are available from my personal apt repository for intrepid explorers. (I will be uploading to Debian again after the freeze. I am afraid I'm too lazy to upload to experimental, or do backports. Help is welcome!)

From the Obnam NEWS file:

• The`ls command now takes filenames as (optional) arguments, instead of a list of generations. Based on patch by Damien Couroussé.
• Even more detailed progress reporting during a backup.
• Add --fsck-skip-generations option to tell fsck to not check any generation metadata.
• The default log level is now INFO, instead of DEBUG. This is to be considered a quantum leap in the continuing rise of the maturity level of the software. (Actually, the change is there just to save some disk space and I/O for people who don't want to be involved in Obnam development and don't want to have massive log files.)
• The default sizes for the lru-size and upload-queue-size settings have been reduced, to reduce the memory impact of Obnam.
• obnam restore now reports transfer statistics at the end, similarly to what obnam backup does. Suggested by "S. B.".

Bug fixes:

• If listing extended attributes for a filesystem that does not support them, Obnam no longer crashes, just silently does not backup extended attributes. Which aren't there anyway.
• A bug in handling stat lookup errors was fixed. Reported by Peter Palfrader. Symptom: AttributeError: 'exceptions.OSError' object has no attribute 'st_ino' in an error message or log file.
• A bug in a restore crashing when failing to set extended attributes on the restored file was fixed. Reported by "S. B.".
• Made it clearer what is happening when unlocking the repository due to errors, and fixed it so that a failure to unlock is also an error. Reported by andrewsh.
• The dependency on Larch is now for 1.20121216 or newer, since that is needed for fsck to work.
• The manual page did not document the client name arguments to the add-key and remove-key subcommands. Reported by Lars Kruse.
• Restoring symlinks as root would fail. Reported and fixed by David Fries.
• Only set ssh user/port if explicitily requested, otherwise let ssh select them. Reported by Michael Goetze, fixed by David Fries.
• Fix problem with old version of paramiko and chdir. Fixed by Nick Altmann.
• Fix problems with signed vs unsigned values for struct stat fields. Reported by Henning Verbeek.

After one week of campaign on -vote@, many subjects have been mentioned already. I’m trying here to list the concrete, actionable ideas I found interesting (does not necessarily mean that I agree with all of them) and that may be worth further discussion at a less busy time. There’s obviously some amount of subjectivity in such a list, and I’m also slightly biased ;) . Feel free to point to missing ideas or references (when an idea appeared in several emails, I’ve generally tried to use the first reference).

On the campaign itself, and having general discussions inside Debian:

• have those discussions on a more regular basis, outside DPL elections (from lucas)
• use polls to measure consensus (from lucas, question from mjr)
• use a pre-arranged questionnaire that DPL candidates would fill in (from algernon)

On getting new users and contributors to Debian:

• discussion on the various steps: Debian user – first contribution – regular contributor – DM/DD (from lucas)
• maintain a single list of “paths in” (from moray and lucas)
• have some “neutral” people to ask about tasks, and to get suggestions from in response to explaining their current skills and experience (e.g. http://www.debian.org/women/mentoring) (from moray)
• more local meetings, compile list of regional contacts (moray)
• increase Debian presence at local meetings. Advertise the Debian Events initiative that facilitates that (from lucas)
• provide “Debian ambassador” title for students, similar to what is done by Google or Microsoft (from moray)
• re-work on advertising gift tags (bugs suitable for new contributors) (from lucas)
• make sure teams have list of easy tasks in their wiki pages (from lucas)
• discussion on student projects involving Debian (from lucas)
• do mentoring inside teams, like DebianMed’s MoM (from moray)
• participate in other internship-like programs, like Outreach Program for Women (link from lucas), or organize our own, which would also avoid some restrictions from GSoC (northern hemisphere only (point made by moray), restricted to students (ana))
• extend internship-like programs to other kinds of work (packaging, documentation, etc.)
• localize -mentors@ (mailing lists + IRC channels for DE, FR, ES contributors) (from lucas)
• organize IRC schools/seminars about e.g. packaging (from lucas)

Infrastructure, processes, releases:

• improve infrastructure to help with team maintenance (e.g. PET) (from lucas)
• authorize NMUs for archive-wide changeovers such as /usr/doc -> /usr/share/doc  (from moray)
• increase visibility of RC bugs squashers by listing them in Debian Project News (from lucas)
• provide inexpensive non-monetary gifts (free t-shirts?) to RC bug squashers (from lucas)
• re-open discussion on gradual freezes (from lucas), focus attention on more important packages by improving tools (from lucas) and removing packages earlier (from moray and lucas)
• involve upstreams and downstreams in RC bug fixing (from algernon)

Relationships with upstreams/downstreams:

• use Debian money to sponsor maintainers to attend upstream events (from lucas)

This list could be moved to wiki.d.o if others find sufficiently useful to help maintaining it.

Dear project members, here's another report of DPL activities, this time for a period longer than usual (February + 1st week of March), so that the next one will be at the very end of the current DPL term.

Highlights

• As you know, we are now well within the DPL election process. And we have 3 valuable candidates running. I encourage all of you to participate in the discussions on -vote, and ask questions about project vision, goals, and improvements. It's something that is rarely as intense as during campaigning, so don't miss the chance!

• You might have noticed a sharp decrease in the count of RC bugs affecting Wheezy; that is largely due to the Release Team, who started the usual final sweep of RC triaging before release. Please thank them for their work, ... but don't give up on our collective work yet! You can still help up in the usual ways (NMUs, severity adjustments, unblock reviews, etc).

• The technical committee had to deal with a rather urgent issue during last month (#699808). I mention it here only to applaud their efficiency in doing so: 4 days to reach a decision. Resorting to tech-ctte shall always remain a last resort in Debian, but when it comes to that it's useful to know that we can count on a wise and speedy answer.

Appointments

• As the previous term was about to end, I've agreed with the Kurt Roeckx to re-appoint him as Project Secretary for another year.

• Following up to last month news, we've now assembled a team of admins for Debian participation into Google Summer of Code 2013 and delegated them for the task. Many thanks to David, Nicolas, Paul, and Sukhbir for volunteering, as well as to last year admins for their help in reaching out to interested volunteers.

  On a related note, we've until March 28th to propose projects and/or volunteer as (co-)mentor for GSoC 2013.

DPL helpers

Two more DPL helpers IRC meetings have happened, minutes and logs of both are available.

Assets

• I've worked with the press and publicity teams to announce the new trademark policy more widely and call for producing Wheezy merchandise. Apparently, we are now also being cited as a reference on how to strike a balance between free software and trademark (unfortunately the article is behind a paywall now).

• In related news, Brian Gupta has volunteered to help with answering trademark@d.o inquiries and has already helped a lot in streamlining the process and keeping track of past requests (thanks!)

• Following a -project inquiry by Thomas Koch, I've investigated with SPI the possibility of assigning to them the copyright for (code) contributions to Debian. The bottom line is that at present there is no safe way to do that with SPI; that might change in the future.

• As agreed at a DPL helpers meeting, we are trying to federate interests in Debian sponsoring and fund-raising. Part of the goal is avoid duplication of efforts DebConf- and sponsoring for other Debian activities; and part is establishing a more stable income flow for Debian (to ease long-term budget decisions). If you have experience and interest in this area, please join the debian-sponsors-discuss list on Alioth.

• Together with auditors, we have updated reimbursement procedures to better keep track of both outstanding and past requests. Main difference is that you'll now have to mail a RT queue instead of leader@d.o directly. Check the wiki page for details.

Events Past

At the beginning of February, I've attended FOSDEM 2013, together with many other Debian people. I didn't have any specific talk this year, but it's been a chance to talk F2F about several ongoing issues (see logs), and help mediating in some conflicts. I've also accepted the invitation to participate in the GNOME Advisory Board meeting, together with Laurent Bigonville of our GNOME team. No report of that has been prepared as of yet (sorry about that), but we have both reported "live" to the rest of the team on IRC.

Future

• It looks like my last month as DPL will be quite busy. Next week I'll be first in New York City, delivering an invited Debian talk at NYLUG (thanks a lot to Brian Gupta and Tom Limoncelli for the invitation). Then I'll head to LibrePlanet 2013 to talk about the relationship between Debian and GNU (thanks to John Sullivan for the invitation). Finally, at the beginning of April, I'll be in Amsterdam to deliver a talk about Debian experience with various legal issues across the years, at the yearly FSFE Legal and Licensing Workshop (thanks to Karsten Gerloff for the invitation).

  Both trips (LibrePlanet and FSFE) will be on Debian budget. While I usually insist on having travel sponsorship from inviting entities, in this cases I've accepted to do otherwise given they are free software non profits like Debian.

• I've been invited to represent Debian at Distro Recipes. Due to a conflict with FSFE workshop I couldn't make, so I've looked for substitutes. Lucas Nussbaum and Jonas Smedegaard have kindly accepted to go in my stead and deliver two talks, one about QA and the other about Pure Blends; thanks folks!

Miscellaneous

A couple of months ago I've mentioned that I had filed an application, as Debian representative, to participate in a working table to define software procurement rules for the Italian public administration. Good news: my application has been accepted, together with those of other well-known FOSS communities and organizations (e.g. KDE, FSFE). I'll keep you posted of how it goes.

Let's go back to elect a new DPL and release Wheezy now,
Cheers.

PS the day-to-day activity logs for February and March 2013 are available at the usual place master:/srv/leader/news/bits-from-the-DPL.txt.20130{2,3}

There are several ways to sell access to content on your Drupal site. One of the ways that hasn't been discussed much in Drupal tutorials is selling access to private Organic Groups with Drupal Commerce. 

As I needed this for my own project I hired Hibersh to create the Rule configurations for me. It worked perfectly ever since. As I saw other people struggling with achieving the same thing I decided to spend half a day writing this tutorial for you. I hope it helps you doing Drupal :)  

What you get

First let me discuss what you will get at the end of this tutorial:

Drupal users can purchase access to an Organic Group by purchasing a certain Drupal Commerce product.

You are going to make it so that you won't have to create a custom Rule for every Organic Group. You will have a 'universal' Rule configuration. Your site administrators or content admins can manage products and Organic Groups and the product -> Organic Group relationship and add and delete them as they see fit - if you decide to allow them to do that if course :)

Neat fact: buying 1 product can give access to 1 or several Organic Groups if you like.

To Make it Work

I've actually made 2 tutorials for you:

the Quick version: enable the example Feature and add a few nodes and you're done

the Drupalist version: learn how the structure works - knowing the right Fields and Rules configuration enables you to make it work for your own usecase. You will feel you've mastered a cool Drupal skill once you completely understand how this works!

the Quick version

Enable these modules: Organic Groups, Organic Groups access control (and Organic Groups UI). They are all part of the og project on drupal.org.

Download the selling_content feature as a zip file or through Git.

Enable the selling_content Feature on your site.  

Create 1 'Content Group' node,

Create 1 'Group Content' node and make it reference your 'Content Group' node.

Create 1 'Product for Organic Group' and make it reference your 'Content Group' node.

Done.

the 'Drupalist version'

Now let's have a look what we've actually built by enabling that selling_content Feature.

The Feature consists of a structure and a Rules configuration.

The structure

The Product Display -> Product reference

This is how most Drupal Commerce stores are configured. If you are not familiar with them, learn about them in this tutorial about Product Displays.

The Product -> Organic Group reference

This allows you to create a Drupal Commerce product and reference the Organic Groups it should give access to. Our Rules configuration below allows us to reference multiple Organic Groups from one product - or just one if your usecase needs to give people access to one Organic Group per product purchase. The Organic Groups need to be private and the content copies this behavior.

The Content -> Organic Group relationship

This is how most Organic Groups are structured: A content node with an Organic Groups field that makes it behave as 'Group content' and a group node with an Organic Groups field that makes it behave as 'Group'. The 'Group Audience' on the content node references the Group node.

the Rules Configuration

To make this work we'll have 2 Rules and 2 Rules components.

Rule 'OG subscribe after Product purchased'

This Rule in the selling_content Feature gives people access to the Organic Group if they completed the checkout AND made the payment for the order. In this example our 'Organic Group Rules' will act on the Rule event 'Completing the checkout process'. To make absolutely sure we only give paid users access to our group we've added a condition that checks of the order is paid. (Order balance comparison <= 0)

It's action loops over the line items and executes the Rule Component 'OG subscribe line item' for each of them.

Rule Component 'OG subscribe line item'

This Rule Component checks a couple of things in its condition:

the line item is of type 'product'

the product is of type 'Product for Organic Group'

The Organic Group Entity reference field is not empty

As action it loops over all the references field - that way we can reference multiple Organic Group nodes from one product node.

In that loop it adds the customer to the referenced Organic Group

That completed the Checkout part. You're done.

OG unsubscribe after Order Canceled

You probably want to remove users from the Organic Group when their order is cancelled for some reason - for example when they 'return' the product and want their money back.

That's exactly what the Rule 'OG unsubscribe after Order Canceled' is for, have a look:

When the order is changed (action) and its 'state' is set to 'Canceled' (condition) it loops over the line items of that order. For every line item a Rule Component is executed.

Rule Component 'OG unsubscribe line item'

This Rule component works almost the same as the other Rule Component. The only difference is that it UNsubscribes the user from the Organic Group instead of subscribing the user to it.

Test test test

Keep in mind that this is only an example Feature and you may need to tweak it to make it work for your specific usecase. If you have suggestions about making it better suited for certain usecases, please share below so others can benefit from your knowledge. Cheers!

 

Category: Drupal Planet Drupal Commerce Drupal Organic Groups

I've a collection of about 500 bookmarks which I've barely touched for a few years. I started organizing them late the other night, because I'd been off work sick for two days and that was about the most I felt up for doing with a computer.

The intention was to "tidy" them, and then setup some way of syncing them across browsers/computers. In the end I didn't like any of the syncing plugins I could find - xmarks, etc - so I decided to take a step backwards.

I'd exported my bookmarks to HTML page, via firefox, before I started, and then later in a fit of pique I deleted the whole damn lot of them.

So now a few years worth of bookmarks are stored in a single HTML file. But wait, we can use revision control can't we? We can host that file on github/similar. We can rely upon merges to deal with conflicts - simple if we just add lines to the end, or delete lines.

Maybe that's the best way to store bookmarks? I updated the bookmark file to read:

<ul> <li tags="debian, personal"><a href="http://www.debian-administration.org/">Debian Admin</a></li> .. </ul>

Adding "tags" to the LI-container and then some simple jQuery code gave me the ability to search/filter the bookmarks and auto-populate tags.

A small example placed online here:

• http://www.steve.org.uk/Software/bookmarks/

The obvious comment is that this makes adding new bookmarks a bit harder, but we'll see.. The javascript works in the browsers I tested, and for those that have none the bookmarks will just be a simple unordered list which should be universal.

I expect the javascript could be improved by a real developer.

A boy died.

He knew he was dying. He tried to get help. We don't know if it occurred to him to switch off the modem and make a phone call, or if he was too weak to get up and do it. We know he sent an email.

He didn't type perfect English at the best of times, and as his life slipped away from him, he misspelled many things. He misspelled “ambulance”. He may have misspelled “diabetes”. That was all fine—the meaning was clear enough—but the bit where it gets tragic is that he misspelled “.net” in the To: line.

So instead of arriving at its destination, the NOC of his employer, where it would have opened up a ticket and been seen by a human at some point, the email bounced.

We will never know whether they could have or would have done anything in time. We will never know if, had whoever been on postmaster duty at his ISP at the time been paying attention, he could have been saved.

These things were debated angrily, by people struggling to make sense of something, but it changes nothing. The email bounced, and he died.