Drupal 8 with Docker CE and Docksal on MacOSX christophe Sat, 18/11/2017 - 14:56 We will cover here two options to get started with Docker for Drupal: the Docker Community Edition, then a more straightforward way with Docksal. Let's have a look at the underlying stack by starting with the bare minimum Docker setup to have a Drupal 8 site running before switching to Docksal.
Anyone handy with D7 permissions? I have an admin-lite role so the site owner can make new user accounts without being a full Administrator. The problem is that he does not see the "Role" list when creating/editing a user.
The admin-lite role has "View user profiles" and "Administer users" permission but not "Administer permissions". There doesn't seem to be an "Administer user roles" or similar, perhaps there's a module for that?submitted by /u/nautme
Read our Roadmap to understand how this work falls into priorities set by the Drupal Association with direction and collaboration from the Board and community.Announcement New issue shortcuts and friendly url structure
Drupal contributors have been managing bug fixes, feature requests, and code reviews on Drupal.org for around 15 years now. Passing an issue node id around a sprint table is a stable of DrupalCon and camps around the world. In October we announced that we would be implementing some changes to the issue url structure, as well as some shortcuts to help users navigate to issues more easily.URL Pattern for issues:
When an issue is moved between projects the alias will be updated.
The search bar will now automatically redirect you to a node if you enter its id directly:
A new menu callback will help you get to issues with a shorter url string:
And of course you can still use the old https://drupal.org/node/<nid> urls if you still have them bookmarked.
Spoiler alert: These shortcuts and new url patterns were deployed in November and you can use them right now!Drupal.org updates Composer instructions on release pages
To make it easier for site builders to figure out how to use a release with composer we've added the composer command line instructions to release pages.
This command installs the package with the current release number specified as a minimum version parameter. We also provide a link to the documentation on using Composer to manage Drupal site dependencies, to help users who may be unfamiliar with Composer learn how to use it.The Community Section
The community is the heart of the Drupal project, but until now community news has not had it's own place to live. We've now made the community page a proper section with its own blog, so that community posts and CWG information has a dedicated place to live.
When the first posts in this new section go live, we'll add this blog feed to Drupal Planet as well. Over time, we hope to further refine the community section and improve the tools we provide for the community to connect with each other.WYSIWYG for Forums (CKEditor)
We're always looking for ways to make improvements to the site that have a high impact to effort ratio. One such change was enabling the CKEditor for editing in the forums. CKEditor has been in the wild as a WYSIWYG editor on Drupal.org for other content types for quite a while now, and we felt confident it was ready for use on forums as well.Bug-fix: Dev releases on project pages
In the runup to DrupalCon Vienna we made a number of improvements to project pages - however a bug or two crept in as well. A race condition was causing dev releases not to display in some cases, and we resolved this issue in October. If you're a project maintainer on Drupal.org and see anything else go missing, please let us know!Infrastructure DrupalCI: Faster, more affordable testing
DrupalCI uses spot requests on Amazon Web Services to spin up testbots on-demand for the Drupal project. In the past, instances were provisioned in minimum increments of one hour, meaning to make the most of testing we had to queue up tests to reuse the remainder of any paid-for instance-hours.
Because AWS has enabled per-second billing, we no longer have to try to fill instance-hours, and so we have reconfigured our spot instance requests to provision testbots faster, while still saving money overall compared to the previous configuration.DrupalCI: More efficient RTBC testing
We also discovered that a bug in our automated RTBC retesting system was triggering more tests than necessary. We've fixed the bug, and now only the most appropriate recent test/environment will be retested for RTBC issues.Server Maintenance Windows
Finally, we scheduled several maintenance windows in cooperation with our infrastructure services partner to schedule updates/restarts of our servers.
https://t.co/57fE1VZHTn db maintenance window is complete. We may schedule a follow up maint window, and will notify here if needed.
— Drupal infra (@drupal_infra) October 31, 2017
As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who made it possible for us to work on these projects. In particular we want to thank:
- Elevated Third - *NEW* Premium Supporting Partner
- Thunder - Renewing Premium Supporting Partner
- EPAM - Renewing Premium Supporting Partner
- CI&T - Renewing Premium Supporting Partner
- Inviqa - Renewing Classic Supporting Partner
- Bellcom - Renewing Classic Supporting Partner
- Osforce - Renewing Classic Supporting Partner
- Faichi Solutions - Renewing Classic Supporting Partner
- Vardot - Renewing Classic Supporting Partner
- SymSoft Solutions - Renewing Classic Supporting Partner
- Forum One - Renewing Classic Supporting Partner
- Catalyst IT - Renewing Classic Supporting Partner
- Duo Consulting - Renewing Classic Supporting Partner
- Mobomo - Renewing Classic Supporting Partner
- CHROMATIC - Renewing Classic Supporting Partner
- New Target - Renewing Classic Supporting Partner
- weKnow - Renewing Classic Supporting Partner
- Davyin Internet Solutions - Renewing Classic Supporting Partner
- Kellton Tech - Renewing Classic Supporting Partner
If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.
Even when salt, shells or stones were used instead of money, the most successful sellers were those relying on marketing and analytics! After, it was always important to find ways to persuade people to buy goods, as well as to figure out which goods were most in demand.Read more
Ever since the release of Drupal 8, the most popular keyword search in the framework is “Headless Drupal” also referred as Decoupled Drupal. Headless Drupal is something where you use Drupal to store data that can be accessed in multiple applications (via REST APIs). The front end frameworks like Ionic interacts with Drupal using HTTP requests.
Check out how to use this feature of Drupal and Ionic framework to build a hybrid mobile application.
What is Ionic?…
You probably would agree that Drupal is a universal solution for the most of the sites. Drupal handles huge content websites, runs simple landing pages. This CMS is used both by clients with limited budgets and those who invest a fortune into web apps.
We - Drupalers of all kinds - know all the pros. But sometimes we need a reminder. Read this article about Drupal's advantages and reasons for migrating a site to this CMS.
We are working on a large Drupal 8 site and we are having some trouble with configuration import. Between dev, staging and prod we're seeing that some configuration stays 'overridden' even after multiple (successful) synchronisations, both through the administrative backend and drush cim. I've tried googling this but it seems we are the only ones this happens to, as I could not find anything on this issue. Has anyone experienced this, and does anyone know if this is solvable?
 Here is an example of configuration we cannot revert: https://imgur.com/e98I0xT
[edit2] We found that we can successfully synchronize these overridden items by using drupal console;
drupal config:import:single --file="/path/to/file.yml"
Note that a full import does not work, only when importing a single one. This is very strange because it looks like importing all configuration does a for loop calling the same function as the single import. This looks like a bug to me. But with this knowledge we can come up with a workaround for deployment.submitted by /u/robador51