A straightforward problem, but one I’ve wasted time on when setting up a D6 LTS site.
The site is currently not available due to technical problems. Please try again later. Thank you for your understanding.
If you are the maintainer of this site, please check your database settings in the settings.php file and ensure that your hosting provider’s database server is running. For more help, see the handbook, or contact your hosting provider.
The uncommented example line in default.settings.php is:
$db_url = ‘mysql://username:password@localhost/databasename’;
I spent some time verifying usernames/passwords and adjusting ansible scripts, what I hadn’t noticed was I need mysqli (Mysql Improved – which has been around since way with mysql v4.1.3), not mysql.
So remember to check the connection protocol as well as the credentials.
A fairly straightforward problem that won’t be unique to Drupal, but you may run into when migrating PHP applications from other hosts.
I was reviving an old D6 site that had been hosted on another ISP (Hostgator, as it happens) and on setting it up on Acquia DevDesktop (which is a local MAMP stack) found PHP wouldn’t execute as normal.
First, isolate the problem:
- i.e. do other sites besides this one, running on the same computer (typically you’ll get this problem on a local dev setup) work correctly?
- create a test PHP file (e.g. containing
<?php echo "Hello, world!"; or
<?php phpinfo(); and load it
Solution in my case:
- check the .htaccess – it had the following, which was redirecting all PHP requests to a PHP binary that didn’t exist. Once commented it out PHP could run correctly.
# Use PHP56 as default
AddHandler application/x-httpd-php56 .php
Of course any .htaccess files become irrelevant if you move your dev or production sites to Nginx, but it’s a good idea to read through it anyway.
Gitk is a built-in GUI repository browser for Git.
There are options, but to begin with, just launch it by typing
It’s fast and handy if you just want to quickly browse commits or staged/unstaged files and don’t have an alternative GUI app.
Also a useful companion if you’re doing interactive staging.
You can instantly search full commit messages (matching commits will be shown in bold, remember to set IgnCase otherwise the search is case sensitive).
You can also use the touching paths option to look for files affected by a commit, and you can search by strings added or removed or changing lines matching.
There’s a second search box for finding things in the diffs.
You can modify colours, fonts and so on.
NB: Sourcetree has command line tools as well (so you can type
stree, though I couldn’t get them to install properly when I tried).
I’ve been trying Tailwind CSS recently. I’ll likely to continue using it.
People talk about Component First vs Utility First CSS frameworks – in my opinion the important word here is “first” – you should use your own best judgement to combine the two techniques.
- Start prototyping the design using atomic styles.
- Observe where you’re reusing the same styles a lot and/or it’ll be a pain (e.g. paragraphs of body text)
- Build components for these using
@apply in your CSS file (between
@tailwind components; and
- Don’t bother build components for things you are unlikely to reuse.
Does the HTML source code look a horrible with all those styles?
A bit when you very first see it. But:
- most code you didn’t write yourself looks confusing initially
- maybe your CSS file looks confusing close up too
There are several ways Utility First can save time:
- You’ll be switching back and forth between HTML and CSS rather less
- There won’t be as much friction in the early stages of building the site (you’ll be plugging in atomic classes and seeing the results straight away, you won’t be worrying about how to name things or constructing BEM selectors) – however you should keep an eye out for when you need to build a component.
- Obviously for a while you’ll be referring to the framework’s documentation a lot to learn the class names, but in the case of Tailwind CSS there’s an autocomplete search field on the site. The abbreviations for margin, padding, flexbox etc., once learnt, are logical and easy to remember.
- I find specifying code for screen breakpoints a lot simpler (typically I end up with lots of nesting in conventional CSS/SASS).
- No maths needed when building grids etc.
Can you still customise everything?
Yes. Your tailwind.js config defines everything – colours, breakpoints, font sizes, font families, leading, the grid etc. etc.
Who’s it good for:
- Developers who aren’t working in CSS every single day and can’t remember the intricacies of flexbox or grids.
- Anyone who doesn’t want their site to look like every other Bootstrap site (or any other framework that comes with pre-built components)
Can you still use it with SASS?
Yes (my typical build process for static sites uses Gulp and PostCSS)
There are two aspects to this, the CSS file size/download speed, and the speed the browser can process the quantity of selectors in it.
By default Tailwind will generate a very large CSS file with several thousand selectors. But with a little optimisation (turning off unused colours and screen sizes) you can dramatically reduce this. Also, the size is modest if served minified and gzipped.
Here’s a gulpfile.js, tested with gulp.js 4.0.0 and BrowserSync 2.26.3
It also uses the Tailwind CSS framework.
View example gulpfile.js on GitHub
Here’s a good beginner’s guide to Gulp (although the syntax for task execution has changed in 4.0.0, you need to use gulp.series or gulp.parallel)
Update – Sep 2019: PECL memcached extension v3.1.0 and above support PHP 7.3
Just a note that the PECL memcached extension doesn’t work with PHP 7.3 yet, you need to stay on PHP 7.2.
This is the error I got when trying to running
sudo perl install memcached (along with several sasl deprecation warnings):
/private/tmp/pear/install/memcached/php_memcached.c:1284:20: error: expression is not assignable
NB: Also, don’t get memcache and memcached mixed up when searching extensions.
I had a site using WPML (WordPress Multilingual) where the site’s language picker was set to English but a Chinese translation was consistently showing up for one particular item.
This turned out to be a simple case of the wrong language being set for the post in the database, but to the best of my knowledge you’d never be able to find that out from the UI.
Fortunately it’s easy to detect and fix with some simple PHP and SQL – the examples below use WP-CLI commands.
Firstly, you can use
wp shell to verify the language the post is set to.
The language is stored in the wp_icl_translations table, where element_id = the post ID. So, using
wp db query:
update wp_icl_translations set language_code = 'zh-hans' where element_id = 123456;
The above sets the post language to Chinese, which means it won’t be visible when the English version is requested.
Remember to clear any caches you are using.
Sandbox modules don’t have a drupal.org/project/foo URL like full contrib modules, and therefore you can’t use
composer require drupal/foo to add them.
If you have a Drupal 8 site using drupal-composer/drupal-project, here’s what to edit in composer.json – using a sandbox module of mine as an example.
- Within the repositories section
2. In require (or run
composer require with the name you’ve specified)
You can choose any name you like, but drupal-username/module makes sense to me.
Your sandbox module doesn’t need a composer.json file of it’s own.
Regardless of your ‘auto play’ setting, Amazon Prime Video displays a “Next Up” box bottom right, with movie artwork, on reaching the credit offset point; because, after spending perhaps more than two hours watching a film, who doesn’t want immediately want to start another?
Here’s the adblock rule you need:
(i.e. you’re blocking div.nextUpWrapper)
It’s worth noting the version of MySQL that comes installed with Acquia Dev Desktop 2 (5.6.41-84.1) is still 32-bit (unlike PHP which is now 64-bit). Recently I was testing with a particularly large database and found it kept crashing with things like:
‘MySQL server has gone away’
Lost connection to MySQL server at ‘reading authorization packet’
Intensive operations such as Drupal-to-Drupal migration tended to trigger this.
I used MySQLTuner but the changes made little difference so then it occurred to me the 32-bit version simply wasn’t up to it, so I installed the latest 64-bit mariadb from homebrew instead and moved the relevant databases over to that (I have mariadb running on port 3306 and Dev Desktop’s MySQL on it’s default 33067).
So far it’s been stable.