AMD Radeon RX Vega 64 und 56 angetestet: Rückstand verkürzt, heiß erkauft

heise online Newsticker - 16. August 2017 - 11:00
Die Radeon RX Vega 64 gelangt am heutigen Montag für 500 Euro in den Handel. Erste Testergebnisse zeigen: Trotz hoher Rechenleistung kann AMD nur zu Nvidia aufholen, aber nicht überholen. Der Preis: Eine hohe Leistungsaufnahme.

Elektroautos: Porsche entwickelt Schnell-Ladesäulen

heise online Newsticker - 16. August 2017 - 11:00
2019 soll der erste Elektro-Porsche auf den Markt kommen. Mit der Infrastruktur, die nun entwickelt wird, würde er schneller laden als die Konkurrenz.

Datenbank-Server PostgreSQL: Lücke lässt Anmeldung ohne Passwort zu

heise online Newsticker - 16. August 2017 - 11:00
Administratoren, die PostgreSQL-Datenbanken betreiben, sollten ihre Software updaten. Unter bestimmten Umständen können sich Angreifer an den Servern ohne Eingabe eines Passwortes anmelden, warnen die Entwickler.

Janez Urevc: Call for help with Media source plugin porting

Planet Drupal - 16. August 2017 - 10:42
Call for help with Media source plugin porting slashrsm Wed, 16.08.2017 - 10:42

As you may already know Media entity module entered Drupal 8.4 as Media module earlier this year. This was the result of years of hard work in contrib and core space. While the module stayed conceptually the same we used this opportunity to clean it up and refactor some things; mostly to make APIs even easier to understand and use.

Media entity comes with the concept of so-called source plugins (also called type plugins in the past). They are responsible for everything related to a specific media type: they have knowledge about their nature, about the way they should be stored and displayed, they are aware of any business logic related to them, etc.

There were many plugins already available before Drupal core decided to adopt the module and they mostly lived as separate modules in contrib space. Since the API changed a bit during the core transition all this plugins need to be updated. The process is pretty straightforward, but the number of modules that need to be worked on is quite high. This means that we'll need quite some help from the community to do this as fast and as effectively as possible.

Here is where you come in!

Are you interested in contributing but don't know how? Are you looking for a task that is relatively simple but not completely trivial? Then the porting of media source plugins might be a really good entry point for you!

There is a meta issue that is trying to keep the overview over the porting process. You will find the list of modules and their current status in it. In order to get familiar with the changes that were introduced during the core transition you should check the relevant change record. All information that is needed for ports should be available there. If you'd rather work with examples then take a look at Media entity image and Media entity document, which were adopted to core as Image and File source plugins respectively.

When you decided which module deserves your attention check its issue queue. If there is already an issue about the porting get involved there. If there is not create one to let others know that you are working on the port. In any case make sure to add its reference to the meta overview issue. This will help us to keep the general overview over the process.

Need help?

Have you checked all the resources I mentioned above and you feel that there are still things that are not entirely clear? Come to the #drupal-media channel on IRC. We are hanging out in that channel most of the times. Our weekly meetings happen in the same channel every Wednesday at 14h UTC.

Enjoyed this post? There is more! Results of the Drupal 8 media sprint Call for Drupal 8 media ecosystem co-maintainers Presentations about various Drupal 8 media modules

iX-Workshop zu OpenStack und Docker: noch eine Woche Frühbucherrabatt

heise online Newsticker - 16. August 2017 - 10:30
Wer Docker einsetzt, erledigt die Cloud-Integration oft mit OpenStack. Wie man die beiden Softwarepakete integriert, zeigt ein iX-Workshop am 4./5. Oktober in Nürnberg.

HTTP-Status 418 "Ich bin eine Teekanne" darf bleiben

heise online Newsticker - 16. August 2017 - 10:00
Der HTTP-Statuscode 418 "I'm a tea pot" war eigentlich als Aprilscherz gedacht und drohte, aus dem Netz zu verschwinden. Doch nun könnte der sinnlose Fehlercode sogar zum offiziellen IETF-Standard werden.

Gefährliche SSH-Befehle: Kritische Sicherheitslücke in GitLab

heise online Newsticker - 16. August 2017 - 10:00
Viele Versionskontrollsysteme haben eine Sicherheitslücke, die es Angreifern ermöglicht, Schadcode auszuführen. Beim Webfrontend GitLab ist dies besonders brisant. Admins sollten Installationen der Software umgehend aktualisieren.

Dank Tochter-Firma: Facebook analysiert Nutzungsdaten der Konkurrenz

heise online Newsticker - 16. August 2017 - 9:30
Dank einer vor einigen Jahren übernommenen Firma haben Facebook-Mitarbeiter einem Bericht zufolge Zugriff auf wertvolle Nutzungsdaten anderer App-Anbieter. So kann der Konzern die Konkurrenz analysieren und sich diese vom Leib halten.

DJI Spark im Test: intelligente Flugfunktionen, durchschnittliche Akkulaufzeit

heise online Newsticker - 16. August 2017 - 9:00
Die DJI Spark ist eine kompakte Drohne mit hochautomatisierten Flugfunktionen. Darüber hinaus kann sie per Handgesten gesteuert werden. Mit einem Preis von 599 Euro ist sie allerdings kein Schnäppchen. TechStage hat die Spark unter die Lupe genommen.

Breitbandausbau: EU-Kommission genehmigt Beihilfen für Vectoring-Projekte

heise online Newsticker - 16. August 2017 - 8:30
Auf Basis der Beihilfevorschriften hat die EU-Kommission grünes Licht für drei virtuelle Zugangsprodukte in Deutschland gegeben, über die der DSL-Turbo Vectoring in staatlich geförderten Breitbandnetzen genutzt werden kann.

Spracherkennung: Google erweitert die Cloud Speech API

heise online Newsticker - 16. August 2017 - 8:15
Der Dienst zum Umwandeln von gesprochenem in geschriebenen Text kann nun Audiodateien mit bis zu drei Stunden Länge verarbeiten. Außerdem gibt es 30 neue Sprachvarianten.

Standortgefahr: Industrie verteilt schlechte Note für den Breitbandausbau

heise online Newsticker - 16. August 2017 - 7:45
Die Unzufriedenheit der produzierenden Unternehmen mit der Breitbandanbindung nimmt immer weiter zu, hat eine Umfrage des Deutschen Industrie- und Handelskammertag ergeben. Die Politik unternehme zu wenig, dies sei ein "ernstes Warnsignal".

iPad-Smart-Connector: Geschäft kommt nicht in Gang

heise online Newsticker - 16. August 2017 - 7:30
Seit 2015 liefert Apple seine Profi-iPads mit einem magnetischen Anschluss aus, der die schnelle Anbindung von Zubehör erlaubt. Doch bislang nutzt die Peripherieindustrie ihn nur selten.

Spekulationen über Verzögerungen beim iPhone 8

heise online Newsticker - 16. August 2017 - 6:00
Einem Medienbericht aus Korea zufolge könnte Apples nächstes Top-Smartphone erst im November in ausreichenden Stückzahlen verfügbar sein. Es sind nicht die ersten Gerüchte über Verzögerungen bei dem OLED-Gerät.

myDropWizard.com: FREE migration to Drupal 8 for 10 nonprofits

Planet Drupal - 16. August 2017 - 4:01

Migrating your site to Drupal 8 isn't simple or cheap. Nor is maintaining it or getting support once your new Drupal 8 site is live!

This is a problem that affects all organizations using Drupal, but it's particularly hard on smaller nonprofits.

A couple weeks ago, I wrote a super long article detailing how Drupal 8 has left many small nonprofits behind. It also proposes a possible path for fixing it!

We're building an Open Source platform for nonprofit websites built on Drupal 8 and CiviCRM, available as a SaaS with hosting and support included.

That article was primarily about why - in this article I'd like to talk about the details of how!

There's a lot to discuss, but I'll try to make this article shorter. :-)

Oh, and we're looking for 10 adventurous nonprofits to join the BETA and help build it.

If you join the BETA, we'll migrate your existing site to the new Drupal 8 & CiviCRM platform for FREE!

Read more to learn about all the details we've got worked out so far...

Tameesh Biswas | Blog: Gsoc17 : Client Side File crypto : Week 11

Planet Drupal - 16. August 2017 - 0:16
Gsoc17 : Client Side File crypto : Week 11

This blog post summarizes the eleventh week of writing open-source code for Drupal with Google Summer of Code.

The module is finally complete with most of it’s major features. It is complete for testing and a bit more changes are to be made that have been discussed, suggested and some things that were planned and are left to implement.

tameeshb Wed, 08/16/2017 - 03:46 Tags GSoC Google Summer of Code 2017 Drupal Drupal Blog

ActiveLAMP: Drupal Modules to Help Improve Your SEO

Planet Drupal - 15. August 2017 - 22:00

So you just finished building an awesome new website on Drupal, but now you’ve run into a new dilemma. How do optimize the site for search engines? Search engine optimization, or SEO, can be overwhelming, but don’t let that cause you to ignore certain things you can do to help drive traffic to your website. There’s nothing worse than spending countless hours to develop a web application, only to find out that users aren’t able to find your site. This can be extremely frustrating, as well as devastating if your company or business heavily relies on organic traffic.

Read more...

Mediacurrent: Accessibility, Nachos, and a Responsibilities Document

Planet Drupal - 15. August 2017 - 21:17

I had this blog post written last week but didn’t publish because it felt wrong. It wasn’t until earlier today, when I was listening to one of my favorite public speakers, that I realized it was because I was talking at you, not to you. In truth, whenever I’ve discussed this document I keep talking about the what its purpose is and how it could bring value to our Drupal community but not why you should care.

Elevated Third: Decoupled Drupal Technologies and Techniques

Planet Drupal - 15. August 2017 - 20:17
Decoupled Drupal Technologies and Techniques Decoupled Drupal Technologies and Techniques Joe Flores Tue, 08/15/2017 - 12:17

Part 3 in this series is continued from a previous post, Decoupled Drupal: A 10,000ft View.

One of the main considerations when building the POWDR website was uniformity. POWDR is a holding company composed of many separate companies, all with individual websites. In order to ease the burden on content admins, we sought a solution that avoided multiple content types for each separate site. As a holding company with so many websites to maintain, managing many content types can become really complicated really quickly. It was our job to keep the content admins at top of mind in order to make their job updating the various websites as easy as possible.

Drupal Multisite for Easier Administration

The reason we ended up going with a multisite is that for each POWDR property there is a separate Drupal instance. In typical ski industry form, POWDR continues to acquire additional resorts and companies. They are constantly bringing on companies with different processes, different applications, and different third-party vendors. Many have different teams acting as admin. So, one of our first considerations was how people on the main POWDR team were going to administrate and edit all of this content.

We considered doing it all in one large API site though that plan quickly became too complicated when it came to permissions. Instead, it was decided that the project would be split up into multiple sites. Acquia made this process nice and easy. Using Acquia and Drupal 8, we were able to spin up a new multisite instance within the parent Drupal instance.

After some practice, we are now able to spin up a new instance in a matter of minutes. Using Drupal 8 and configuration, we copy the configuration from a parent skeleton site into a new site This allows the design team to start their development process with a basis on the API side without us having to reprogram and rebuild from the ground up.

Paragraphs Makes Complex Content Manageable

Working with Hoorooh Digital, we created an overarching entity structure using paragraphs that allowed us to make a baseline unit to build upon. Each paragraph was essentially a different piece of the website. They made components within Angular line up with paragraphs on the Drupal side. If you’re not familiar with paragraphs, in Drupal 8, their entities in and of themselves. This was nice for us because it allowed us to load and alter them programmatically, much like any other entity on the backend. They could be rearranged and served to the frontend from any site to meet design needs.

Implementation was one of the larger challenges of the POWDR project. The difficulty arose as we matched up the frontend to the Drupal backend. Custom code was required to ingest the paragraphs in the components. If you’re thinking about taking on this project, be sure to consider this step during the estimation process. In our experience, a good portion of the frontend development was required to render frontend components. We took the time to decide how componentry and paragraphs would be ingested from the Drupal platform, then matched up with the frontend framework. This allowed us to standardize all of the content coming out of the API so that frontends wouldn’t have to be rewritten for every site.

D8 and JSON REST API Decrease Development Time

The real power here was that, out-of-the-box, Drupal 8 does have a JSON REST API. We took that and ran with it. We realized early on that the Angular frontend and the out-of-the-box JSON API were going to require a lot of work to get them to work together. Instead of sacrificing this time, we extended the JSON encoder class in Drupal 8 and created our own POWDR format JSON encoder. This allowed us to create a serializer service and a bunch of custom entity normalizers. We then added related entities and some custom processing to meet the frontend needs. Out-of-the-box, the JSON API is built so that you’re requesting each related entity down the line. You get an entity ID and then you make another call to the API to get the content of that entity.

Essentially, what we did by extending the JSON encoder and all the entity normalizers was create an entity reference class. By using this structure we were able to load related entities, such as paragraphs and media, all on the same parent node, enabling the JSON encoder and all the entity normalizers to load the related entities and be served up as pieces on the API call. This gave POWDR the ability to create pages in much of the same structure that they’d be using on the frontend. The content admin sees a structure similar to the frontend and their API calls. POWDR is building pages on the backend in much the same way that they’re coming out on the frontend. This saves a lot of these extra extraneous API calls.

One of the great things about Drupal 8 is that it is built on Symfony, and incorporates a lot of modern PHP concepts, which helped our development of this custom API move quickly. Using Drupal 6/7, we would have to build from the ground up then figure out how the API was going to call itself. Instead, we just extended the class, extended a few other classes and, in a matter of days, had at least a working model for the design team to work from.

Overall, development was much faster for this project. Since everything was an entity point the back end API could load taxonomies, media, paragraphs in the same way and they also looked the same. This meant the design team could be presented something that is agnostic to the backend functionality but still utilizes Drupal’s media power.

To Be Continued...

In the next post of this series our hosting Partner, Acquia will cover the ins and outs of the POWDR project’s frontend design. Stay tuned!

Web Wash: Moving Forward with Webform in Drupal 8

Planet Drupal - 15. August 2017 - 19:00
In part two of our Webform tutorial, we’ll show you how to create multipage forms, apply conditional logic, create layouts and much more! We’ll take the simple newsletter signup form created in part one of this tutorial and add additional pages. Then we’ll demonstrate how to show or hide an element depending on the selection made on another element. We’ll also look at layouts and then finish off with an overview of some of the other great features Webform has to offer. For forms with many elements, it’s best to spread them across two or more pages. In this section, we’ll take the form we created in part one and move some of the elements to make a two page form. We’ll also add a preview page and make changes to the confirmation screen.