It's Day 3 of DrupalCon, and so much has happened in the last 72 hours! From keynotes and two full days of recorded sessions, gallons of Stumptown, and let's be honest, sore feet from all the walking... well take a deep breath, because it's not over yet!
So, here's what happened yesterday...We built a website to help the tornado victims in Oklahoma
On Tuesday night, a team of volunteer Drupal developers gathered in the DrupalCon Portland coder lounge to build a website to help FEMA help the victims of the Oklahoma tornado.
Drupal is a lot like enterprise software. Before you think this is a bad judgement on Drupal or a slur please hear me out. It's more a description of Drupal based on my experience with it for nearly 8 years and my last couple years dealing with enterprise software. I want to dive into some specific points that may be good, bad, and even make us unhappy with some of the things that make us happy.
If you are a site builder or themer in Drupal, you might have a similar situation happen to you. You obtain a set of requirements for a content type, create all the necessary fields with semantic labels, and start building the displays and views. Great! Life is good. Now your project manager waltzes over to your desk to deliver an updated set of wireframes, and before you even get halfway down the page, you feel a breeze as you notice a person-shaped cloud of dust where your project manager just stood.... Read more
Symphony Blog: ST Fiddle, an organization Drupal theme, free-of-charge for anyone to use it for charity purposes
This organization theme was inspired by my talk with Kim McCluskey, the founder of SunInMyHeart.com, a charity fund. During his trip to Halong Bay, I have heard about what he did for SunInMyHeart to help orphanage children. So after the trip, I created this theme for organization and non profit purposes.
If you are interested in using this theme for your charity funds, please feel free to ask me and I will send you the package free-of-charge.
We have received many requests to download this theme. As we believe the use of this theme for your websites will bring alot of benefits to other people, especially for charity purposes, we have converted this theme to Drupal 7 and provide it free of charge. No more asking, just go to the theme page and click on the Download tab, you will be able to get it.Demo
See the demo here: Drupal theme ST Fiddle demo
I belive every sitebuilder already had the need to wrap multiple fields with some markup, for example to group them in a fieldset or simply to wrap them with a div to solve theming issues. The easiest way to acoplish that is to use the field group module, wich gives you a nice and handy ui integrated in the core field_ui. It comes with a common set of often used wrappers, like expandable fieldsets or even horizontal and vertical tabs.
The module itself is a great tool for sitebuilders and themers because it is easy to use and exportable with the features module.
Sadly the module is pretty old and it is very complicated to get new features in it, because so many sites already use the module. So everyone lived with the overload of classes field_group appends to its containers and the poor set of available markup. Yannickoo from Loom created a patch, wich allows the user to decide how the wrapper should look like, by simply adding the tag in the ui.
This looks somewhat like in the image above!
If you want to take advantage of this new feature, you need to download the latest development snapshot 7.x-1.x, instead of the stable release.
Credits are going to yannickoo for this great work!Weitere Bilder:
WYSIWYG in Drupal 8 is going to rock, simple as that. Practically all annoyances, complications and other stuff we have had to endure In Drupal 7 and earlier has been fixed. Read all about it and also watch Nate Haug's DrupalCon Portland 2013 session about the improvements here.
Unfortunately Nate also revealed that Drupal 8 will still automatically delete files when their usage gets zero. That is a bad thing and I'll explain why I strongly believe that.Read the full "Drupal 8 WYSIWYG and File Cleanup" post on www.tsvenson.com
Often times it is needed to create module specific custom tables to store persistent data. Drupal offers a set of hooks in connection to this. Most commonly used among these are hook_schema() and hook_update_N(). First hook, hook_schema() holds the structure of table in the form of PHP array.Google Plus One Linkedin Share Button Tweet Widget Facebook Like
Here's a quick video recap from Drupalcon Portland - Wednesday May 22nd. If you missed yesterday's recap, you can watch it here.
In this episode we continue learning about Drupal Commerce and dive into some of the layout aspects of building out Drupal Commerce product displays.
In this episode you will learn:
- How to modify the layout of a Drupal Commerce product display
- How fields are used to control the Drupal Commerce product display layout
This Drupalcon has in many respects been about winning the hearts of the user: There's a constant UX track installed for the first time at a Drupalcon; Dries has used his keynote to talk about the importance of improving the web experience management (with some UXy slides!), UX expert Karen McGrane was invited to give today's keynote on the subject of multi-device content.
Her point: Lots of the tools that we build give the user the illusion that the web is print. Instead of using WYSIWYG and other (misleading) instruments, users should be able to add metadata with longer legs, making content multi channel capable. And if there's just one thing you want to watch today: Chris Blow's magically athwart presentation on Design Ops:
Here is one more conversation I had at Drupal Camp Alpe-Adria in April, 2013. Ranko Marinic is from Croatia and has some great perspectives. He works as an IT consultant with a wide range of technologies and with Drupal "by night". He is studying economics and has become interested in the economic effects on local communities of implementing open source software. Ranko also talks about the moment he really started believing in open source as a social movement.ranko_final.mp3
Just a quick note that the St. Louis Drupal Users group chose to reschedule our normal meetup, which occurs every third Thursday of the month, to next week, the week after Drupalcon Portland. Last year, we had a meetup right after Drupalcon Denver and had a great turn out. Those who weren't able to attend learned what it's like to attend Drupalcon, and also got valuable insight into the sessions, keynotes, and other events surrounding this great event. This year, we have at least a few known members who are here at Drupalcon (along with myself for the first time), who will be sharing their experience with the group at next week's meetup.
So if you live in or around the St. Louis area, or know someone who does, please be sure to join us this Thursday, from 7p-9p at the Missouri History Musuem (more details about the meetup can be found here).Tags
Hey, that's not what I was thinking!
That's a very common complaint customers have with developers, when they receive the result of weeks or months of hard work. And it indicates a failure of planning.
We've found nothing that works better to avoid this result than to write up and discuss user stories in detail.
What's a user story? It's a description of the process a person goes through to get a specific result, and what happens along the way.Tags: Drupal PlanetProcessUser StoriesUMLQualityIndustry: BusinessE-CommerceEducationHealth CareSoftwareStory Type: Sustainable/Open Business
Mike Gifford is President of OpenConcept Consulting Inc. and co-founder of Open Source Alliance of Canada.
Personal blog tags: Drupalcrowd fundingDrupal 8
DrupalCon Portland 2013: DrupalCon Portland Day 2: See the group photo and watch Karen McGrane's keynote, "Thriving in a World of Change: Future-friendly content with Drupal"
Here comes the rain! DrupalCon Portland welcomes our attendees to Day 2, with breakfast sandwiches (look for the big black truck across the street from the Oregon Convention Center) and of course, cold and dreary Portland rain. Grab a Drupal branded hoodie and KeepCup from the DrupalCon bookstore (in room C121) to keep warm between sessions and so fellow Drupalers can spot you when running around the city later this week completing missions from our Photo Scavenger Hunt.
I'm sure the sentence 'There is nothing impossible in Drupal' is not something unfamiliar for your ears. This blog post is a proof of this statement. Here we, the Propeople Drupal Digital Agency team, will make an overview of the Organic Groups module, another useful and powerful module that is appreciated by many Drupal users and developers.
First of all: OG – what is this all about? I think the best example would be Facebook Groups. Have you heard about Facebook Groups? I bet you have. In most of the cases Organic Groups are similar. Creating groups – public or private, inviting members, posting content, commenting it. These sets of features are in the core of Facebook groups as well as in Organic Groups.
By using Organic Groups we can build an entire community platform similar to a forum, but with more social networking features such as notifications and connection between members. We also have advanced access management via roles and permissions, and the flexibility to create various types of content. On the project page we can see a list of websites that use Organic Groups, quite a few big names can be spotted.
Before creating an Organic Groups platform from scratch or implement it in an existing website, we have to figure out what do we want to have as main features and if they can be by the OG module pack.
Here is a list of necessary points and a short description for each of them on how to configure it in Drupal:
Creating Groups – the site administrator should be able to create group rooms.
After enabling the OG module we can define each content type, new or existing, as a group or as a group content. On the content type edit page we have a vertical tab called Organic Groups.
Groups are entities. Every user with the right permissions will be able to create groups. We can define multiple types of groups. If we create Public group and Private group content types we have different content types, so we can set different permissions and access levels.
Appoint a group owner – the site administrator should be able to appoint an owner of the group who will manage all the group settings, membership and content.
By default, the group owner is the author of the group node. But it is configurable. Every group node has an interface for managing subscribed people.
Group posts or group content - define various types of content and relate it with groups.
Defining group content is similar to defining groups. Organic Groups vertical tab that appears on the edit page of the content type has an option - Group Content where can set the target bundles. In other words we choose which group types to use as group content. Posting content in groups can be restricted via roles and permissions.
Commenting in groups – all group members should be able to comment.
As a node itself, groups and group content have the option to enable comments. Commenting in groups can be restricted via roles and permissions. Defining roles and setting permissions will give us the control we need.
Listing group content and group members.
OG modules pack comes with predefined views. We can use them to list group content or group members. Displays are Block and Content Pane so we have what we need. Great!
Notifications – send emails when user is subscribing and adding content.
The OG modules pack also comes with a predefined set of rules. We can send emails to user subscription. For adding content we need to define custom rules.
So, if you need a social-based flexible forum-like website, or you are just curious about the module, do not hesitate to install and configure Organic Groups today.DrupalDevelopmentTutorialsCheck this option to include this post in Planet Drupal aggregator: planet
More and more projects today are using CSS preprocessors, with Sass being one of the most popular out there. What exactly is a CSS preprocessor? It is a scripting language based on CSS that lets you do amazing things with your CSS. We have a new series out, Learning Sass and Compass, to get you up to speed on this new cool tool for front-end development.
Sooner, not later, you will end up in the Issue Queue on d.o. Its practically unavoidable if you want to get the most out of your relation with Drupal.
The more involved you get, particularly as a code developer or themer, you will find that you spend more and more of your time working on and jumping around between issues. The list of issues you are active in and/or monitoring is constantly growing.
At this point you have turned the issues queue into: Your Workplace!Read the full "Our Drupal Workplace: The Issue Queue" post on www.tsvenson.com
Here's a quick video recap from Drupalcon Portland - Tuesday, May 21st.
The hook_requirements (API Doc) hook allows you to define custom requirements for modules. The hook can be used to simply notify a site builder with an alert, this is how the Update manager module works. If you have the Update manager module installed and it discovers an out of date module, it'll display an alert that certain modules need updating.
As another example, in the past I've used the hook to display an alert if API login credentials were not available.
You can also define very strict requirements where the installation of a module is aborted when requirements are not met.
In this article we'll look at how to use the hook for install requirements that aborts an installation if the requirements are not met. Then we'll look at how to display an alert, similar to how the Update manager displays alerts.