The today’s workaround is for the bug in “node preview” functionality. It is not frequently used, but can be rather convenient for large websites with moderation enabled. The bug can be spotted only when CSS styles, applied to the node/page template rely on the <body> CSS classes, namely the core-added page-node-type-[node bundle] body class. It helps to effectively distinguish different node templates, and therefore are widely relied on by front-end developers. However, in preview mode, this class appears entirely missing, which breaks the styling.
We spend a good deal of time touting our work for “bigger” clients – but we take just as much pride in our work for the “smaller” ones. Over the years we have done lots of work for non-profits like NYC Swim and the Byrd Hoffman Water Mill Foundation and we’re pleased to have recently added the Five Boroughs Bicycle Club to our client roster.
By default, the migrate module in Drupal 8 updates existing nodes by completely overwriting all the fields in the target node with the data from the migration. But what if your client has modified content on the target (D8) system, and still wants to update the content with newly-mapped fields? For instance, there is a “description” that has been updated after the first migration, but now the client wants “subtitle” field to be migrated (which was empty or not present during the first pass), without overwriting the description field changes. Continue reading
By resorting to YAML files for configuration, Drupal 8 achieved a huge boost in flexibility and understandability of the parameters. Even more it is useful for such a “commonly uncommon” task as migration.
Indeed, in D7 you had a set of forms to match source to destination, using some limited set of processing options. Now, in D8, these three stages of migration are totally separated out, unleashing a (nearly) unlimited power of building processing pipes and referencing other migrations. Continue reading
It was completely unexpected. Out-of-the-blue I was asked today by one of my co-workers to write a blog post. I thought hard about which new front-end development tools I have been using lately, but couldn’t think of anything that had had a significant impact on my professional life recently. Then I looked at today’s date and I realized that it is my 20-year anniversary here at Boyle Software. These twenty years certainly had a significant impact on my life…
RhinoCo Fitness was founded in 2007 with the goal of making fitness more accessible by using connected technology to deliver essential tools, supplements, and training programs to people across the world. In 2010 RhinoCo partnered with Reebok to open the first Reebok Crossfit Gym, which quickly became the highest-grossing retail store for Reebok and a world-renowned fitness center for RhinoCo.
It’s a weird piece of Drupal 8 out-of-the-box behavior: each time after you AJAX-load a views block with exposed filter, you are scrolled to the top of the block! It’s especially tiresome for mobile device users… Is there a way that we can fix it??
Removing this behavior entirely is a massive improvement. Here is a recipe to circumvent the issue for Drupal 7 – but it won’t work for Drupal 8! But search no more. Here for you is the exact solution:
Those of you hosting Drupal sites on Acquia might come across this issue: enabling compressed cached pages leads to Varnish errors instead of redirects. As explained by Acquia support, this happens because Varnish tries to unzip zero-length response – and, naturally, then fails. Your options for solutions are to purchase a dedicated balancer configuration – or make the response non-zero (for instance, add the “Redirecting…” text into the body).