Im Rahmer der CodeWeek.eu organisierte Drupal Austria organisierte einen ganztägigen, kostenlosen Workshop um einen perfekten Einstieg in das frei verfügbare Open-Source Content Management System Drupal 8 anzubieten und so den Entwicklungsstandort Wien zu fördern. drunomics unterstütze die Veranstaltung und ich durfte den TeilnehmerInnen "Coding mit Drupal 8" näherbringen. Inzwischen hat Drupal Austria auch die Aufnahmen des Workshop veröffentlicht und das Resultat kann sich sehen lassen: 4 Stunden hochqualitatives Drupal 8 Schulungsmaterial.
Today, I've the pleasure to introduce the #d8rules initative, our combined effort to get the Rules module ported to Drupal 8 in time!
Fortunately, the first beta of Drupal 8 is coming closer so it's time to make sure all the modules are ported and ready for Drupal 8. Unfortunately, the Rules module - my long term number one contributed module - is about to be left behind. I've worked a lot on Drupal 8 to get critical Entity API improvements like the new Entity Field API (called Entity Property API at the time of the introduction) as well as the new Typed data API done. Of course, the work on core is time intensive, not "done" yet and won't stop - so there is not a lot contribution time left for my contributed modules. :/
Last week was a packed experience of sprinting, presenting & exchanging at Drupal Developers Days Szeged 2014. Here are our favorite picks.
Recently, the Drupal 7 Rules module has received some new functionality - mostly thanks to the development of the fluxkraft project. Quite some of them are under-the-hood improvements available to developers, but there is new stuff for site builders as well. So let's have a look at what's new for everyone using Rules and at what's in for developers also:
With Rules 2.4 events may define an event settings form via an optional event handler class. This might be useful in various scenarious, one of which Rules already implements: It's now possible to restrict entity related events to certain bundles immediately when adding an event. Compared to the previous way of adding a generic entity event plus a separate condition to check the bundle (e.g. "After saving new content" plus "Content is of type" condition) it's way nicer to just select the content type directly while adding the event!
While the conversion to full CRUD for entities and classed objects for Drupal 8 made good progress, we’ve not yet reached the goals of fully translatable entities and having a default entity serialization for import/export, content staging and web services. For those points we need to know what’s in an entity! Yes we can look up the fields, but there are also base entity properties and further stuff modules put on entities, which both are no fields so we do not know anything about them. That is what the new Entity Property API is supposed to change!
