Yesterday, Acquia open sourced Reservoir, a new distribution designed for building headless Drupal instances. The Reservoir team provided a composer project command for setting up a Reservoir instance easily, but it doesn't bundle a VM. Fortunately, making BLT work with Reservoir isn't difficult. There are, though, a few steps to be aware of.
To get started, run the composer project to build a new BLT instance.
composer create-project --no-interaction acquia/blt-project MY_PROJECT
Once that completes, you need to add reservoir and (optionally) remove the lightning distro
composer require acquia/reservoir
composer remove acquia/lightning
Next, update the blt/project.yml file. The key changes you'll want to make here (beyond setting a new project prefix, etc) are a) changing the distro from ligthning to reservoir and b) removing views_ui from the modules:enable list for local environments.* An excerpt of my git diff for this file looks like...
- name: lightning
+ name: reservoir
- enable: [dblog, devel, seckit, views_ui]
+ enable: [dblog, devel, seckit]
Once that's done, continue with the BLT setup process from Step 4 (assuming you want to use Drupal VM. Step 5 otherwise).
* If you don't remove views_ui, the world won't explode or anything, but when you run blt setup you'll get errors reported like the ones below:
blt > setup:toggle-modules:
[drush] dblog is already enabled. [ok]
[drush] The following extensions will be enabled: devel, seckit, views_ui, views
[drush] Do you really want to continue? (y/n): y
[drush] Argument 1 passed to [error]
[drush] must implement interface
[drush] Drupal\Component\Plugin\PluginInspectionInterface, null given, called
[drush] in /var/www/mrpink/docroot/core/modules/views/src/Entity/View.php on
[drush] line 281 and defined PluginDependencyTrait.php:29
[drush] E_RECOVERABLE_ERROR encountered; aborting. To ignore recoverable [error]
[drush] errors, run again with --no-halt-on-error
[drush] Drush command terminated abnormally due to an unrecoverable error. [error]
[phingcall] /Users/barrett.smith/Desktop/mrpink/./vendor/acquia/blt/phing/tasks/setup.xml:370:8: /Users/barrett.smith/Desktop/mrpink/./vendor/acquia/blt/phing/tasks/setup.xml:374:12: /Users/barrett.smith/Desktop/mrpink/./vendor/acquia/blt/phing/tasks/setup.xml:377:69: Drush exited with code 255
[phingcall] /Users/barrett.smith/Desktop/mrpink/./vendor/acquia/blt/phing/tasks/setup.xml:350:45: Execution of the target buildfile failed. Aborting.
BUILD FAILED/Users/barrett.smith/Desktop/mrpink/./vendor/acquia/blt/phing/tasks/local-sync.xml:12:30: Execution of the target buildfile failed. Aborting.
; 2 minutes 37.24 seconds
Barrett Tue, 06/20/2017 - 10:09 Tags Add new comment
In Drupal, many a time we come across a situation where we want to hide certain URL part from end users.
To achieve this we often use Drupal modules like Pathauto to hide node IDs, taxonomy IDs from URL and replacing them with some patterns (eg. Titles).
The above scenario can not be achieved for Drupal commerce checkout flow(URLs) as the Drupal modules like PathAuto do not support this. To achieve this in Drupal 7 we often used one of the following ways mentioned below:
Commerce Checkout Paths Module.
The Denver Business Journal’s annual “Best Places to Work” awards wrapped up with Elevated Third landing the top spot in the “Workplace Wellness” category for small companies. The category recognizes Denver employers with an outstanding commitment to employee well-being.
As a business practice, committing to employee wellness means that everyone is operating at their highest capacity. When our minds are fresh to focus on the task at hand, we can crank out the best work possible.
Striking the ideal work-life balance is central to our culture. Where some agencies expect employees to work nights and weekends at the drop of a hat, we are committed to respecting employees’ time beyond the office and staying true to a 40 hour work week.
We believe that when employees feel valued beyond the output of their work, the workplace is a more positive and productive environment.
Outside of the office, the Elevated Third team is covered with 3 weeks of Paid Time Off, a subsidized gym membership, a $1,500 Health Reimbursement Account (HRA), and an RTD ecopass.
In the office, we are surrounded by a work environment that stimulates creativity and keeps spirits high. Office dogs can be found roaming the hallways, the kitchen is stocked with goodies of a (mostly) healthy variety, and our location on the top floor of the Denver Masonic Building provides plenty of sunlight and the occasional summer breeze.
We are incredibly proud to be recognized among Denver’s best places to work. Joining our fellow recipients, we believe this commitment to workplace wellness makes Denver a better place to live, work, and do business.
Interested in joining the team? Have a look at our open positions
In a previous post, we saw the Drupal 8's new policies for versioning, support and maintenance for its minor and major versions. This policy has evolved somewhat since the last DrupalCon Baltimore conference in April 2017. And this evolution of Drupal's strategy deserves a little attention because it can bring new light to those who hesitate to migrate their site on Drupal 8. Or those who are wondering about the relevance of launching their web project on Drupal 8.
Around two years ago, when the launch of Drupal 8 was just around the corner and the main topic of concern was the status of the issue queue, the Drupal community slowly started murmuring about a topic outside of technical solutions and patches. As a result, a brand new DrupalCon track was introduced - Being Human. Our COO, Zsófi is the Being Human local track chair at DrupalCon Vienna - this is her Call for Papers.
I'm working on a large, complex migration from Drupal 7 to Drupal 8 right now. One thing I noticed is that the migrate modules pollute the database with an unreal number of tables which allow migrations to be re-run, etc. Well if you don't need that, here's how to remove these tables. Currently the migrate modules don't clean up after themselves. Put this in a custom module or PHP script that has bootstrapped Drupal. Note this code only works in Drupal 8. Shown is a .install file for a custom module. If you uninstall the custom module, it will run the cleanup:
- Configurar una PHP Web Application para depurar por la línea de comandos.
- Todo el código ejecutado debe estar disponible en el proyecto, incluyendo drush.
- Ej. Instalando drush como dependencia de composer (también, recuerde ejecutar drush desde su proyecto).
- Habilitar depuración xdebug para la línea de comandos.
- Un enlace simbólico de xdebug.ini de mi directorio /etc/php/7.0/cli/conf.d como estaba usando en /etc/php/7.0/apache/conf.d para la depuración web.
Ejemplo de configuración:
Y añadimos:zend_extension=xdebug.so xdebug.remote_connect_back = 1 xdebug.default_enable = 1 xdebug.remote_autostart = 1 xdebug.remote_enable = 1 xdebug.remote_port = 9000 xdebug.remote_handler = dbgp xdebug.max_nesting_level = 500 xdebug.idekey = PHPSTORM xdebug.profiler_enable_trigger = 1
Utilice el botón "Listen for PHP Debug connections" de PhpStorm:
- Establezca el cliente de depuración remota en la línea de comandos utilizando:
- Editamos ~/.bashrc y añadimos:
- Establezca la configuración del servidor. Asegúrese de que el nombre que utiliza coincide con el nombre del servidor que configuró en PhpStorm:
- PHP_IDE_CONFIG = PHPSTORM
- Ejecute drush.
Drupal Drupal 8.x Drush Drupal Planeta Tag Drush Drupal Drupal 8.x Drupal 7.x xdebug debug PhpStorm Añadir nuevo comentario
We teamed up with Acquia to present “A Decoupled Drupal Story: Powdr Gives Developers Ultimate Flexibility To Build Best CX Possible.” The webinar aired in June but you can view the recording here anytime.
As the internet and web-connected devices continue to evolve, so do the needs to develop and render content. Given today’s rate of change, organizations are using decoupled architecture to build applications - giving them flexibility to accommodate any device or experience.
In this session, we’ll cover Powdr, a ski resort holding company. To give its developers the freedom to use the right front-end tools needed for any given use case, Powdr built its 17 ski resort websites on one decoupled Drupal platform. Join Elevated Third, Hoorooh Digital and Acquia to learn:
How a custom Drupal 8 solution cut implementation time in half vs Drupal 7
The ease in which Drupal 8’s internal REST API can be extended to fit a client's needs
The details of handling non-Drupal application routing on Acquia's servers
If you are considering a decoupled Drupal implementation, let’s talk.
The Drupal CLI. A tool to generate boilerplate code, interact with and debug Drupal.heykarthikwithu Wednesday, 28 June 2017 - 12:05:12 - IST, Asia/Kolkata
Over the last few years, many of us have seen the need to evolve community governance. Up until now, we had to focus on other priorities, but now is the time to address our needs for community governance especially in light of recent community events.
Our project has matured greatly and participation has expanded from developers and site builders to also include more content editors, designers, and marketing managers who work not only as freelancers or at Drupal shops, but also for large digital agencies or system integrators. We want all community members to be included in these community discussions so the redefined community governance serves everyone. This is an exciting time to create an even healthier future for our ever-growing community.
The Drupal Association is committed to staying in a support role as the community determines how to best evolve community governance to support everyone’s needs. We started helping by hosting Community Discussions that were mediated by Whitney Hess. There were 7 sessions at DrupalCon Baltimore and 7 virtual sessions between April and May. You can find the meeting minutes here.
The Community Discussions surfaced several common needs and identified several strategies for addressing those needs.
The most commonly shared needs of the community are (in order of frequency):
Strategies to address those needs ranged from clarifying the responsibilities and boundaries of the leadership roles throughout the Drupal project, determining how and where to communicate community decisions, improving processes for community management, and providing easier access to documentation about leadership roles and clearly communicating what is expected of Drupal community members.
In terms of next steps, the participants were in agreement that we need to come together in a Governance Summit to start architecting improvements to today’s governance structure. However, the community did not define the best way to hold this meeting. It is still unclear when and where it should be, and who should participate and facilitate. We will send out a community survey next to get input from you to answer these questions.Attend The Webinar
We invite to you attend a webinar on July 6 at 11 am ET / 1600 BST / 8:30 pm IST hosted by Whitney Hess. Whitney will review the findings from our Community Discussions in more detail. We will record the video and share it with you afterwards, along with a written transcript.
Dial in details are below:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 589 988 397
International numbers available:
Thank you for your patience and participation as we tackle these big questions and move forward together as a stronger community.
Meet our last intern: Brandon Reid of our Web & Drupal Developer Internship program! One of his first projects as an intern was to research High Tech Website built on Drupal, so without further ado, here are his findings:
For those who aren't familiar with Drupal. Drupal is the #1 platform for web content management among global enterprises, governments, higher education institutions, and NGOs. Drupal is flexible and highly scalable, publishing a single website or shares content in multiple languages across many devices. Technology and business...Read more
As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!
Today, there is a Moderately Critical security release for the SMTP module to fix an Information Disclosure vulnerability.
This SMTP module enables you to send mail using a third party (non-system) mail service instead of the local system mailer included with Drupal.
When this module is in debugging mode, it would log privileged information.
With the help of the D6LTS vendors, a new version was released.
If you have a Drupal 6 site using the SMTP module, we recommend you update immediately.
If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.
Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).
If you're a non-profit volunteer, board member, director, or staff, should you be afraid of using Drupal for your website needs?
There's been a lot of doom and gloom in the Drupal Community with Drupal 8 being more complex than ever! Other "content management systems" (a.k.a. CMS's) have long claimed that "Drupal is hard", "Drupal is expensive".
Is Drupal hard? Is Drupal 8 even "harder"? Is it "too expensive" for your non-profit?
Does Drupal suck at non-profits?
In this article, I take a deep dive, looking at what non-profits need from a website and how well Drupal can provide for those needs.
Read on to see what I think, and PLEASE, share your thoughts in the comments below!
Webform 8.x-5.x-beta14 has become a significant release because it addresses several important features and milestones listed on the Webform roadmap, including support for multiple drafts, Ajax-enhancing submission forms and the administrative UI.
Before I start to "show-n-telling" you about these cool new features, wanted to announce that I am targeting monthly releases and explain my goals for each release of the Webform module.
Initially,I was reluctant to publically commit to regular releases for software that I am maintaining for free. Turns out my public commitment is a good thing. Targeting regular releases motivates me to organize the Webform's roadmap and issue queue while iteratively working on fixing bugs and adding new features. I’m trying to take an agile approach with maintaining the Webform module that seeks to iteratively implement working features knowing that features and functionality can and should evolve over time.
The Webform for Drupal 8 (formerly known as YAML Form module) is a completely new codebase striving to reach reasonable feature parity with the Webform 7.x-4.x module, which is used by a half million Drupal 7 websites. I've also looked at the Webform ecosystem for Drupal 7 - gradually I’m integrating key Webform add-on modules into the core Webform module for Drupal 8.
Ajaxifying Webform Forms and User Interface