There was a MASSIVE deal when 7.32 came out as it patched a very serious security hole. If you're site wasn't patched within 7 hours, you could consider it hacked. We had all ours patched within 45 minutes.

Not keeping your website's security update patches applied will get you in trouble.

They still haven't updated their website, so if you wanted to hack them again, you could simply use one of these scripts: https://github.com/…/drupalg…/blob/master/attack/exploit.php

(P.S. I am NOT suggesting anyone should hack them - just illustrating how easy it is - be careful when you trust your sensitive information to others.)

If you're anyway interested, the theme to power their portal cost a whopping $48.

And it seems their server is running on PHP 5.2, which reached end of life over 5 years ago.

Each show will be a friendly conversation (lasting approximately 30 minutes) giving participants a chance to share their thoughts on a recent project, how it was built, what others can learn from it, and contributions made to the Drupal community from the project.

The site is complete in terms of functionality, some more theming is needed, and some more interviews need to be added to the backlog. I'm hoping to launch within about 6 weeks.

In the mean time, join the mailing list for updates and/or suggest a website for the podcast, or chat with me at DrupalCon Barcelona about participating in a show.

Thanks, and keep Drupalling!

(Oh, and the website is here: http://dscpc.mark.ie)

For example, you are setting some permissions for a certain role, you run the update but then realise there was another permission you should have enabled. Instead of adding another update hook, you can revert the update you just ran, amend your update hook, and then re-run the update.

Note*: this is only for reversible changes - like adding/removing permisisons; it will fail if the update had created a new field for example.

It's as simple as this SQL query:
update system set schema_version = XXXX-1 where name = 'module_name';

This means, you are telling your database to update the table 'system' using scheme_version 'XXXX-1' (this will be something like 7001 or 7137 or whatever N equals in your hook_update_N() function minus 1, so if the update was hook_update_7138 you would use 7137 where XXXX-1 is), and apply this update to 'machine name of the module'.

Note*: Do not try this unless you know what you are doing. Make sure you have a backup of your database in case things go wrong - of course you do, don't you?

*Note - notes were added from items left in the comments, to bring them to the body.

I try to live my life along the lines of open source philosophy. Actually, I try to live my life following the tenets of anarchism - no hierarchies, a system of relations towards others built on trust, friendship, helping each other, solidarity, and distributed leadership (if leadership is the right word here).

When I came upon open source software (specifically Drupal), I quickly realised that anarchism and open source software have so much in common. Drupal is distributed, it is without formal leaders (except Dries as project lead - I know, this is a very simplistic reading of Drupal's set up). Developers work in solidarity/cooperation with each other, sharing code and knowledge to build the best product we can. We are friends, we trust each other.

It was inevitable, then, that I would think an organisation such as CoderDojo was such a good idea. Many, many groups around the world. Everyone helping each other to learn. All sharing knowledge. However, living in a small town in rural Ireland, I wasn't sure it would work here - we don't have coders, we don't have a meeting room, we don't ... Hang on. Let's not be negative, let's give it a try.

So tonight, we have our inaugural meeting of Portumna CoderDojo in the local adult education centre. With use of the computer room. And me as mentor. And some more parents as supervisors. And about 20 kids ready to start coding.

This looks workable. And exciting. Wish us luck.

When site building in Drupal, I am constantly using the drush si (site install) command to rebuild the site and check that my new feature is working correctly. Whilst this is a great way to get the site re-installed in super-quick time, it has a built in security feature of creating a user called admin (fine by me) and a new password for this user (which I then change to something simple like "admin" - just for development purposes). This is quite simple:

drush user-password admin --password="admin"

When I'm given a new project to work on, the first thing I do with my local instance is set the admin password to "admin".

To speed things up, I decided to write a drush alias to make these two use-cases easier to manage (yes, I know, first world problems!). And then I thought, why not share this and some of my other aliases. So, here goes (with comments):

alias dr='drush' // general alias for drush
alias drcc='drush cc all' // clear all the caches
alias drup='drush up' // update core and contrib modules
alias drupdb='drush updb' // run update.php
alias dren='drush en' // enable a module/theme
alias drdis='drush dis' // disable a module/theme
alias drfl='drush fl' // list all features on the site
alias drflo='drush fl | grep Overridden' // list all overridden features
alias drfu='drush -y features-update' // update a feature - you must put the feature's name after this
alias drfua='drush -y features-update all' // update all feature
alias drfr='drush -y features-revert' // revert a feature - you must put the feature's name after this
alias drfra='drush -y features-revert all' // revert all features
alias drpad='drush user-password admin --password="admin"' // change password for user admin to admin

Note: to get these working, I put them in my bash_profile file. Every time I add a new one, I run source ~/.bash_profile to reload the file and make the alias available to drush.

What aliases do you use?

This will create an "Image Gallery" content type, with images within each gallery re-orderable by 'drag and drop'. Here we go.

You will need:

• Drupal 7
• Multi-upload File Field Widget (to allow your file fields to upload multiple files in one batch)
• Multi-upload Image Field Widget (to allow the above to upload multiple images in one batch)
• Colorbox
• Some rudimentary CSS

Technique

• First off, enable the modules listed above.
• Then we need to create a content type. In this case, we'll call it "Image Gallery".
• Next, we need to create an image field inside this content type.
  • Choose "Image" as the field type and "Multiupload" as the widget type
  • Set the number of allowed values for this field to "Unlimited".
• Create some image presets, such as:
  • Gallery Thumbnail (150px x 150px) - used on the gallery page to list the images in that gallery.
  • Gallery Full Size (1000px wide) - used in an overlay when Gallery Thumbnail images are clicked on.
• Go to your "Manage Display" page for this content type and for "Full Content" set the following displays for the image field
  • Label = Hidden
  • Image = Colorbox
    • On the colorbox settings, set "Content Image Style" as "Gallery Thumbnail" and "Colorbox Image Style" as the "Gallery Full Size"
    • There are some other options here as well. Feel free to experiment.
    • Click "Update".
  • Click "Save".

Now you are ready to create an image gallery. You may need some CSS to float the images left/right and set some margins/padding.

You can then use Views to list the galleries and link each item in the list to its corresponding gallery.

(Note: a version of this is available on Drupal.org.)

Creating your own Drupal installation profile is a great way to save time when building a new website if you have many features that you use again and again on projects, such as news content type, image galleries, rotating slider. It's a great way to store your configuration in code and build and rebuild your site while in development. It's also best practice if you want to share code and rebuilds between developers working on large projects.

So, how do ywou make an installation profile, the easy way? The easiest way to create an installation profile is to just copy one that comes with Drupal core and modify it. To do this;

• Open up your profiles folder, find the folder called "standard" and copy it, then rename it to whatever you want. I call mine "adfl" as I do work as a freelancer under the name "A Design for Life".
• Next, rename each file in your new folder from standard.profile to adfl.profile, standard.install to adfl.install, standard.info to adfl.info.
• In the .info file, edit the description to something more meaningful for your installation profile.
• Finally, open each file and replace the word "standard" in the code with the word "adfl".

You now have a working installation profile called adfl, but it does the exact same as the standard installation profile. Let's customise it.

In the .info file, you'll see a number of modules already installed, like so:

dependencies[] = block
dependencies[] = color
dependencies[] = comment
dependencies[] = contextual
dependencies[] = dashboard
dependencies[] = help
dependencies[] = image
dependencies[] = list
dependencies[] = menu
dependencies[] = number
dependencies[] = options
dependencies[] = path
dependencies[] = taxonomy
dependencies[] = dblog
dependencies[] = search
dependencies[] = shortcut
dependencies[] = toolbar
dependencies[] = overlay
dependencies[] = field_ui
dependencies[] = file
dependencies[] = rdf

We can turn these off by deleting some, like so (or simply placing a semi-colon before them to comment them out):

dependencies[] = block
dependencies[] = comment
dependencies[] = contextual
dependencies[] = image
dependencies[] = list
dependencies[] = menu
dependencies[] = number
dependencies[] = options
dependencies[] = path
dependencies[] = taxonomy
dependencies[] = dblog
dependencies[] = search
dependencies[] = field_ui
dependencies[] = file
; this is commented out dependencies[] = overlay
dependencies[] = rdf

Now, if you reinstall your website, you'll see that we only have the above modules installed. We can now add in some modules that we use on every website. Place these modules in profiles/adfl/modules/contrib. We add them like so:

dependencies[] = admin_menu dependencies[] = ctools dependencies[] = features dependencies[] = views

Keep adding whatever modules you need. Now, when you resinstall your site drush si adfl, you'll see these modules also installed. To add custom functionality, you create features, and then add those features to your install profile, like so:

dependencies[] = adfl_blog dependencies[] = adfl_views_blog dependencies[] = adfl_gallery dependencies[] = adfl_views_gallery

A new site install will have these features enabled as well. A site install gives some simple errors at the moment: since I don't have dashboard enabled, the blocks placed in the dashboard can't be placed. Opening the .install file, we can find where this is and delete it:

array( 'module' => 'search', 'delta' => 'form', 'theme' => $default_theme, 'status' => 1, 'weight' => -1, 'region' => 'sidebar_first', 'pages' => '', 'cache' => -1, ), array( 'module' => 'node', 'delta' => 'recent', 'theme' => $admin_theme, 'status' => 1, 'weight' => 10, 'region' => 'dashboard_main', 'pages' => '', 'cache' => -1, ), array( 'module' => 'user', 'delta' => 'login', 'theme' => $default_theme, 'status' => 1, 'weight' => 0, 'region' => 'sidebar_first', 'pages' => '', 'cache' => -1, ),

In the above case, we need to delete the array

array( 'module' => 'node', 'delta' => 'recent', 'theme' => $admin_theme, 'status' => 1, 'weight' => 10, 'region' => 'dashboard_main', 'pages' => '', 'cache' => -1, ),

Then, just keep building up your profile with features, theme, variable settings, etc. There you go, a custom installation profile, the easy way. (Might be better to start with minimal as your base, I'm only using standard for illustration.)

Come to Drupal Open Days 2014, 16-17th May, to find out how you can use Drupal for your next website or online application. This free event has a variety of guided training, presentations and small group discussions. You’ll learn loads, get your questions answered and meet some friendly people too.

Drupal is an open source CMS (content management system) that allows an individual, a community of users, or an organization to easily publish, manage and organize a wide variety of content on a website or application. http://drupal.org/

Full details at: http://2014.drupal.ie

The event is at the the Guinness Enterprise Center. This event is free, however registration is required.

*Note: I am in charge of organising speakers. If you have a session/presention to you like to give or be in attendance for, just let me know.

These days, it's quite simple - in Who Wants to be a Millionaire terms ("it's only easy if you know the answer"). These days, I use CKEditor. Why? Well, it's going to be in core for Drupal 8, so I thought I might as well get used to it, but since making that decision a year ago, I find it a very pleasant editor to use. Then there was a damsel person in distress on Twitter wondering how to install it, so I thought "time to jump into character and save the poor soul".

@AgentCD are you sure? I've never paid for it. Can you send a link to it being premium. Perhaps I should write a blog post on installing it.

@AgentCD are you sure? I've never paid for it. Can you send a link to it being premium. Perhaps I should write a blog post on installing it.

— Mark Conroy (@markconroy) December 11, 2013

So, here goes.

1. Download the CKEditor module for Drupal.
   1. This gives you a Drupal module to power the CKEditor WYSIWYG - it is NOT the editor itself, merely a bridge to it.
2. Download CKEditor library from CKEditor.com.
   1. Extract the .zip folder you get from this.
   2. This is the editor itself. You need the Drupal module from 1 above to act as a bridge to this.
3. Download the Libraries module for Drupal.
4. In your sites/all/libraries module, drop in the CKEditor folder that you have downloaded from CKEditor.com, so you should have sites/all/libraries/ckeditor
5. Enable the CKEditor and Libraries modules in your Drupal installation on your modules page.
6. Take a bow. That should do it, now you can go to admin/config/content/ckeditor on your website and start playing with your sexy new WYSIWYG.

The camp started off with Gary Hammond (@manonmir) from iterate talking about adopting Drupal as a business, with some advice that started a great discussion about "defending Drupal" - the need to promote Drupal as a platform but also to defend the attacks that are levelled against it from proprietory vendors and others. Following this, Alan Burke (@alanjosephburke) from Annertech gave an overview of their work on the Oxfam Website, work which resulted in a large increase of site activity and also revenue for Oxfam. Lastly for this morning session, Daniel Alb (@danielalbro) from Monsoon Consulting extolled the benefits of Responsive Web Design (RWD) over unresponsive and/or mobile web design. This latter presentation gave me reason to demo a small animation I created using breakpoints. See here (on desktop, then resize the browser).

After coffee, we were treated to a talk on CoffeeScript by Mark Horgan. If I ever become a Javascript guru, I'll look into that a bit more - for this weekend, I was happy to learn as much as I did and get introduced to Grunt at the same time. Heather James (@learningdrupal) from Acquia took the podium to give us a preview blow us away with a preview of Drupal 8 - responsive images, configuration in code, in-place editing, and more, more, more. We needed lunch after that.

Mapping with Drupal - the topic I most wanted to hear about - was presented by Feargal O'Kane (@gul) from BT48. Best presentation of the weekend - Open Layers, changing map settings/layouts, layers - need I say more? Well, to host a complex mapping website, you might need the help of our next presenter - Jochen Lillich (@geewiz) from FreistilBox, who spoke about building high performance hosting stacks for Drupal. Jochen was followed by Peter Woalanin from Acquia with an in-depth look at the hook and plugin system for Drupal 8. Now, time for more coffee and sandwiches, and then on to ...

... Alan Burke to give an overview of configuration in code for Drupal 8, assisted by Conor Cahill (@conorc) from Fluid Edge who took the reins as a trusty sidekick. Suffice to say, everyone was impressed.

On Saturday we spent the morning engaged in round table discussions about various topics such as Twig, CSS animations, Grunt and Phing, and more, before moving on to our AGM in the afternoon. Ah, the AGM and our voting structures - le's just say, we all know a bit more about "single transferrable votes" now (and coin tossing!).

No need to mention the social aspects, the chats, the drinks, the food, the shuttleboard, the (nearly) dancing in a late bar, "jacketgate" in a hotel toilet, and - ultimately - the fun of yet another successful Drupal Camp. Thanks to Ruairi (@Snakedog_101) for organising.