Submitted by jenlampton on July 12, 2022 - 6:22pm
NameCheap hosting will promise you "Free SSL" when you sign up for hosting, but it's a trap. What you get is actually the first year free, for a certificate that will cost you $9/year, plus all the frustration and developer time to manage renewals of that SSL certificate.
Let’sEncrypt, on the other hand, provides always-free SSL certificates. Many modern web hosting providers include SSL certificates from Let’sEncrypt, by default, with your new hosting plans.
Submitted by jenlampton on August 9, 2013 - 9:41pm
I don't recommend trying to stay 100% on top of all updates for all of your modules all the time. However, when a security update becomes available for one of your modules, you should certainly make that update as soon as is reasonable. And while you're at it, that might be a good time to bring everything else up to date as well. Below is my recipe for keeping modules on my Drupal sites up to date, by using two of my favorite development tools, Git and Drush.
Submitted by jenlampton on June 2, 2013 - 7:22pm
I use MAMP for my local Drupal development on my Apple computer.
If you would like to do the same, first download the most recent version of MAMP and install it locally. When you are done, you should have directories for both MAMP
and MAMP PRO
in your /Applications
directory.
To run the application, double click MAMP.app
inside the MAMP directory. Once it's up and running, you should see a MAMP widget with a cute elephant icon.
Submitted by jenlampton on March 16, 2013 - 8:23pm
Every once in a blue moon, you'll run into a problem with your Drupal site where the solution involves patching core. Start by making sure that you have a safe place to apply your patch. This would be a 'dev' copy of the website, either running locally on your own computer, or in a development environment on the same server (or one that's identical) to your live site. *Never* apply patches directly to your live website - *especially* core patches!!!
Submitted by jenlampton on March 16, 2013 - 8:21pm
Applying patches is easier than you think! Start by making sure that you have a safe place to apply your patch. This would be a 'dev' copy of the website, either running locally on your own computer, or in a development environment on the same server (or one that's identical) to your live site. *Never* apply patches directly to your live website!!!
For the purposes of the example below, we'll pretend we are patching the panels module.
1) Start from the root of your Drupal site.