Drupal.org is a critical resource for anyone working with Drupal. However, for the new--and sometimes even for the not-so-new--Drupalist, the sheer scale of Drupal.org can make it intimidating and difficult to use. This post is the first in a collection of posts that will explore Drupal.org, its resources, and how to use them.
For those of us in New England, today is a day we are hunkered down in blizzard-like conditions pondering thoughts of the new year and what it has in store. At Isovera, we continually take cues from our clients to get a feel for how folks are approaching their web strategy for 2014 and beyond. As a Drupal-focused technology firm, we are very excited about what is on the horizon. Here are just some random thoughts about Drupal, etc. (with some possible helpful links from others) that you may or may not find interesting:
Today we have another quick screencast answering a question in the Q&A section of drupalcommerce.org. This user, golubovicm, has asked "Edit own products permission" is not working! First off, that's not the best way to phrase a question, but it does happen that a number of people are wondering how to set up a user to create, edit, and delete their own products. So, we've created a quick screencast to walk you through how to set this up.
One thing about Drupal 7 that people have a love-hate relationship with is the Features module. Features attempts to give you the means to export database-stored site settings in code that you can put into version-control and move from server to server. In Drupal 7 using Features, when you want to make a change to your Drupal site configuration, you would need to either update the feature or make sure that setting was in a feature and (re)create it. When deploying, you would revert your Features so that your site settings match what was in code. If only things were that straight-forward!
For those that don't know: LeadPages is awesome landing page creation software. (watch a demo here) It allows you to setup a professional landing page in no time, so you can get real results in no time! Signup here if you don't have an account yet (you need one for this tutorial).
LeadPage module for Drupal
At the time of this writing there isn't a Drupal module for LeadPages available yet.
But there is a way to have LeadPages pages on your Drupal website, your own domain! :)
It's not as pretty as a Drupal module for LeadPages would be, but it allows you to act now, to implement and get results. <--- can be very valuable :D
First: create a LeadPages account by clicking this link.2 - Download and enable these modules
Next, download and enable these modules:
(I'm assuming you already have your Drupal site up and running)3 - Create a landing page content type
In your Drupal admin page go to Structure -> Content Types and click 'Add Content type' (or go to example.com/admin/structure/types/add)
Name it 'Landing page' and setup your content type as you see fit and save.4 - Configure 'Landing page' as Static Page
go to Configuration -> Config static page (located at example.com/admin/config/content/static_page)
and check the box before 'Landing page' and save.5 - Configure a 'No filter' text format
Use with caution. Allow this filter for trusted roles only.
Go to Configuration -> Text formats and click 'Add text format' (located at admin/config/content/formats/add)
Name it 'No filter' and make sure only 'administrator' is checked. Click 'Save configuration'.6 - Set 'No filter' text format for the Landing page body field
Edit the body field of the 'Landing page' content type.
Check the box before 'Limit allowed text formats' and select 'No filter' as the only option.
And click 'save settings'.7 - Get the source code of your Leadpages page
After creating a page in your LeadPages account, publish it with the settings selected below:
When you click 'Download HTML' you'll get a .html file. Open that with a text editor. You'll need it's source code.8 - Create content and paste the source code
In your Drupal admin go to Content -> Add content, and click 'Landing page'.
Enter a title, and paste the HTML source code from step 7 into the body field.
You'll be taken to the content on your page for example example.com/node/3
Enter that into a browser where you're not logged into the Drupal admin and there you have it:
your LeadPages landing page on your own Drupal domain!
Bonus: the page will update on your domain if you edit it from your LeadPages account!
Make sure to upvote and comment on the feature request about the Drupal module for LeadPages here: https://support.leadpages.net/entries/23003809-Drupal-7-module-for-LeadPagesCategory: Drupal Planet
As you may have heard, Drupal Dev Days is going back to DrupalCon Europe 2008's host town Szeged, Hungary on March 24th to 30th, 2014! This is the ideal place for Drupal Dev Days, a whole week of sprinting with learning and participation opportunities plenty on Drupal coding and all the related technologies involved. Here are five good reasons to register for this event now:
- It is the biggest distraction-free sprint to work out remaining issues in Drupal 8 in the whole year. The sprint runs from Monday morning to Sunday night. Szeged wants to provide enough but also be out of your way to be awesome! For example, we booked the same venue up until midnight each day.
- We believe it is essential for a successful core sprint to have core committers on location. Szeged will have Alex Pott and Nathaniel Catchpole with Angie Byron supporting from home while we sleep. If you are a core developer in any capacity, having these two great leads directly at the same place is an amazing opportunity.
- Of course there is no requirement to be a core developer to attend! If you want to join the list of almost 1800 Drupal 8 developers though, Drupalize.me is flying in Joe Shindelar and Amber Himes to deliver the Community Tools Workshop to get you on board with all the tools and processes used in Drupal core and contributed module/theme development. Great new skill to have under your sleeves in 2014. There is not much hard about it once you get started.
- We are taking the BADCamp/DrupalCon labs concept and provide options for speakers to deliver 2 hour and 4 hour long workshops for a fuller deep-dive on development topics. Even if you don't want to be a developer of Drupal itself in any capacity, there is a good chance that if you earn money with Drupal, you would benefit from some of these deep-dives. This is a unique format that other events don't offer. (Admittedly we are short on submitted sessions so far. If you, yourself would love to deliver such a deep-dive or a regular session, see http://szeged2014.drupaldays.org/program/sessions, submissions close on January 15th (in 12 days)!)
- Szeged is a great cozy town! Many of those who have been there in 2008 asked us repeatedly to organise a come-back opportunity. Here it is and it only costs 30 EUR now! See our interview video on Szeged experiences at http://szeged2014.drupaldays.org/community/attendees. You won't regret coming.
With all these great reasons, what are you waiting for? Buy your ticket now at http://szeged2014.drupaldays.org/buy-your-ticket
In this episode, Addi is joined by Todd Nienkerk of Four Kitchens and Brian Skowron from Lullabot to discuss "consultancy scrum." We start off by briefly explaining what scrum and agile are, and then dive into the lessons learned about using this methodology in a client/vendor relationship, versus a completely internal product team.
What is a Drupal Drive-in? The idea is to have an un-conference-style one day event where attendees have the opportunity to propose topics for group discussions to fully prepared presentations. Each attendee will get to vote on the topics presented during the event.
If you want to learn more about the concepts and inspirations behind Drupal drive-in type events, check out the recent DrupalEasy podcast 119. Our very own Thomas Lattimore discusses his concept behind the Charlotte Drupal Drive-in event.
Whether you have a topic idea for the drive-in or not, you are invited to register today!.
I am really looking forward to seeing old Drupal friends and meeting new ones at the event. It will be a blast.Blog Category:
The application itself will be fairly simple. It will wait for you to click the "Select" button on the Pebble watch. Once the button is clicked, the app will grab your current latitude and longitude coordinates. It will then use the Services module to create an Article node and save the coordinates onto a Geofield on your Drupal site.
Let's get started!
Drupal 7.25, a maintenance release with numerous bug fixes (no security fixes) is now available for download. See the Drupal 7.25 release notes for a full listing.Download Drupal 7.25
Upgrading your existing Drupal 7 sites is recommended. There are no major new features in this release. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement.Security information
We have a security announcement mailing list and a history of all security advisories, as well as an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.
Drupal 7 includes the built-in Update Manager module, which informs you about important updates to your modules and themes.
There are no security fixes in this release of Drupal core.Bug reports
Drupal 7.25 contains bug fixes and small API/feature improvements only. The full list of changes between the 7.24 and 7.25 releases can be found by reading the 7.25 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log.Update notes
See the 7.25 release notes for details on important changes in this release.Known issues
None.Front page news: Planet DrupalDrupal version: Drupal 7.x
I met Anthony, aka @ircmaxell, for the first time at the PHP BeNeLux conference in early 2013. He was among the first people I spoke with on mic about PHP. Our conversation about PHP being secure was one of the seeds that grew into the "Power of PHP" series on Acquia.com, though you'll notice we were still calling it "PHP Myths" at the time. The series will be continuing in 2014, stay tuned to the Acquia podcast and the Acquia blog for more!
Classic Graphics bet big on Drupal. Our largest customers get their orders on time because we have built systems for them based on Drupal. Even though we're up to 300 employees now, with layers of management, the non-technical management still is aware that we use Drupal for custom development in part because Bryan and I heavily evangelized Drupal within Classic.Thinking ahead
One of the concerns we discuss at infrequent intervals is what Classic would do if Drupal ceased to exist or if Drupal is still the best choice for doing our custom development now and in the future for the types of accounts we're pursuing. Our considerations also have to include our guesses about how the community will adopt things like Symfony or what Drupal 9 might look like.
The recent acquisition of Classic by Imagine! Print Solutions raised the discussion again. The guys at Imagine! have largely bet their development platform on .NET. Should Classic now look to adopt .NET platforms, or vise versa. We pretty quickly concluded that was not likely, at least in the short term.
As a "printing company", the Classic and Imagine! sales teams obviously look for opportunities to put ink on paper, but companies who have failed to adopt computerized order management to match their customers' needs have been becoming extinct in the printing industry. A lot of big business still operate using spreadsheets that get emailed around between departments and edited by people instead of systems. The companies which are excelling in becoming service providers in addition to being a "print shop" can adapt their print manufacturing to a customized list of retail locations or to a particular grouping of kits.Pain
You shouldn't hire a new accountant until your current accountant is unable to complete their work in a normal workday. You ask your accountant to work a couple extra late nights and start looking for another accountant. Wait until the pain has reached its peak, then relieve it. In the meantime, there's a waiting period to put a job posting out, wait for responses, interview people, do background checks, hire them, let them give 2 weeks notice at their current place, and then train them. From the date you decide to hire a new accountant, you may be putting extra stress on your existing team for another 5-6 months.
In my experience, nobody spends big money on custom software development to manage sophisticated data workflows until they're screaming in pain. That's probably the result of some prudent money management, but it draws parallels to adding to your accounting department. By the time a software development budget is approved and a business analyst has writtens some vague specifications, the customer is already impatient. They're living their peak of pain. They won't want to wait for prototyping, agile sprint reviews, automated testing, continuous integration platform builds, VM spin-ups. etc. The better you can streamline all the overhead of project ramp-up, the closer you are to just working on solving the customer's problems.Insert: cinder block
In the situations where the project is already filled with hot, impatient people, the "when all you have is a hammer, everything looks like a nail" scenario applies. I think the best thing you can do in that case is use your hammer, but I prefer a slightly different view on the common analogy - using a cinder block; a hammer is much too elegant. A cinder block is a clumsy thing to carry around. If you've ever worked with cinder blocks for a long period of time, you'd also find they have fragile points that cause them to leave cinder block crumbs everywhere they go.
I also extend the analogy by introducing oak, the hard wood. Most construction projects for buildings take advantage of softer wood like pine. They're cheaper because soft wood trees grow quicker and are easy to work with. Even when you have the right tools, like a standard claw hammer and some hard-wood nails, driving a nail into oak is a tough task; you have to hit the nail harder, probably a few more times, but the nails are also much more likely to bend. Driving nails into oak simply requires more skill and patience than does pine.
Put it all together now. I think of development like driving a used nail into an oak board using a cinder block. Picture some skinny desk geek gently "tapping" a nail while awkwardly straddling a block. That's development. Even though he might know just where to put the nails, he's going to bend a lot of them.Using the ideal tools
The problem with development is that developers can't just drive to Lowe's, buy a claw hammer or an air compressor with nail gun, and return to the job site. Professional development is the culmination of years of practice, trial-and-error, and research. For a developer to leave their cinder block behind, they essentially engage in a process of researching all devices that could be used for hitting a nail, types of screws and screw drivers, rivets, whether its appropriate to be using wood or if they should switch to aluminum, then narrow down to one with is most appropriate for a specified budget, go to meetings about how to hold the hammer in the right place, how to apply safety equipment, and on and on.
Since the customer always wants their solutions now, as cheaply as possible, when all the developer has is a cinder block, it's best that they use it. Drupal has been my cinder block since 2004 and I continue to use it because it's been able to solve most of the problems brought to me. It may not be always the most elegant, but I know how to hold the Drupal cinder block in just the right angle to bend the fewest nails. I've built up muscles for holding the Drupal block. Drupal has a lot of flexibility to change and hook in custom code and I've spent a lot of time already figuring out how to use Drupal in a way to minimize project startup overhead.
I think in Classic's case, since we've invested heavily in Drupal and staff that specializes in Drupal, it continues to be the bet for our development in the next 3-4 year window.Preventing stale
Using your cinder block to hit all your nail problems isn't really all so bad because it's probably still the shortest, cheapest path to driving the nails. Keep researching and learning about other tools so you can occasionally hit the nails with a sledge hammer, the back of an ax head, or even a rare, standard claw hammer. PHP developers should probably be able to read some .NET code, try to take on some bug bounties for a node.js server, and write their own devops scripts in bash instead of trying to get a server admin to do it.Post categories Drupal
During TWBS development upgrade Drupal 7 core jQuery libraries into its latest version for Bootstrap is a must. BTW jQuery Update seems not my cup of tea because it give me too much trobule within previous site building experience: too complicated, bundle everything within its own archive (which I love to manage 3rd party libraries with drush make and Libraries API), and it is really too much for my use case. So why not just work out a simplified version?
After some research and development during Christmas holiday, I would like to introduce my helper module named "TWBS jQuery". The goal of TWBS jQuery is to provide a handy support for jQuery upgrade and act as the helper module for on going Drupal-Bootstrap-Remix development.
All replacement will be handled automatically. No additional configuration is required.Key Features
- Provide drush make file for library download
- Confirm library successfully initialized with hook_requirements()
- Upgrade jQuery related libraries as below version:
- Port from jQuery Update, upgrade conflicted .js implementation:
Download and install with drush manually:drush -y dl --dev twbs_jquery drush -y make --no-core sites/all/modules/twbs_jquery/twbs_jquery.make
Package into your own drush .make file (e.g. drustack_core.make):api = 2 core = 7.x projects[twbs_jquery][download][branch] = 7.x-3.x projects[twbs_jquery][download][type] = git projects[twbs_jquery][download][url] = http://git.drupal.org/project/twbs_jquery.git projects[twbs_jquery][subdir] = contrib Live Demo
For general and generic jQuery update functionality, you should always consider another jQuery Update module which started since 2007-04-26.
On the other hand you should consider about using this module because of:
- Purely design for assist TWBS, which means you will have the best compatibility when using both together
- Fetch libraries directly from original repository and handle initialization with Libraries API; jQuery Update bundle all libraries into it's own code repository and initialize manually
- Only support latest official version of libraries which result as no additional configuration required; jQuery Update support multiple version of jQuery
- Much simple implementation which handle all upgrade and replacement automatically; jQuery Update provide more customization options
Please feel free to test it out and comment with your idea. Let's enjoy simplified jQuery update experience ;-)Tags Drupal Development jQuery
Every day, millions of nodes are saved. It happens every time content is created, migrated, or updated. It's probably the most common content management task in Drupal.
But there are lots of ways you can change the node-save experience for your users, and there are many contributed modules that offer alternative approaches to saving nodes. Here are a few that I like.Add another
The Add Another module allows gives users the option to save a node while quickly creating a new one. You can choose to add the option to the admin form itself, or as part of the save confirmation message. It's great for those content types, like "Image" or "Video" for example, where your users find themselves creating a series of nodes in succession.Hide Submit
Occasionally you'll see an issue where an end user clicks submit on a the node-edit form and, being ignorant of the fact that the request is being processed, clicks submit several more times to see if it's broken. Sometimes this can lead to multiple form submissions, resulting in bad things like duplicate content. The Hide Submit module does one simple thing: Prevent forms from being submitted multiple times. It does this by disabling the submit button once it's been clicked, with settings to fade out the button, append text, or hide it all together. This prevents errors, but it also signals to the user that the submission is in progress, helping to alleviate a bit of the frustration.Publish Button
"Does the word "Save" mean that I'm saving a draft or does it mean that I'm publishing the content live?" While it may be obvious for those familiar with Drupal, the intent of the button isn't always clear for new users. The Publish Button module aims to make it more explicit by splitting up the "Save" button into two buttons: "Save" and "Publish". If a node is published, the publish button is replaced with an "Unpublish" button.Node Buttons Edit
What if you have your own idea on what button text should be used? You could use "string overrides" module for a universal approach to text customization, but the Node Buttons Edit module gives you a straightforward admin page for customizing the button text specifically. No need to incur the additional overhead if you don't have to.More Buttons
The More Buttons module gives you the option of turning on more buttons (shocking, I know), to further customize your content saving experience. For example, you may want a "Save and Continue" button to save the status of the current input while continuing to make changes. Or maybe you'd like a cancel button, to close the form altogether. If so, this module makes these (and other options) available to you.
So next time you see users tripping over the node saving workflow, remember that you, as a sitebuilder, have a handful of options at your disposal to make things a bit more clear.
I took over a Drupal 7 project building a web application for college students to upload original videos about their school, and for schools to manage, group, and share the videos.
It's a startup privately funded by the principal, and we are literally working on a shoestring. My previous experience with media in Drupal led the principal to contact me via LinkedIn.
When it came time to build a video playlist in Drupal Views for JW Player version="6.7.4071" (formerly known as Longtail Video), I found very little useful documentation. In fact, someone suggested that those who know how are not interested in sharing their knowlege. -- but not me
Back to the playlist: Site admins can mark a video featured by ticking a checkbox on the custom video content type. Now I want to display those featured videos as a playlist.
Angie and I were at Acquia headquarters in Massachusetts at the same time in the spring of 2013. This gave us the chance to sit down and chat in front of the camera about all things Drupal. Highlights from our conversation became two podcasts with accompanying video. In this part of the conversation, Angie talks about how she got into Drupal and more.
- Before we jump into it, I want to get a little background on Headscape, so that people know where you’re coming from. What kind of sites do Headscape typically work on?
- How big is Headscape?
- What other technologies do you guys build with?
- What was the driving factor behind going open source?
- What’s your role at Headscape? What do you do day-to-day?
- Paul and Marcus mentioned on the Boagworld Podcast that Headscape has put out a couple of Drupal sites recently. Which ones are those?
- Since you guys aren’t a Drupal-only shop, why was Drupal the right choice for these projects?
- Are you contributing anything back to Drupal.org?
- What problems have you encountered using Drupal?
- How did using Drupal make the development process easier or harder?
- Where do you guys host your sites?
- Ted Bowman
What type of projects or project aspects will make you choose another system besides Drupal? What make you choose WP? Custom Coded?
Could you ask if Ian sees wordpress as inferior / used for different types of projects than drupal.
Why not use drupal for all projects and drop wordpress / custom builds
Would be interested to know what drupal version they use and when they will consider 8 - 12 months or longer
Would be interested to know about their development process from dev to live
Have you heard of/used NodeSquirrel?
Use "StartToGrow" it's a 12-month free upgrade from the Start plan to the Grow plan. So, using it means that the Grow plan will cost $5/month for the first year instead of $10. (10 GB storage on up to 5 sites)
2014 is going to be a big year for Drupal. I spent a lot of 2013 sprucing up services like Hosted Apache Solr and Server Check.in (both running on Drupal 7 currently), and porting some of my Drupal projects to Drupal 8.
So far I've made great progress on Honeypot and Wysiwyg Linebreaks, which I started migrating a while back. Both modules work and pass all tests on Drupal's current dev/alpha release, and I plan on following through with the D8CX pledges I made months ago.
If you use Drush, it's likely that you've used the "drush pm-download" (or "drush dl" for short) command to start a new project. This command downloads projects from Drupal.org, but if you don't specify a project or type "drush dl drupal", the command will download the current stable version of Drupal core. Currently, this will be Drupal 7 with that being the current stable version of core at the time of writing this post.
But what if you don't want Drupal 7?