macOS 10.13.4: Welche eGPU-Setups funktionieren (sollen)

heise online Newsticker - 5. April 2018 - 8:30
Apple hat Details zu der in High Sierra nun offiziell verfügbaren Unterstützung für externe Grafikkarten genannt – und gibt Empfehlungen zum Kauf.

Apple bringt angeblich ab 2020 eigene ARM-Chips statt Intel-Prozessoren für Macs

heise online Newsticker - 5. April 2018 - 8:30
Insidern zufolge soll Apple in den kommenden Jahren bei seinen Rechnern den "Switch" weg von Intel-CPUs planen. Der Umstieg soll in mehreren Schritten erfolgen.

beA: Besonderes Anwaltspostfach nach neuen Sicherheitsproblemen bis mindestens Mitte Mai offline

heise online Newsticker - 5. April 2018 - 7:30
Erste Ergebnisse der Sicherheitsüberprüfung des besonderen elektronischen Anwaltspostfachs legen neue Probleme offen, an deren Behebung der Dienstleister Atos arbeitet. Das Gutachten soll Mitte Mai vorliegen.

Googles KI- und Suchmaschinenchef legt sein Amt nieder

heise online Newsticker - 5. April 2018 - 7:00
John Giannandrea zieht sich wohl von der Spitze von Googles KI- und Suchmaschinenteams zurück. Über die genauen Gründe ist derzeit nichts bekannt, aber er bleibt dem Unternehmen anscheinend erhalten.

Hook 42: Community in Harmony - Hook 42 gives back at DrupalCon Nashville

Planet Drupal - 5. April 2018 - 5:09

DrupalCon is one of the most exciting Drupal events all year, especially for those of us who enjoy working in the community. We really get to shine.

This year is no different. It’s nice to share knowledge through presentations, but there are many ways to give back to the Drupal Open Source project.

macOS 10.13.4: DisplayLink & Co. bleiben dunkel

heise online Newsticker - 5. April 2018 - 0:00
Apples jüngstes High-Sierra-Update kommt mit USB-Grafiklösungen nicht mehr zurecht. Probleme gibt es auch mit Apps, die den Desktop auf iOS-Geräte erweitern.

Colorfield: Drupal 7 to Drupal 8 migration with configuration entities

Planet Drupal - 4. April 2018 - 20:38
Drupal 7 to Drupal 8 migration with configuration entities christophe Wed, 04/04/2018 - 20:38 The migrate system is stable since Drupal 8.5.0, so this is a great time to review the migration tools provided by the community. This post does not cover migration from the UI, it focuses on partially customized migration that are runned with Drush. In most cases, you will probably want to review the content model a bit (you know, that content type or field machine name that does not actually reflect the truth since its creation, ...). The idea behind is to delegate the heavy lifting to Migrate Upgrade for migration template generation, then apply content model changes if needed.

Mac & i Heft 2/2018 jetzt vorab im Heise-Shop

heise online Newsticker - 4. April 2018 - 18:30
Themen: 50 ultimative Mac-Tricks • Retro-Kult • Extern speichern • 360°-Panoramen • HomePod • iOS 11.3, macOS 10.13.4 • Musik programmieren • Top-PC-Spiele auf lahmen Macs • Steuererklärung • iMac Pro mit 10/18 Kernen • Apple-Support

Pillen gegen Fettleber: Träger resistenter Gene helfen bei der Entwicklung

heise online Newsticker - 4. April 2018 - 18:30
In den USA helfen Big-Data-Genomanalysen dabei, Menschen zu finden, deren Genausstattung sie unanfälliger gegen Lebererkrankungen macht.

TIP Solutions: Why a critical security hole is actually not so bad?

Planet Drupal - 4. April 2018 - 18:28
First (before the problem)

If you have a Drupal site and this is the first time you hear about the critical vulnerability published on March 28 2018 read the two last chapters immediately.

During the last week in the Drupal community around the world there has been a hustle about the security hole which was named DrupalGeddon2 [1] [2]. This vulnerability was "highly critical" and got many people scared - unnecessary. This post tries to explain when the vulnerability will become a problem? When the vulnerability is actually not a problem and how to handle the situation right. 

DrupalGeddon DrupalGeddon2 tietoturva Planet Drupal

Zuckerberg zum Facebook-Datenskandal: "Wir werden noch Jahre brauchen"

heise online Newsticker - 4. April 2018 - 18:00
Mark Zuckerberg räumt ein, sein Unternehmen sei im Umgang mit den Daten der Nutzer zu idealistisch gewesen – und erwidert Kritik von Apple-Chef Tim Cook.

Dropsolid: How we installed a Drupal security patch on 1300 sites, stress-free!

Planet Drupal - 4. April 2018 - 17:28
04 Apr How we installed a Drupal security patch on 1300 sites, stress-free! Nick Veenhof Drupal

Yesterday a highly critical security issue in Drupal was released. The issue itself is considered critical, because, the way we understood, it makes it possible to execute code as an anonymous user. This could lead to a complete hack of your site and complete exposure of your content - or, worse, if your webserver is badly configured, a full-scale hostile takeover of your server. (More background info available here and here.)

The issue was announced to the Drupal community a week early, so our Dropsolid team had plenty of time to anticipate and prepare. Currently, Dropsolid serves 482 unique and active projects, which contain on average three environments. To be more precise, this gave us a whopping 1316 active Drupal installations to patch. These environments are located on 65 different servers. 45 of those servers are out of our hands and are managed by other hosting companies, such as Combell or even dedicated hardware on site with the customer. At Dropsolid we prefer to host the websites within our own control, but to the Dropsolid Platform this ultimately makes no difference. For some customers we also collaborate with Acquia - these clients are taken care of by Acquia’s golden glove service.

So, back to preparing to patch all the different Drupal installations. We would be lying if we said that all Drupal installs were running on the latest and greatest, so we used Ansible and the Dropsolid Platform to gather all the necessary data and perform a so-called dry run. This was a real-world test across all our installations to verify if we could pass on a patch and then deploy it as soon as we have confirmed that the patch works for all the versions that we have available on our Dropsolid Platform. For example, it verified if the patch tool is available on the server, it injected a text file that we then patched to make sure the flow of patching a Drupal installation would go smoothly, etc. Obviously we detected some hiccups as we were testing, but we were left with enough time to resolve all issues in advance.

Throughout the evening, we had plenty of engineers on stand-by, ready to jump in should something in the automated process go wrong. The entire rollout took us about 2 hours - from the release of the patch over verifying the patch on all the different Drupal releases to rolling it out on all sites and, finally, relax with a few beers. This doesn't mean we had it easy. We had to work a lot, but a lot of hours just to make sure we could handle this load in this amount of time. That is why we are continuously building on our Dropsolid Platform.

Those who joined our hangout could bear witness to exactly how comfortable and relaxed our engineers were feeling during the rollout.

You might ask, joined our hangout? What are we on about exactly? Well, since the Drupal community was in this together, I suggested on Twitter to all join in together and at least make it a fun time.

A few nice things that happened during this hangout:

  • Someone played live ukelele for us while we waited
  • Someone posted a fake patch and made everyone anxious, but at least it was a good test!
  • People were able to watch Dropsolid in total transparency how we coped with this patch and were also able to interact and talk to others in the hangout.

It made the whole evening a fun activity, as witnessed by Baddy Sonja.

Obviously this couldn’t have happened without the help of our great engineers at Dropsolid - and also because we invest a lot of our R&D time into the development of the Dropsolid Platform, so we can do the same exercise times 10 or times 100 without any extra human effort. Thanks to the Drupal security team for the good care and the warning ahead of time. It made a tremendous difference!

All our Dropsolid customers can rest assured that we have their backs, all the time!

If you are not a Dropsolid customer yet and you are interested to see how we can help you make your digital business easy, we’d be more than happy to talk. If you are running a Drupal site and need help with your updates or with your processes, we’d be glad to to help out and onboard you onto our Dropsolid Platform. You can keep your server contract while benefiting from our digital governance and expertise. Are you in charge of many many digital assets and feeling the pain? Maybe it’s time you can start doing the fun things again - just have a chat with us!

 

Get in touch

Intel bringt neue "Coffee-Lake"-Prozessoren und Serie-300-Chipsätze

heise online Newsticker - 4. April 2018 - 17:00
Für High-End-Notebooks und mobile Workstations erscheinen Core i9-8950HK und Xeons mit 6 Kernen und bis zu 4,8 GHz; außerdem kommen 28-Watt-Quads mit besserer Grafik, USB 3.1 sowie mehr Desktop-Chips.

Aus für edle UHD-Blu-ray-Player: Oppo stellt Produktion und Entwicklung ein

heise online Newsticker - 4. April 2018 - 17:00
Oppo Digital hat überraschend bekanntgegeben, keine neuen Produkte mehr zu entwickeln. Für die beliebten Player UDP-203 und UDP-205 soll es weiter Firmware-Updates und Service geben.

Falcon 9: Privater Raumfrachter "Dragon" bringt Nachschub zur ISS

heise online Newsticker - 4. April 2018 - 17:00
Der Raumfrachter "Dragon" ist an Bord einer Falcon-9-Trägerrakte des privaten US-Raumfahrtunternehmens SpaceX zur Internationalen Raumstation ISS gestartet. Neben Proviant für die Astronauten ist auch Material für wissenschaftliche Experimente an Bord.

Bundesverkehrsminister kündigt Gipfel zur Schließung von Funklöchern noch vor Sommerpause an

heise online Newsticker - 4. April 2018 - 16:30
Bundesverkehrsminister Andreas Scheuer will die großen Mobilfunkanbieter noch vor der Sommerpause auf einem Gipfel versammeln, damit die Lücken in der Mobilfunkabdeckung in Deutschland verschwinden.

Evolving Web: Structuring Content with Drupal 8

Planet Drupal - 4. April 2018 - 16:11
Structuring Your Drupal Website

Drupal has always been a strong content management platform. The number one reason we use Drupal is because it so easily adapts to our clients’ content models. It enables us to easily map and structure many different types of complex content.

Let’s look at how we go about structuring that content in Drupal, and how we use terminology to define, group and link different types of content.

Content Entities

In Drupal 8, every piece of content is an entity. To structure a site, you want to define different types of entities that will store different types of content.

Let’s take a publishing website as an example. We’re going to create entities for: books, authors, editions, interviews, reviews, book collections, book categories, and so on. You can start by drawing a map of all these nouns. I like mapping out content on a whiteboard because it’s easy to erase and change your mind and it’s bigger than a piece of paper.

Relationships

Once you’ve mapped all the different types of content that will exist on your site, identify the connections between them. Simply draw arrows arrows between the content types that are related to one another.

For example:

  • A book has an author (or multiple authors): draw an arrow from book to author

  • A book can have editions: draw an arrow from book to edition

  • A book can have reviews, interviews: connect these

  • A book collection has books: group books by collection

  • A book has categories: associate books with topics and categories

Entity Terminology: Bundles, Nodes, Taxonomy, Paragraphs, Blocks

Nodes, taxonomy terms, custom blocks, and paragraphs are all different types of entities. Each entity type has unique properties that make it better suited for different use cases and content types.

Here’s a breakdown of the most important Drupal terminology you need to know to structure your content:

  • Node: A page of content is a node, accessible via its own URL
  • Taxonomy terms: Used to categorize other content, taxonomy terms live in a hierarchy. They can be used to filter content and create unique landing pages.
  • Paragraphs: Content that lives within other content and doesn’t need a dedicated URL is a paragraph.
  • Custom Block: Any content that will be reused throughout the site becomes a custom block. You can also embed a block in a node.
  • Bundle: An entity sub-type is a bundle. Usually, bundles can have have unique fields and settings.
  • Field: A field is a component of the content, i.e. an ISBN, author’s name, or book title
Applying this Model to our Example Project

Here’s how we would decide which entity type to use for each content type:

  • Books and authors become nodes

  • Book categories become taxonomy terms

  • Interviews, reviews and editions could be paragraphs

  • Books and authors would be node bundles (aka content types)

  • A book category is a taxonomy bundle (aka vocabulary)

  • A book collection is a block bundle (block type)

  • Reviews and interviews are paragraph bundles (aka paragraph types)

  • A book collection that needs to be displayed on several pages becomes a block

Focusing on Each Entity to Create Fields

Once you’re looking at a book, you can start to think about what defines a book.

Ask yourself:

  • What information should it have?

  • Which information needs to be displayed?

  • How will we filter and order this content?

  • Will there be a single value for the field or multiple values?

List the various components of the content: title, author, ISBN, covers, genres, editions, reviews, interviews. Each of these will be a field.

Fields in Drupal can be single value (for example, each book has a single ISBN number) or multi-value (a book can have multiple reviews or authors). There are many other fields types that can store the content in a certain way that will affect how it can be displayed or used later (text, date, number, email, link, etc). A field that links one entity to another is a ‘reference’ field.

Information Architecture

So far we’ve talked about structuring your content using entities and bundles. But how do users actually access your content? When you’re building out your site map, you’ll probably picture top-level pages. These may link to dynamic lists of content, or they may have sub-pages that are added beneath them.

Linking to Content

In Drupal, we have three main ways to link to content: menus, views, and fields. In general, this is how we use them:

Menus are for static content: Menus are a static hierarchy of content. If you’re creating permanent content on the site that will be relevant for a long time, you’ll probably link to it through a menu.

Views are for dynamic content: Content that is ‘dynamic’ that will be added to frequently and is too abundant to add to a menu will probably be listed and linked to via views (the Drupal term for ‘list of content’).

Entity reference fields or link fields: You can also explicitly add a link from one content item to another using an entity reference field or a link field. For example, if you have a book and you want to have it link to three other hand-selected ‘related books’, you could create a ‘Content’ reference field for this.

You can go through your site map and figure out which pages are static (linked to by the menu) and dynamic content (linked via views). Landing pages tend to be connection pages. For example, a landing page might live in the menu, list a bunch of dynamic pages and also include explicit links to other pages via ‘calls to action’.  

Applying Menus and Views to Our Example

Using our example, you may have a static page for ‘About Us’, ‘Contact Information’, or ‘History of Publishing’. These would be created as pages and linked to via the menu.

You may also have a page that lists all the books and another that lists all the authors. Because your lists of books and authors are likely to change often, these lists should be created using views. When you add a new book or a new author, it automatically appears in the list.

Taxonomies make creating lists more interesting because we can create lists of content that are filtered by a particular taxonomy term. For example, if ‘prize winning’ is a book category, a taxonomy allows us to create a list of all the books that are ‘prize-winning’.

Finally, you might have a landing page for an upcoming book tour that includes details about the tour, a link to the book being promoted, and also links to other books by the author.

Conclusion

There are many more things to know to build a site with Drupal. But when you’re planning out your content, you simply need to be able to draw out the structure and communicate this with your team. Knowing the basic Drupal concepts will help you communicate clearly and think about the site’s architecture at a high level.

To read about a real-life project in which we built out book content in Drupal 8, read about our project for Princeton University Press.

+ more awesome articles by Evolving Web

Windows entschlacken

heise online Newsticker - 4. April 2018 - 16:00
Aufräumen auf dem Windows-Laufwerk ist riskant: Schnell sind Windows oder Anwendungen beschädigt oder gar unersetzliche eigene Dateien verloren. Wie Sie überflüssige Platzfresser aufspüren und beseitigen, hat c't zusammengetragen.

Darknet-Drogenhandel bedient "letzte Meile"

heise online Newsticker - 4. April 2018 - 15:30
Weil die Darknet-Märkte völlig jenseits staatlicher Regulierung operieren, gelten sie als ökonomisches Labor. Neueste Forschungsergebnisse wecken jedoch Zweifel an dieser These.

Mehr Sicherheit: Update für Arduinos Linuxboard Yùn

heise online Newsticker - 4. April 2018 - 15:30
Sicherer, robuster und endlich Open Source: Arduino hat ein Update für den Yùn angekündigt, der einen Linux Mikroprozessor mitbringt. Ende April soll es lieferbar sein.