Flocon de toile | Freelance Drupal: Render programmatically a unique field from a node or an entity with Drupal 8
It may sometimes be necessary to render a single field of a content or entity. For example, for a simplified display of contents relating to the content consulted, the use of specific fields in other contexts, etc. Obtaining programmatically the rendering of a field may be problematic for the Drupal 8 cache invalidation system, since the resulting render array would not contain the cache tags of the source entity. Let's take a look at some solutions available to us.
I'm thinking of making the switch to Drupal 8 from 7 but the one thing I'm unsure about is how to display content from one node in different regions of a page.
For example; if I had a node with an image and a title crediting the image owner and I wanted to display the image in a banner region and the image credit (image title) in the footer region. What would be the best way of doing this?
In Drupal 7 we used lots of hacks or workarounds that didn't seem very elegant (custom block, loading the node from url in page.tpl or using template.php) so I'd like to shake any bad habits going into D8.submitted by /u/rbunneeyy
Last week, I presented on "Docker & Drupal for local development" at Drupal414, the local Drupal meetup in Milwaukee, WI.
- a basic introduction to the why's and how's of Docker,
- a couple live demos, and
- the the details of how we use Docker as our local development environment to support & maintain hundreds of Drupal sites here at myDropWizard
The presentation wasn't recorded at the time, but it was so well received that I decided to record it again at my desk so I could share it with a wider audience. :-)
Here's the video:Video of Docker & Drupal for Local Development
(Sorry, for the poor audio! This was recorded sort of spontaneously...)
And here are the slides.
Please leave any questions or comments in the comments section below!
Sometimes you want a View that follows the internal logic of the filters you set up on the View, but also can have some items hand selected or cultivated to the top of the View. Or perhaps the other way to describe it is a Nodequeue View that is backfilled with some other View based logic so that you end up with a full display regardless of how many items are actually in the Nodequeue.
To do this requires three adjustments to the View (assuming you have already built the normal View logic based on filters that are separate from Nodequeue.
- Make the Nodequeue a relationship to the View.
- Add the Nodequeu to the sort criteria.
- Restructure the filter settings to make it the Nodequeue logic OR the Filter logic.
Let's say you have a 3 item View that gets used to display some promoted items on your home page. You want the View to be populated by anything in the Nodequeue and then randomly backfilled with any other item(s) that match some filter criteria if the Nodequeue does not contain three items.
0) To start, create your View that has a maximum of 3 items and set the filter(s) to use your backfil critera (a status of published and limited to whatever entities you are using) and a sort of Global: Random to randomly pick from items that meet the filter criteria.
1) Add your Nodequeue as a relationship.
You want to limited to a specific Nodequeue. The relationship should not be required, or you will not have anything to backfill with.
2) Add the Nodequeue as sort criteria to the View.
Since we want the Nodequeue items to come first, and in order we have to set the sort order in front of the rest of the View sort criteria (which in this case is random).
3) Adjust the filter criteria and break it into logical sections. The first section is the set of filters that must be applied to all items regardless of whether they are in the Nodequeue or not. (the purple region below)
Then you need to create another filter group AND in this group put the items that are either the default logic OR the Nodequeue. The default logic in this case is that audience field matches some criteria. The trick is to set the operator within this filter group to OR.
Now when you add, delete or rearrange items in the Nodequeue the VIew will match the order of the Nodequeue and if you don't have enough items in your que, it will backfill from other items that meet your criteria.
Caching Issues: By default, updating a nodequeue will not cause the cache on the View to expire if the View is cached. If you need the updates to be immediately seen by anonymous users, you can implement a hook_nodequeue_update() to clear the cache.on any changes to that nodequeue.
On the ELMS:LN team, we’ve been working a lot with polymer and webcomponent based development this year. It’s our new workflow for all front-end development and we want Drupal to be the best platform for this type of development. At first, we made little elements and they were good. We stacked them together, and started integrating them into our user interfaces and polyfills made life happy.
In 2006, only 22% of the Top 50 digital properties were Media & Entertainment companies. Today, this number has risen to nearly 70%. How did M&E brands achieve such growth over the past 10 years?
Media brands were the first movers to the web and mobile - but in world dominated by digital behemoths like Google, Facebook and Microsoft - M&E brands are forced to innovate quickly in order to grow their position in today’s digital landscape.Language Undefined
As always, Chromatic had a great time at DrupalCon - we brought knowledge to share, and learned a lot!
In 2007, Jay Batson and I wanted to build a software company based on open source and Drupal. I was 29 years old then, and eager to learn how to build a business that could change the world of software, strengthen the Drupal project and help drive the future of the web.
Tom Erickson joined Acquia's board of directors with an outstanding record of scaling and leading technology companies. About a year later, after a lot of convincing, Tom agreed to become our CEO. At the time, Acquia was 30 people strong and we were working out of a small office in Andover, Massachusetts. Nine years later, we can count 16 of the Fortune 100 among our customers, saw our staff grow from 30 to more than 750 employees, have more than $150MM in annual revenue, and have 14 offices across 7 countries. And, importantly, Acquia has also made an undeniable impact on Drupal, as we said we would.
I've been lucky to have had Tom as my business partner and I'm incredibly proud of what we have built together. He has been my friend, my business partner, and my professor. I learned first hand the complexities of growing an enterprise software company; from building a culture, to scaling a global team of employees, to making our customers successful.
Today is an important day in the evolution of Acquia:
- Tom has decided it's time for him step down as CEO, allowing him flexibility with his personal time and act more as an advisor to companies, the role that brought him to Acquia in the first place.
- We're going to search for a new CEO for Acquia. When we find that business partner, Tom will be stepping down as CEO. After the search is completed, Tom will remain on Acquia's Board of Directors, where he can continue to help advise and guide the company.
- We are formalizing the working relationship I've had with Tom during the past 8 years by creating an Office of the CEO. I will focus on product strategy, product development, including product architecture and Acquia's roadmap; technology partnerships and acquisitions; and company-wide hiring and staffing allocations. Tom will focus on sales and marketing, customer success and G&A functions.
The time for these changes felt right to both of us. We spent the first decade of Acquia laying down the foundation of a solid business model for going out to the market and delivering customer success with Drupal – Tom's core strengths from his long career as a technology executive. Acquia's next phase will be focused on building confidently on this foundation with more product innovation, new technology acquisitions and more strategic partnerships – my core strengths as a technologist.
Tom is leaving Acquia in a great position. This past year, the top industry analysts published very positive reviews based on their dealings with our customers. I'm proud that Acquia made the most significant positive move of all vendors in last year's Gartner Magic Quadrant for Web Content Management and that Forrester recognized Acquia as the leader for strategy and vision. We increasingly find ourselves at the center of our customer's technology and digital strategies. At a time when digital experiences means more than just web content management, and data and content intelligence play an increasing role in defining success for our customers, we are well positioned for the next phase of our growth.
I continue to love the work I do at Acquia each day. We have a passionate team of builders and dreamers, doers and makers. To the Acquia team around the world: 2017 will be a year of changes, but you have my commitment, in every way, to lead Acquia with clarity and focus.