So let’s imagine the following taxonomy tree:
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
Although WannaCry, the massive worldwide ransomeware attack, is the biggest story these days when it comes to cyber crime, it’s definitely not the only issue causing problems for sites right now.
Last week, website security leader Sucuri identified code that appears to be WordPress API related, but is actually sending active cookie data to attackers. This is most problematic when the active user is a site admin because it gives someone the opportunity to create a new admin user which can be then used to do considerable damage to a site and/or gain access to user data.
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…
We’re seeing reports this morning that a massive security breach associated with WordPress 4.7.0 and 4.7.1 has apparently led to the defacement of up to 1.9 million pages across almost 40,000 domains.
Upgrading to version 4.7.2 should fix the issue and WordPress urges anyone who hasn’t already updated to do so immediately. WordPress actually announced the security issue in a blog post at the beginning of February, but apparently there are still many sites that either weren’t aware or didn’t realize how serious the issue really is.
If you or anyone you know is running a WordPress site, please make sure it is updated to 4.7.2 as quickly as possible.
I was always a bit skeptical of the whole Cloud IDE thing, that was until recently when I gave Cloud9 a shot. I must admit, I was surprised when I read the Engineering Orientation wiki page for one of our clients, Vroom.com, as it suggested I create a Cloud9 IDE account as part of my project setup. What??
I figured I’d give it a try…