Over the years, Zivtech has worked on many different types of existing Drupal websites and web applications. These projects have ranged from sites that were built with Drupal’s best practices to those built by developers with little to no Drupal experience. At Zivtech, we typically call a website that follows little to none of Drupal’s best practices a “lemon.” Our CTO, Jody Hamilton, did a great two part blog series called Lemon: Drupal Diseases and Cures if you would like to know more about what a Drupal lemon is.
If your site fits into the category of a lemon, it likely requires too much work to fix and should probably be rebuilt. In many cases though, our developers find that we can “rescue” the site to get it back into a secure and maintainable state after a site audit. We perform a site audit to identify the issues that can be fixed, and then provide an informative report about what problems have been found and how we can resolve them.
Our extensive experience with site audits has helped us identify common mistakes that Drupal sites are often guilty of. In this post we’ll outline the common mistakes and configuration issues that we find on most lemons. Some of these issues are even common on sites that have mostly followed Drupal’s best practices.Read more
How can I make a view contextual filter work with a term name that may contain forward slashes? Drupal 8
In Drupal 8, I need to create a view filtered by a term name that has spaces converted to dashes and non-alpha-numeric characters removed. A non-alpha-numeric is required to match the existing/old site path structure and remove forward slashes in the term names that are causing the view term name contextual filter to fail.
For example, a node may have a term reference with the term name of Americas/Caribbean. The URL arg passed to the view would be americas-caribbean. There does not seem to be a way to use the term name context filter with sanitized term name arg.
I've spent days and got very close, but my filter view breaks if the term name contains forward slashes. I suspect other characters in the term name may cause it to fail also.submitted by /u/quantumized
I'm planning to use Drupal for a community project as CMS for news inside an app. I'm using Active Directory (AD) in the Cloud to manage users and groups. The app I'm currently developing should display the news for a user as an webview (using Drupal default theme for mobile).
My requirements are:
- redaction system for news
- authentication to the Drupal site via AD for the users writing news
- synchronization of users and groups from AD
- backend users writing news for a specific group from AD
- user authenticates against AD inside the app and are automatically logged in into Drupal too
- user logged in can see all news belonging to them, depending on the groups they have in AD
- recursive groups are supported; means a news is written for a specific group and users belonging to that group over a group should see them (or if they directly belong to that group of cause)
- hiding the header, footer, menu and so on for displaying the news inside the webview, as the app has it's own layout
I wanna try to avoid using some API to get the news from Drupal, so I don't have to render the news content by my own.
What I found so far:
- Thunder could be the redaction system
- authentication with LDAP against AD is possible
- It possible to map AD groups to Drupals ones, but I would really prefer to use the group directly from AD and only some for redaction team
- authentication against Drupal could be done with an XHR request against it and saving the session id for the webview (not sure how to pass it to the webview then)
Any ideas? Thank yousubmitted by /u/Fabiey
Take the Amazee Agile Agency Survey 2017
As part of my new role as Agile Consultant with Amazee Labs Zurich, I'm running a global survey to assess agile practices in our industry. Anyone working in an agency environment is welcome to fill out the survey!Josef Dabernig Wed, 10/18/2017 - 13:57
Do you / does your agency work using defined agile methodologies such as Scrum and or Kanban? How do you fit theory into practice when it comes to working for different clients with different levels of understanding with regards to Agile practices at the same time?
Thank you for taking the survey before October 31 - I’m looking forward to report the findings in an upcoming blog post.
We've stepped into the last quarter of the year, but in Drupal community is still much going on. We've made a list of DrupalCamps and summits that are still available to attend. Drupal events are bringing together Drupal developers, themers, end users and those interested in learning more about Drupal for talks, sessions and collaborative discussions. Drupal Summit Tokyo Fukurasia Shinagawa Crystal Square, Tokyo, Japan 19. October 2017 9:00-19:00 Largest Drupal event in Japan will host more than 15 strategies and technical sessions, starting with a session of a formal digital director of… READ MORE
Sometimes you would like to import a huge volume of data from a CSV file into Drupal. Maybe from another CMS. Maybe from a spreadsheet. But there is no such functionality in Drupal 8 core.
To import your data from a CSV file, you need to install and enable the contributed module "Content Import". In this tutorial, you are going to import five content items of the content type Customer.
A checkout is a pretty fundamental part of a commerce system. So the fact that Commerce 2.x has a checkout is not really news. But it’s what you can do with the checkout that makes 2.x special.
You can now configure the checkout workflow. You can opt to ask for billing information, shipping information, certificates, registration details, etc. There’s lots of different data that can change depending on the type of product you sell. If you sell digital products, for instance, you don’t need shipping information. If you sell course registrations, you might require pre-existing certificates. Maybe you do both, so you need to configure multiple types of checkouts.
And that’s easy to do. For the most part, it’s a matter of dragging and dropping options. You can add or remove pieces pretty easily. If you need something really custom, like if you need to validate a safety certificate against a third party, you might need a developer to build that functionality. But otherwise it’s a fairly simple process.
You can also integrate into any part of the checkout. Maybe you do something when you add to cart, or when you complete the order. Maybe you even go off-site to pay through PayPal or register through Eventbrite and then come back. You can hook into any step you need in order to get those things done.
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.
We're back from DrupalCon Vienna, with updates on what's new from the month of our European event.Announcement TLS 1.0 and 1.1 deprecated
Drupal.org uses the Fastly CDN service for content delivery, and Fastly has depreciated support for TLS 1.1, 1.0, and 3DES on the cert we use for Drupal.org, per the mandate by the PCI Security Standards Council. This change took place on 9 Aug 2017. This means that browsers and API clients using the older TLS 1.1 or 1.0 protocols will no longer be supported. Older versions of curl or wget may be affected as well.Drupal.org updates DrupalCon Calendar syncing
In our last update, we teased a new feature for DrupalCon attendees - the ability to sync your personal schedule to a calendar program. We're pleased to report that this feature made it in time for the event, and was used by attendees throughout the week. If you've already synced your calendar for DrupalCon Vienna, you're already set up to use the same feed for DrupalCon Nashville next April!Keynote simulcast to Youtube
This year at DrupalCon, in addition to live streaming on Events.Drupal.org itself, we simulcast the keynotes to YouTube. We also embedded the keynote on the Drupal.org homepage - to spread the latest news about Drupal beyond DrupalCon attendees.
In fact, if you couldn't attend DrupalCon or just missed the keynotes, you can watch Dries' update on the Drupal project here:Industry Pages promoted in the front page Call-to-Action
We've also made some updates to how the industry pages are promoted. In addition to the dedicated block with icons linking to each industry, we now also promote the industry solutions landing page in the main CTA under the homepage header.
We hope to further encourage users evaluating Drupal to explore some of the tremendous solutions that are already out there, and take inspiration from their success.First-in/First-out issue sorting
To make sure that issues are reviewed by maintainers in the order they are received, it is now possible to sort the issue queues by when the issue status last changed. This means RTBC issues can be reviewed on a first-in/first-out basis!
This 'status changed' date field is available on the advanced search view for any issue queue. Here's what it looks like for Drupal core:Project creation analysis
About six months ago we opened up project creation on Drupal.org to allow any confirmed user to create a full project. We've put together a blog post outlining the impact these changes have had on the contrib landscape. In short, we've seen a tremendous increase in the rate of project creation, and the rate of applications for security advisory coverage, and a modest increase in projects receiving stable releases without yet opting in coverage. We're continuing to monitor project creation and work with the Security Working Group and others on next steps.Displaying orphan dev releases
In last month's update we talked about a variety of changes we made to project pages, to provide better signals about project quality to evaluators. In response to feedback, we've restored the visibility of dev releases, even when they aren't associated with a tagged release.
This is particularly helpful for project maintainers trying to bring visibility to the next major development version of their modules, such as their Drupal 8 module port efforts.
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:
- comm-press - Renewing Classic Supporting Partner
- Code Koalas - Renewing Classic Supporting Partner
- KWALL - Renewing Classic Supporting Partner
- ANNAI - Renewing Classic Supporting Partner
- UniMity Solutions - *NEW* Classic Supporting Partner
- Berger Schmidt - 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.