In this video we look at the Protected Pages module for Drupal 7. This module allows for password protection on paths in Drupal. In other words, this module will prompt a visitor to a specific page to enter a password before they are able to see the content.
This is one of those modules that exists to just make this use case simple. There are a ton of other ways to accomplish this with permissions and roles in Drupal, but it is always nice to have a simple way to accomplish this task.Tags: DrupalUsersDrupal 7Drupal Planet
At the Drupal Association, we’re focused on making Drupal better for everyone. You may have heard that we are working to make the Drupal.org experience better for all of our visitors, but we’re not going to stop there. We also want to make DrupalCon a more valuable and inclusive experience for everyone.
For that, we need help from our friends in the Drupal community. We’re looking for people who work at companies that use Drupal, but don’t provide a Drupal product or service. Whether you’re in the C-suite at Twitter, a developer working for a small business, or a manager who oversees the running of a Drupal website, we want to talk to you.
If you fit this criteria and do not attend DrupalCon, and would be willing to speak with us, please fill out this contact form or leave us a comment. Megan Sanicki, our Associate Director, will be in touch with you shortly to talk to you about how we can improve DrupalCon to better fit the needs of you and your business.
Image credit to Alan Levine on flickr.
Have you ever wanted to put a border on an image or highlight a link for more information in a text field? It is possible to configure the Styles dropdown menu in your WYSIWYG editor to allow you to add styles to the content in a text field. If you don't know how to configure your Styles dropdown, here's how you can add multiple classes to an element using the HTML editor pane of the WYSIWYG.Disable the WYSIWYG
To edit the HTML in a text area:
Navigate to the page you'd like to edit
Last year, we reached a milestone at Cherry Hill when we moved all of our projects into a managed deployment system. We have talked about Jenkins, one of the tools that we use to manage our workflow and there has been continued interest on what our "recipe" consists of. Being that we are using open source tools, and we think of ourselves as part of the (larger than Drupal) open source community, I want to share a bit more of what we use and how it is stitched together. Our hope is that this helps to spark a larger discussion of the tools others are using, so we can all learn from each other.
Git is a distributed code revision control system. While we could use any revision control system such as CSV, Subversion (and even though this is a given with most agencies, we strongly suggest you use *some* system over nothing at all), git is fairly easy to use, has great...Read more »
I recently updated the PostBooks packages in Debian and Ubuntu to version 4.7. This is the version that was released in Ubuntu 14.10 (Utopic Unicorn) and is part of the upcoming Debian 8 (jessie) release.Better prospects for Fedora and RHEL/CentOS/EPEL packages
As well as getting the packages ready, I've been in contact with xTuple helping them generalize their build system to make packaging easier. This has eliminated the need to patch the makefiles during the build. As well as making it easier to support the Debian/Ubuntu packages, this should make it far easier for somebody to create a spec file for RPM packaging too.Debian wins a prize
Steve Hackbarth, Director of Product Development at xTuple, myself and the impressive Community Member of the Year trophy
This is a great example of the productive relationships that exist between Debian, upstream developers and the wider free software community and it is great to be part of a team that can synthesize the work from so many other developers into ready-to-run solutions on a 100% free software platform.
Receiving this award really made me think about all the effort that has gone into making it possible to apt-get install postbooks and all the people who have collectively done far more work than myself to make this possible:
- The Debian PostgreSQL packaging team making the PostgreSQL server, client libraries and related packages available to install and upgrade easily on Debian and Ubuntu.
- The Debian Qt/KDE packaging team providing the Qt libraries.
- Andrew Shadura originally started the Postbooks packaging and preparing patches for a clean build on Debian.
- Juliana Louback who created the JSCommunicator / WebRTC extension for xTuple's new web interface while working in Google Summer of Code.
- xTuple themselves, who have an ongoing and enthusiastic commitment to free software and are actively developing their new web platform on Github.
Here is a screenshot of the xTuple web / JSCommunicator integration, it was one of the highlights of xTupleCon:
and gives a preview of the wide range of commercial opportunities that WebRTC is creating for software vendors to displace traditional telecommunications providers.
xTupleCon also gave me a great opportunity to see new features (like the xTuple / Drupal web shop integration) and hear about the success of consultants and their clients deploying xTuple/PostBooks in various scenarios. The product is extremely strong in meeting the needs of manufacturing and distribution and has gained a lot of traction in these industries in the US. Many of these features are equally applicable in other markets with a strong manufacturing industry such as Germany or the UK. However, it is also flexible enough to simply disable many of the specialized features and use it as a general purpose accounting solution for consulting and services businesses. This makes it a good option for many IT freelancers and support providers looking for a way to keep their business accounts in a genuinely open source solution with a strong SQL backend and a native Linux desktop interface.
Migrate is horribly broken! Migrate works awesome! Both are true. (Yes!) So Keith Dechant reported migrating a live Drupal 7 site to Drupal 8. Melissa Anderson is migrating a Drupal 6 site and gets mostly bugs. How is this possible? Well, Keith was coding his way around bugs, not just using what core provided (this should be obvious since we do not yet provide Drupal 7 sources in core) and Melissa had a site builder approach to it. Both of them are poised to contribute: Keith will share his code for Drupal 7 in the sandbox and Melissa files great bug reports and writes documentation with tips of how to use xdebug to find out what's broken with a migration. At this juncture if you are not prepared for either you will have a bad time with using migrate. Otherwise, see, it works!
Weather.com is the highest trafficked Drupal site in existence, with over 1 billion unique visitors per month. The Weather Channel teamed up with Mediacurrent to migrate from their previous content management system to Drupal. Not only were we able to help The Weather Chanel adopt an open-source solution, but the new website has drastically improved page load times and reduced infrastructure requirements.Key modules/theme/distribution used: PanelsServicesWysiwygOrganizations involved: MediacurrentAcquiaTeam members: jeffdiecksSilicon.ValetKendall TottenkbasarabjamesrutherfordAndrew M Rileypaulmckibbenderek.derapsmrjmdmarkie
There are many paid and free Drupal training sites on the internet. To the best of my knowledge, none of them is open source. And I'm quite certain none of them is "ridiculously open."
In the first post of this series on Drush Make we looked at building a custom Drupal install profile on Acquia Cloud using Drush make. In this installment, we look at managing and updating the code in your install profile and deploying it onto Acquia Cloud. Keeping up with new releases is one of the most important aspects of maintaining any site and leveraging Drush make can dramatically reduce the effort involved with that process.
As things stand today, Drupal.org's mirror network is an essential part of the Drupal.org infrastructure. The ftp.drupal.org infrastructure hosts millions of files, serving everything from Drupal Core to contributed modules and themes, but it's beginning to show its age.
Our current FTP mirrors (co-located, in Oregon, Illinois, and New York) have been behaving erratically: projects have been failing to sync to the mirrors, being deleted before update, and sometimes disappearing from the mirrors for hours or days at a time. Even when working properly, the replication from the primary to additional mirrors can take as much as 45 minutes.
Compounding these issues is the fact that we do not have robust control or access to the existing architecture when problems arise.
So we've taken a step back to ask:
How can we deliver these files in a more reliable way?
On the modern web, the key elements of file delivery are:
- High availability
- Peering capacity designed for global delivery
- Fast replication
- HTTPS/TLS support
A Content Delivery Network is the answer to these problems, which is why we're evaluating MaxCDN to replace the ftp.drupal.org infrastructure.
But wait - does this mean the ftp:// protocol will no longer work?
Yes. The FTP protocol is aging as well...
- In the month of October 2014, ftp:// had 96 unique visitors. Of those 96 unique visitors, only 33 of them made over 10 requests.
- The ftp pathing differs from http, making the experience of using ftp:// confusing and inconsistent.
- Replacing the ftp:// protocol with http will enable us to secure Drupal.org with HTTPS across all domains.
How you can help
We need users to help us test MaxCDN as an alternative for file delivery. You can track the issue here, and help us by testing the MaxCDN based downloads. Please report back your findings (good or bad) and let us know if there are any showstoppers.
To test, add this line to your /etc/hosts file:
~$ sudo vim /etc/hosts
And continue using ftp.drupal.org as you normally would through Drupal.org project pages, drush dl, etc.
When my business partner, Paul Chason, and I joined forces over seven years ago we had a rather simple vision for Mediacurrent. We were convinced that open-source software offered a superior value proposition over proprietary, licensed based solutions. We had an ambitious goal of starting a digital agency that was going to revolutionize how companies thought about the way they managed their web properties. As Simon Sinek so eloquently describes, this was our "why" and purpose.
As AppNeta’s developer evangelist, I work with customers in five different programming languages to monitor application performance. Drupal is just one part of one language, but I’ll always have a soft spot for it because it’s where I learned to program. When I get a chance, I like to keep my skills sharp by contributing to the community-maintained TraceView integration module. Last spring, I decided to port it and learn Drupal 8 the hard way.
Like most Drupal developers, I’d never tried writing Symfony code or using Composer to manage packages. Before attempting it, I decided to research both Symfony in its own right and how it is being leveraged to rewrite Drupal. Thankfully, there were many rich tutorials on “the basics” even then, and, after a relatively painless porting process, I had the module running with a skeletal Symfony bundle inside it.
Initially, I relied on the same strategy as the Drupal 7 version of the TraceView module, which monitors hook execution time by installing two additional modules: an “early” module with a very low weight and a “late” module with a very high weight. As each hook was removed from core, I moved its implementations from the modules into the bundle and tagged that event with listeners at maximum and minimum priority.
One of the world's most trafficked websites, with more than 100 million unique visitors every month and more than 20 million different pages of content, is now using Drupal. Weather.com is a top 20 U.S. site according to comScore. As far as I know, this is currently the biggest Drupal site in the world.
Weather.com has been an active Drupal user for the past 18 months; it started with a content creation workflow on Drupal to help its editorial team publish content to its existing website faster. With Drupal, Weather.com was able to dramatically reduce the number of steps that was required to publish content from 14 to just a few. Speed is essential in reporting the weather, and Drupal's content workflow provided much-needed velocity. The success of that initial project is what led to this week's migration of Weather.com from Percussion to Drupal.
The company has moved the entire website to Acquia Cloud, giving the site a resilient platform that can withstand sudden onslaughts of demand as unpredictable as the weather itself. As we learned from our work with New York City's MTA during Superstorm Sandy in 2012, “weather-proofing” the delivery of critical information to insure the public stays informed during catastrophic events is really important and can help save lives.
Voices of the ElePHPant / Acquia Podcast Ultimate Showdown Part 1 - Cal Evans and I got the chance to sit down and talk (a lot!) at DrupalCon Amsterdam and talk about a range of topics we have in common. In this first part of a 2-part series, we talk Drupal, PHP convergence and the "PHP Renaissance", open source communities, proprietary v open source business and the ethics of helping, and more.Why PHP?
According to Cal, PHP has three things going for it:
It's been a while since the last DrupalCamp in Melbourne, so the community came together recently to share what they know. Here's a brief wrap up of the two day event.
It's been more than a month since Drupageddon so I thought I would post an update of my previous post.
Commands that help with auditing:
Showing files that have changed on the live server:git status
Looking for code execution attempts via menu_router:select * from menu_router where access_callback = 'file_put_contents'
Another possible code execution attempt via menu_router:select * from menu_router where access_callback = 'assert';
Showing which files are on the live server and not in version control:diff -r docroot repo | grep 'Only in docroot'
Looking for PHP files in the files directory:find . -path "*php"
Looking for additional roles and users:select * from role select * from users_roles where rid=123
Checking the amount of time between when a user logged into your site and their most recent page visit:select (s.timestamp - u.login) / 60 / 60 / 24 AS days_since_login, u.uid from sessions s inner join users u on s.uid = u.uid;
Commands that can help with recovery:
Apply the patch. Hotfix: (SA-CORE-2014-005)curl https://www.drupal.org/files/issues/SA-CORE-2014-005-D7.patch | patch -p1
End active sessions, i.e log everyone out.TRUNCATE TABLE sessions;
Updating passwords:update users set pass = concat('XYZ', sha(concat(pass, md5(rand()))));
If you need help regarding the recent drupal vulnerability feel free to contact me.
Latest security advisory was today.Tags: Tweet
If Barbie I can be a Computer Engineer taught us anything it taught us that Steven and Brian are nice guys. They just want to help, they know how to fix it, and they are there just when you need them to be. And worst of all they don't mean anything by it.
So what's a nice guy to do? You care, you retweet the awesomest feminist blogs, you were ON it during #gamergate. But on a human interaction level how does it go? Here are some ways that you can level up from just that nice guy that I don't call out on everything, but who secretly makes me sad, to awesome guy that makes my day well ...awesome.Read more
Hello again, young MacGyver!
In the previous issue you learned how to install Drush, Drupal, and contributed modules. If you missed it, make sure you go back and read Part One from the previous issue.Updates
Now that you've successfully installed Drupal and extended it with some awesome contributed modules, it's time to apply a few updates. With Drush, it is easier by far than any method you might currently be using.
Let's get started: Make sure you are working from the root directory of your website. That would be the directory where you find index.php, and I'm going to assume that location for the remainder of this article.
Issue the following command:drush pm-update
That command will check for new versions of core, themes, and all the contributed modules that are enabled on your site. A list of all available updates will be shown on the screen. Review the list and then press “y” at the prompt if you wish to proceed with the updates.
If you proceed with the updates, Drush will make a backup copy of all the out-of-date packages, download the new ones, and then run database updates, if any are required. It's all very quick and you don't even have to open an FTP client.
Alas, sometimes things go awry; often, very awry. That's why Drush stores a backup copy of the updated packages for you. Should an update fail, it will restore the previous versions and notify you there was a problem. Or, if you need to restore manually, you can find the backups in your user's home directory under “drush-backups”.
Now let's say you only want to update Drupal, but none of the contributed projects. Easy enough: this time only check for Drupal core. Let’s use the shorter version of the command, which I prefer:drush up drupal
The command “up” is short for “pm-update”. As in the first example, Drush will backup the installed version, replace it with the latest, and then run database updates, if any are required. In this case, we specified “drupal”, so Drush will only check for updates for Drupal core.
DrupalSouth is the biggest Drupal gathering in the Antipodes.
We'll be at the Melbourne Convention and Exhibition Centre over three days in early March 2015. March 5-7 to be exact.
Find out more at the website
The call for sessions is open, and we're trying hard to get the word out wide and far, to whisper in new ears, and encourage people of all sorts to share their ideas for sessions so we can create a truly wonderful, inspiring, engaging and fun program for this conference!
For those who may not know, Drupal is an open source content management system. It's used by people and organisations all around the world, for all sorts of web sites. It's also being used as back end application framework for mobile apps! It's amazing what Drupal can do.
Drupal events are the heart and soul of the community that makes Drupal. Bringing people together drives the project forward, and forges friendships.
But we're also part of the wider web. So we want to hear from all sorts of web specialists, not just Drupalists.
Please, submit a session, or simply help us spread the word. The deadline is looming and won't be extended. Get that proposal in by 30 November 2014. https://melbourne2015.drupal.org.au/program/session-submission