https://fonts.google.com/?selection.family=Open+Sans
cd /usr/share/fonts
sudo mkdir googlefonts
cd googlefonts
sudo unzip -d . ~/Downloads/Open_Sans.zip
$response = trim(preg_replace('/>\s+</', '><', $response)); |
var mysqlDump = require('mysqldump'); | |
//npm install node-schedule --save | |
var schedule = require('node-schedule'); | |
var j = schedule.scheduleJob(' 12 * * * * * ', function(){ | |
// * * * * * * | |
// ┬ ┬ ┬ ┬ ┬ ┬ | |
// │ │ │ │ │ | | |
// │ │ │ │ │ └ day of week (0 - 7) (0 or 7 is Sun) | |
// │ │ │ │ └───── month (1 - 12) |
[Update 2024] - This gist is almost useless compared to Drupal at your fingertips. Will create pull requests to update that if something is not already there.
// Load file object
$file = File::load($fid);
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
In this snippet I've gathered some examples and cases about how to get taxonomy terms programmatically in Drupal, using always the same method and the same mechanics: get terms and then processing it in order to get only the required under certain criteria.