A few weeks ago I decided to rebuild this portfolio/blog site. The old site was running on Drupal 7, and I had long tired of the design; it was somewhat slow, too. Add to the mix a bit of boredom with the status quo and a desire to try something new and "lightweight," I downloaded the Laravel (v3) framework I'd been hearing so much about.
If you're getting the “Unable to send e-mail. Please contact the site administrator.” error on a Drupal site that's hosted on an Ubuntu server, there's a good chance you don't have postfix installed. Resolving this is quite simple:
sudo apt-get update
sudo apt-get install php-pear
sudo pear install mail
sudo pear install Net_SMTP
sudo pear install Auth_SASL
sudo pear install mail_mime
sudo apt-get install postfixAs part of converting my site from Drupal 7 to Drupal 8, I ran into an issue with the core CKEditor not supporting <code> tags. The tags display fine after the intial node save, but get filtered out on subsequent node edits, regardless of the "Limit allowed HTML tags" option in the text format settings. Google turned up various discussions dating back to Drupal 6 days with this very issue, with finger pointing between Drupal, CK Editor module, and the CK Editor library itself.
If you're used to relying on $_GET['q'] from Drupal 7 (& earlier), you might be in for a surprise with Drupal 8, as $_GET['q'] is no longer defined for any request. Instead, Drupal 8 ships with a series of helper functions:
current_path() - returns the internal Drupal path (ex. node/123)
Every webmaster has encountered spam; from account registrations, to contact form submissions, spam bots are constantly on the prowl for new targets. The usual approach to combating such bots is with one of the many available captcha tools, but they are all far from perfect, and with the abundance of services that have warehouses full of real people entering captchas all day (for spam bots to then use), they are often rendered useless.
It is a very common need to be able to enter a menu path similar to user/[uid]/profile in the Drupal menu system ([uid] being a dynamic argument for the user's id), but that's not possible out of the box, and there are no modules which provide this functionality.
Yesterday I got such functionality working by using the often-unknown custom_url_rewrite_outbound() function.
I have been hosting my sites on (& referring all clients to) MediaTemple for the last several years; it has (generally) been a pleasant experience - MT's control panel is second to none, and support is quite good, too. The only issue I've experienced with their hosting is speed. MT's hosting occasionally gets flaky, and results in very slow load times. I've noticed this happening for a few days every couple months, but for the last couple weeks my sites have been taking an average of 3-4 minutes to load.
Domain Access is a module which allows you to simulate Drupal's internal multi-site functionality; it is easy to set up, and even easier to use. This is (by far) the simplest way of sharing content (and users) between multiple sites. One of DA's downfalls is that it does not work with subsites in subfolders, meaning the structure of site.com and site.com/subsite is not supported. Due to very specific client needs, my project required just that - subsites in subfolders. "Not supported" was not an acceptable answer, so... here is my solution:
I just encountered a strange issue while switching between two development branches of the same Drupal site. On branch A the site worked normally, but on branch B none of the forms contained any fields. After much hair pulling, I narrowed down the difference between the two branches to a drupal_rebuild_theme_registry(); call in my theme's template.php file on (the working) branch A, and realized what was going wrong.
Any seasoned Drupal developer has undoubtedly, at one point or another, come across the infamous "white screen of death" (WSOD) issue. While there are many documented (common) potential causes for this problem, today I encountered a new one, and just like all the ones before, it was a huge pain to find it!
This command will move all files & directories to the parent directory:
find . -maxdepth 1 -exec mv {} .. \;
... it will throw a warning when trying to move the current (.) directory:
mv: cannot move `.' to `../.': Device or resource busyEvery developer knows and loves GREP, the great search utility available on all Unix-based systems; while it does a great job searching, the options are a little lacking. One such option is restricting the search to only specific file types/extension. Luckily that functionality can be easily wrapped up in a handy script.
Create the script file:
cd /bin
sudo vim grepp
(You can name the script whatever you want, I named mine "grepp" for easier typing!)
Paste the following code:
The Aptana Studio IDE (my drug of choice) generates hidden .tmp files whenever you edit a PHP or HTML file. These are used generate the HTML preview within the editor. For those of us who don't use the preview feature, these files can be a nuisance.
Preventing Aptana from creating these files is simple. All you need to do is set the "HTML/PHP Editor Mode" to "Source only" in the Aptana -> Editors -> HTML and Aptana -> Editors -> PHP sections within the preferences.
Alternatively, you can create a handy little script to manually remove all .tmp* files.
Today, while working on a new Drupal 7 site, I somehow managed to lock myself out. I knew the admin (UID=1) username, but could not for the life of me get the password right.
One of the most common questions on Drupal's theming forums is how to create an individual layout for a specific page or node. In this tutorial I'll show you how to do just that!
Let's start off by opening template.php in your theme's folder. If you do not have this file you're probably using a theme that is not powered by the phpTemplate templating engine, and as such, this tutorial will not be of much use to you.
By default, Drupal comes with 5 content "regions": header, footer, left sidebar, right sidebar, and content. In many cases it is convenient to have several additional regions for more granular control over content location.
Sometimes we need to have certain blocks to always appear above or below the content, so let's add a few new regions!
For Drupal 5.x:
Open the template.php file in your theme's folder and add the following function: