DrupalCon LA was a complete blast. In addition to exciting announcements, amazing sessions and tons of fun side events, there were also a lot of super productive sprints that really pushed Drupal development forward. In the Drush sprints, the remaining issues tagged for Drush 7 were all reviewed, and either resolved or deferred, cumulating in the release of Drush 7.0 Stable today.
If you’ve spent much time upgrading older websites to PHP 7, it’s likely you have encountered the annoying situation where PHP notices are printed directly into the HTML output, causing them to display in an ugly, unformatted jumble at the top of the page. The effect looks something like this:
Recently I wrote about how to prepare your site and import it into Pantheon’s new WordPress platform. This process works well for smaller sites. However, if you have a large WordPress installation, the process may not work. The Pantheon Importer has a limit on the size of files it can process. If you are uploading the file to Pantheon, the limit is 100MB. If you are giving the Pantheon Importer a URL, the file cannot be larger than 500MB.
As web developers, when we get hired to make a website, we might forget the driving assumption behind that expense: companies believe a better website will help them make more money. Why else would they be willing to invest in development, design and ongoing maintenance other than a belief in the potential of a return on their investment?
WordPress multisite is a great tool to streamline website management while providing site owners with some versatility. At its best, multisite is the perfect solution for managing multiple websites at once.
But, a multisite certainly isn’t a one-size-fits-all solution. There are some caveats. Before we celebrate or dismiss it, let’s take a look at multisite and see what it’s all about.
This post is for development teams tackling their first non-trivial Drupal 8 build, with multiple developers, and a timeline of several months.
Teams that build websites and marketing projects are often distributed geographically or across groups. It's common to have multiple internal and external collaborators, whether that's IT, marketing and a vendor, or a small business owner and a few independent contractors. Increasingly, these different players are spread out across the globe.
We’ve all had that moment where we have content in our live environment and want to add a new plugin or feature to our site. However, we need to test this new feature in a development environment first before deploying it to our live site. You do all the work to configure the plugin and then realize all of this configuration is saved in the database and you are in no position to override the live database. What do you do?!
While working with clients and helping them create awesome websites, we’ve noticed a need for an outgoing static IP. Pantheon’s cloud architecture is awesome—based on Linux containers, it allows us to scale easily, migrate containers, restart them in just seconds without any customer impact, resize them, and so on. The downside of having such great flexibility is not being able to assign a fixed IP address to a container. This is sometimes needed by third-party applications that only accept connections from services they know about.
Perhaps you've heard the news surrounding "secure" websites? A secure site is better for your users. Their data (and yours) is safer. Google adds new rules all the time that could affect your search engine ranking. Luckily, most hosts offer an easy way to turn HTTPS on. You could even get a free SSL certificate through Let's Encrypt.
So let's say you do that: you enable SSL on your domain. How do you make sure your WordPress site is secure? Specifically, how do you make sure you don't get Mixed Content messages?