Welcome. My name is Jeremiah John, sf/f author & activist.I tell liberationist stories.. . . More About Me
It can be hard to tell why a mixin fails in a sass file. After all, if the mixin isn't included in your dependencies automatically as it was before, grepping for it in the files won't turn up anything.
I was using a child theme of Classy, running Drupal 8. It turns out that this particular generically-named mixin comes from susy 2.x, having been removed in susy 3.x.
I fixed this by setting the susy version number like so in package.json:
I had a very strange problem wherein I was not able to affect variables being passed to views-view-grid--my_view.html.twig.
On the method of disabling a block without recourse to path.
On the method of creating custom breadcrumbs: simply crumble stale bread and dip battered eggs into your bowl. But in Drupal.
I had a devil of a time figuring out where captioning was coming from on my entity embeds.
Another team member had set it up, and I was just kind of baffled as to why captions were being offered on my entity embed forms.
It turns out that if you turn on captioning, you just get it for free on all of your embeds, and it's not configurable.
But... I don't want it for free!
Bah. Humbug. This free software doesn't have the features I think it should.
Alright, so here's how you turn off captioning:
All of a sudden, on a commit which had nothing to do with drush as far as I can tell, drush stopped working on platform.sh. I got an error like this:
Sometimes, you've got a Drupal twig function that doesn't exist in PatternLab, and it prevents PatternLab from building.
You get this error:
Views has a setting to exclude the current nid from the URL from the listing one is currently viewing. This is essential when you have, say, a list of related nodes that are are defined by a category that includes the current node. If you don't exclude the current node, your current node will be listed in the "related content" block on itself. Well, obviously one is related to oneself, one thinks.
First, I tired to accomplish this through the UI with these steps, below.
So, your debug output isn't working.
You checked to make sure you followed all the steps here.
But still... no theme debug output. WTF?
Try turning on and off twig caching. For me, it seemed something was stuck or whatever. First turn it on:
It turns out that image style tokens are an easter egg of the regular Token module, ported in from the Imagecache Token module on this ticket.
Image style tokens don't show up in the media browser, and so you sort of have to guess at how to use them. I figured it out by studying the merged commit that added the functionality.
Pluralizing and singularizing words got very easy with the inclusion of the Doctrine Inflector class in Drupal 8 core.
The task at hand here is to allow the client to create a classed wrapper around multiple elements using CKEditor in Drupal 8.
The fundamental problem here is the CKEditor's built in "Styles" dropdown classes each <p> individually, while we need a class wrapping them.
You could probably make or install your own CKEditor plugin, but that's not what I did.
I did this with Javascript.
You never know when you're going to encounter data ravaged by clients, cast aside and mauled, an antelope passed by lions to jackals.
But fortunately, data is much easier to repair than a gaping wound.
Here's the SQL query I'd use to replace non-breaking spaces with regular spaces. You'll need to replace it with whatever your search term is:
Here's the controlling issue for adding timezone support to Drupal core. As of now, August 1st, 2017, it doesn't appear to be ready.
Instead, I just added a timezone field to the node using the Timezone module, then appended it to the date range on field preprocess.
This won't work for you if you have multiple dates on an entity with different timezones (you might want to try the patch linked above), but it will fit most use cases.
Over the last several days, I've railed in my head against the matroshka structure of Drupal entities. But when I tried to break out some helper functions, and when I realized what each of the different properties each entity had, I realized the complexities of entities were warranted. Life is complex, and thus Drupal is complex.
Entity references load a Media Entity, which load an Image from an image field, which load a File. The alt and title are on the Image, while the file URI is on the file.