Drupal Feeds

Paragraph blocks

Latest Drupal Modules - Fri, 2017-04-28 15:24

This module allows you to place each value of a muti-value paragraph field into a different block. And further it allows you to place paragraph fields from related entities in a similar manner. It does so by extending both paragraphs with an admin title that is only used in the UI for layout and extending panels by providing the blocks for placement.

Categories: Straight From Drupal

Tim Millwood: Content Moderation + Content Translation = Crazy

Planet Drupal - Fri, 2017-04-28 15:08
Content Moderation + Content Translation = Crazy

As part of the Drupal Workflow Initiative we have critical issue relating to Content Moderation and translations. This is not actually a Content Moderation issue, but is just surfaced by Content Moderation because it allows you to create forward revisions. The video here should explain the issue:

Forward revisions + translation UI can result in forked draft revisions and Only having one default revision per entity forces translations to be kept in sync are the related core issues.

timmillwood Fri, 28/04/2017 - 16:08 Tags drupal-planet drupal 8 drupal core drupal Add new comment

Tim Millwood: Content Moderation + Content Translation = Crazy

Feeds from Drupal.org - Fri, 2017-04-28 15:08
Content Moderation + Content Translation = Crazy

As part of the Drupal Workflow Initiative we have critical issue relating to Content Moderation and translations. This is not actually a Content Moderation issue, but is just surfaced by Content Moderation because it allows you to create forward revisions. The video here should explain the issue:

Forward revisions + translation UI can result in forked draft revisions and Only having one default revision per entity forces translations to be kept in sync are the related core issues.

timmillwood Fri, 28/04/2017 - 16:08 Tags drupal-planet drupal 8 drupal core drupal Add new comment
Categories: Straight From Drupal

Valuebound: How to create a Drupal Entity programmatically in Drupal 8

Planet Drupal - Fri, 2017-04-28 14:41

Entities have been introduced late in Drupal 7. Drupal entity is an instance of a particular instance type. For example, the entity type for taxonomy terms is named taxonomy_term and the class name Term. We include the class like  Drupal\taxonomy\Entity\Term. Here taxonomy is a core module name, and Term is the class name of Entity.

A. How to create an user programmatically.

The fields to be created are as follows:

  1.  Username
  2.  Email address

Valuebound: How to create a Drupal Entity programmatically in Drupal 8

Feeds from Drupal.org - Fri, 2017-04-28 14:41

Entities have been introduced late in Drupal 7. Drupal entity is an instance of a particular instance type. For example, the entity type for taxonomy terms is named taxonomy_term and the class name Term. We include the class like  Drupal\taxonomy\Entity\Term. Here taxonomy is a core module name, and Term is the class name of Entity.

A. How to create an user programmatically.

The fields to be created are as follows:

  1.  Username
  2.  Email address
Categories: Straight From Drupal

Views AJAX Form

Latest Drupal Modules - Fri, 2017-04-28 14:28

In some cases, a view's exposed filters can take a significant time to construct and render. In such cases, it can be beneficial to send the view's results back to the user right away, and then load the exposed filters form asynchronously via AJAX.

This is implemented, via a new "Exposed form style" option, in this module.

Categories: Straight From Drupal

Custom Messages

Latest Drupal Modules - Fri, 2017-04-28 13:27
Categories: Straight From Drupal

Smartlook

Latest Drupal Modules - Fri, 2017-04-28 12:24
Description

Adds the Smartlook tracking system to your website.

Requirements

- Smartlook account

Installation

- Copy the smartlook_tracking module directory in to your Drupal 'modules' directory.
- Enable the module
- In the settings page enter your Smartlook ID
- Give permissions to "smartlook tracking" to any role you want to track. This is usually anonymous users

Categories: Straight From Drupal

Amazee Labs: DrupalCon Baltimore, Heads or Tails?

Planet Drupal - Fri, 2017-04-28 11:38
DrupalCon Baltimore, Heads or Tails?

Every few years at DrupalCon, a new theme sweeps through the community. It’s a conceptual theme—a motif, a forward-looking glimpse into the future (not the kind with a .info file). The topic tends to dominate conversations and fill sessions. People have varying ideas of how to best approach the new frontier.

Kathryn McClintock Fri, 04/28/2017 - 13:38

When I first began attending DrupalCons in 2011, I remember the hype about responsive websites: the difference between responsive and adaptive layouts, which grid system to use, and how to best add and target classes to efficiently apply media queries.

In 2014, there was a natural and communal shift in interest to Drupal 8’s frontend. Twig was the new kid on the block and everyone wanted a taste. Developers aimed to learn the new syntax and eagerly compared the new D8 techniques to their tried and true D7 counterparts.

This year at DrupalCon Baltimore, the hot topic has been headless Drupal. Decoupling Drupal’s frontend has been buzzed about for years, but in the past it seemed to be just that—a buzz word—a conceptual, potentially problematic, but exciting idea. Today, on the last day of DrupalCon, it’s clear developers are not just buzzing anymore, they’re building headless Drupal sites and loving it. Amazee Labs is building headless Drupal sites and loving it.

Amazee’s history with headless Drupal is a complicated one. In fact, our own Michael Schmid pointed out during his and Brandon’s React, GraphQL and Drupal session, how Amazee Labs was both skeptical and dismissive of the decoupled/headless vision when the idea initially emerged. In the last quarter of 2016 however, Amazee’s stance on headless changed. I’d encourage you to review Michael and Brandon’s Wednesday session for a deeper explanation as to the reasons behind that shift. 

Technology is a rapidly changing thing and always will be. As developers, it’s natural to feel more or less acceptance towards some changes than others. As a frontend developer who’s grown to master and enjoy working in Drupal’s theme layer, the shift to headless is a tough pill to swallow. I’d equate the sensation to experiencing some kind of loss—there’s a kind of mourning for all the hard, long hours put into building expertise in a complex, yet rewarding theme system. I’ve grown to love Twig, transforming Drupal’s notoriously bad markup into something simple and semantic, and creating truly beautiful Drupal experiences “the old fashioned way.”

Dries published an article Tuesday during the conference, Drupal is API-first, not API-only. In the post, he discusses the benefits of preserving the coupling between Drupal’s front- and back- ends, at least in part. His summary on headless CMSs has validated many of the thoughts I have regarding a fully decoupled Drupal. There are reasons to remain coupled, reasons to go headless, and reasons for a middle-of-the-road approach.

We are certainly future-looking at Amazee Labs. As a company, we are committed to enhancing our team’s skills and providing clients cutting-edge solutions. My takeaway from DrupalCon Baltimore is to embrace and learn new skills required to build innovative headless frontends while simultaneously working to improve and educate others on Drupal 8’s theme layer. The best of both worlds. Let me hear from you, fellow frontend Drupal devs—what’s your take?

Amazee Labs: DrupalCon Baltimore, Heads or Tails?

Feeds from Drupal.org - Fri, 2017-04-28 11:38
DrupalCon Baltimore, Heads or Tails?

Every few years at DrupalCon, a new theme sweeps through the community. It’s a conceptual theme—a motif, a forward-looking glimpse into the future (not the kind with a .info file). The topic tends to dominate conversations and fill sessions. People have varying ideas of how to best approach the new frontier.

Kathryn McClintock Fri, 04/28/2017 - 13:38

When I first began attending DrupalCons in 2011, I remember the hype about responsive websites: the difference between responsive and adaptive layouts, which grid system to use, and how to best add and target classes to efficiently apply media queries.

In 2014, there was a natural and communal shift in interest to Drupal 8’s frontend. Twig was the new kid on the block and everyone wanted a taste. Developers aimed to learn the new syntax and eagerly compared the new D8 techniques to their tried and true D7 counterparts.

This year at DrupalCon Baltimore, the hot topic has been headless Drupal. Decoupling Drupal’s frontend has been buzzed about for years, but in the past it seemed to be just that—a buzz word—a conceptual, potentially problematic, but exciting idea. Today, on the last day of DrupalCon, it’s clear developers are not just buzzing anymore, they’re building headless Drupal sites and loving it. Amazee Labs is building headless Drupal sites and loving it.

Amazee’s history with headless Drupal is a complicated one. In fact, our own Michael Schmid pointed out during his and Brandon’s React, GraphQL and Drupal session, how Amazee Labs was both skeptical and dismissive of the decoupled/headless vision when the idea initially emerged. In the last quarter of 2016 however, Amazee’s stance on headless changed. I’d encourage you to review Michael and Brandon’s Wednesday session for a deeper explanation as to the reasons behind that shift. 

Technology is a rapidly changing thing and always will be. As developers, it’s natural to feel more or less acceptance towards some changes than others. As a frontend developer who’s grown to master and enjoy working in Drupal’s theme layer, the shift to headless is a tough pill to swallow. I’d equate the sensation to experiencing some kind of loss—there’s a kind of mourning for all the hard, long hours put into building expertise in a complex, yet rewarding theme system. I’ve grown to love Twig, transforming Drupal’s notoriously bad markup into something simple and semantic, and creating truly beautiful Drupal experiences “the old fashioned way.”

Dries published an article Tuesday during the conference, Drupal is API-first, not API-only. In the post, he discusses the benefits of preserving the coupling between Drupal’s front- and back- ends, at least in part. His summary on headless CMSs has validated many of the thoughts I have regarding a fully decoupled Drupal. There are reasons to remain coupled, reasons to go headless, and reasons for a middle-of-the-road approach.

We are certainly future-looking at Amazee Labs. As a company, we are committed to enhancing our team’s skills and providing clients cutting-edge solutions. My takeaway from DrupalCon Baltimore is to embrace and learn new skills required to build innovative headless frontends while simultaneously working to improve and educate others on Drupal 8’s theme layer. The best of both worlds. Let me hear from you, fellow frontend Drupal devs—what’s your take?

Categories: Straight From Drupal

Video Embed Google Drive

Latest Drupal Modules - Fri, 2017-04-28 10:16

An integration for Google Drive videos into Video Embed Field.

Categories: Straight From Drupal

Manifesto: What you should know before upgrading to Drupal 8.3

Planet Drupal - Fri, 2017-04-28 09:03
Don’t panic! If you don’t use Content Moderation- and Layout Plugin-based components (like Display Suite, Panels, Panelizer and Contexts) then you’ll be fine upgrading to Drupal 8.3. If you do, there are just a few things you need to know first. “It looks insanely complicated, and this is one of the reasons why the snug. Continue reading...

Manifesto: What you should know before upgrading to Drupal 8.3

Feeds from Drupal.org - Fri, 2017-04-28 09:03
Don’t panic! If you don’t use Content Moderation- and Layout Plugin-based components (like Display Suite, Panels, Panelizer and Contexts) then you’ll be fine upgrading to Drupal 8.3. If you do, there are just a few things you need to know first. “It looks insanely complicated, and this is one of the reasons why the snug. Continue reading...
Categories: Straight From Drupal

Biko 2: Drupalcamp Madrid 2017

Feeds from Drupal.org - Fri, 2017-04-28 07:39

Los próximos días 5 y 6 de Mayo se celebra en Madrid la DrupalCamp 2017. Como todos los años el equipo de Biko será fiel a esta cita marcada en negrita en nuestro calendario a la que asistirán 7 de nuestros drupaleros. Este año hemos tirado la casa por la ventana a la hora de proponer charlas, nada más y nada menos que 10 propuestas de las que la organización ha aceptado 4. Además, como viene siendo costumbre apoyamos a la Asociación Española de Drupal siendo patrocinadores del evento.
Estas son nuestras propuestas de este año:

  • DRUPAL INSTANTÁNEO CON SERVICE WORKERS por Alberto Silva. En esta sesión veremos cómo aprovechar lo mejor del mundo backend PHP de Drupal y las Progressive Web Apps de JavaScript para conseguir cargas instantáneas y offline de tus desarrollos Drupal. Ahondaremos en la tecnología de los Service Workers, que nos permiten hacer una precarga de nuestro site, y que este funcione sin conexión a Internet. También analizaremos las distintas estrategias de cacheo que podemos utilizar y su invalidación.
  • CASOS DE ÉXITO DE DRUPAL EN ESPAÑA por David Gil. Charla compartida con otras 3 empresas en la que se presentarán 4 casos de éxito. Nosotros presentaremos el caso de la implantación de Drupal 8 en el Museo Thyssen-Bornemisza. Hablaremos de por qué elegimos Drupal 8 y la arquitectura general del nuevo conjunto de portales del Museo Thyssen-Bornemisza.
  • EL PODER DE WEBFORM (ANTES YAMLFORM) por Ruben Egiguren y David Gil. En la construcción del nuevo portal del Museo Thyssen-Bornemisza hemos apostado por la creación de todos los formularios de front-end usando el módulo Webform (hasta hace poco llamado YamlForm). En esta sesión explicaremos las bondades de esta solución y veremos cómo utilizamos el API de Webform para construir nuevos Plugins y Handlers que nos permiten crear usuarios, nodos o integrarnos con APIs externas.
  • CONTRIBUIR A DRUPAL, POR DóNDE COMENZAR DE 0 A 100 por Ruben Egiguren. En esta charla veremos los conceptos genéricos para comenzar a contribuir a Drupal: cómo comenzar, qué hacer, dónde mirar… hasta los más complejos de contribuir a Core. Siempre es bueno atraer a gente nueva a contribuir.

Y además uno de nuestros principales clientes de este último año, el Museo Thyssen-Bornemisza, va a presentar su experiencia con Drupal. Concretamente Javier Espadas, Director de tecnología del Museo, hablará de cómo el Museo ha ido avanzando en sus proyectos digitales desde su concepción hasta la selección del CMS Drupal y el desarrollo de sus dos sitios web principales recientemente publicados. Su charla se titula SELECCIONANDO UN CMS PARA LA TRANSFORMACIÓN: ¿POR QUÉ DRUPAL?

Si quieres charlar con nosotros de estos temas o de cualquiera que se te ocurra, ¡búscanos en la camp!

Categories: Straight From Drupal

Automatic Taxonomy Terms

Latest Drupal Modules - Fri, 2017-04-28 07:28

This module is able to automatically create taxonomy terms for you when an entity, of any type, is being created.

Categories: Straight From Drupal

Pages

Subscribe to My Drupal aggregator