Sign up to be notified when Agaric gives an online or in-person Drupal migration training:
Resources
We're always publishing more about migrating data and also have a growing collection of resources in the follow-up section of our migration training resources page.
And be sure to check out our other trainings!
Image credit: Karlheinrichpasch, CC BY-SA 4.0, via Wikimedia Commons.
Sign up to be notified when Agaric gives a migration training:
The red boxes above indicate what needs to be done. Be sure to select the relationship you added to the Relationship field. This will allow the contextual filter to use the value of the Event's entity reference field for comparison.
Click Provide default value and select Content ID from URL in the dropdown that appears. Note that if your nodes have URL aliases that do not include the content ID, Drupal will still provide the content ID to your contextual filter. Now your view will know which content to display by comparing the current node ID with the the values in the entity reference field of each listing.
Lastly, Click Apply and do not forget to save your view.
The End
Congratulations! Now we know how to filter our view by content that references the current node. You probably still need to place your block and configure which nodes it should or should not display on, but I think that is a "How to" for another day. Have fun Drupaling!
Get updates from Micky, Ben, and other Agarics on their involvement in lots of movement work. We will send you occasional dispatches from our perspective on various overlapping movements for freedom and justice, and the building of democracy thereby, as workers fighting the good fight and as passionate observers.
350.org es una organización global de justicia climática que ayudó a organizar la huelga climática más grande de la historia. Juntos, mejoramos su Mapa de Acción de Justicia Climática (CJAM) en el período previo a la huelga para que los activistas pudieran movilizar mejor a sus comunidades.
Teachers with GUTS
Empowering educators to teach science confidently.
UPDATE: The DrupalCon Seattle training SOLD OUT a few days after we posted the details on the DrupalCon Seattle 2019 website! There were 45 trainees and six trainers - the Agaric team was joined by Leslie Glynn, the recipient of the 2019 Aaron Winborn Award, presented in the DriesNote! Leslie has been a volunteer at just about every Drupal event we have attended and she is well versed in many aspects of Drupal. It was a real pleasure to have her help on the mission to get people's hands and minds on the Drupal 8 migration process.
Maecenas commodo nisi sit amet eros lacinia vehicula. Aenean sollicitudin magna at lectus mollis feugiat. Etiam condimentum, massa sed rhoncus finibus, libero lectus interdum purus, vitae tempor quam odio ac turpis. Nullam gravida consectetur lacinia. Morbi eleifend facilisis auctor. Nam blandit dolor id sodales venenatis. Curabitur eget lorem est. Donec blandit interdum tortor et luctus. Etiam nisi ligula, sodales vitae lorem vel, maximus elementum dui. Suspendisse congue, urna at lobortis scelerisque, odio sapien euismod arcu, et fringilla est tortor porta nisl. Curabitur nec enim a neque condimentum sodales. Sed ac euismod leo, et condimentum velit. Suspendisse potenti. Nam dignissim faucibus odio, quis semper dui sollicitudin cursus.
TLDR: Drupal 7 has a much longer lifespan than the (already pushed back) official date, and Drupal 8 has an essentially infinite lifespan because it updates in-place to Drupal 9 easily (and the same will be true of Drupal 10, 11, ∞.). There's no reason to rush an upgrade— but there's no reason to wait either.
That's the short version.
A client recently wrote to Agaric about Drupal 7 / Drupal 8 / Drupal 9 project planning questions:
With the EOL for Drupal 7 in Nov of 2022, and the EOL for Drupal 8 in Nov 2021, is there a reason we should move a D7 site to D8 at all this year? Seems like we might want to move directly to D9? We don’t want to feel pushed up against a wall with a “new” site build in Drupal 8, if we can limp along in D7 for a couple more years while we develop a D9 site with a longer lifespan. I’m wondering if you might have time to discuss pros and cons briefly so we can get a good plan together for moving forward.
I started typing and almost did not stop:
-
No one believes me when i say this, but i repeat my assurance that Drupal 7 will be well-supported commercially until 2030 or later (Drupal 6, released in 2008, still has semi-official long term support until at least February 24th, 2022— and Drupal 7 has a larger install base than Drupal 6 ever did, and currently has the largest install base of any version of Drupal by far, with more than half a million tracked installs.
Drupal 7 will be supported by the community for a long time. You do not have to feel pushed to a new version, like, ever.
Migration experts
We are acknowledged experts in Drupal migrations, leading paid trainings at Drupal conferences and beyond. Mauricio Dinarte's 31 Days of Drupal Migrations blog series gives evidence for our passion for migrations, and we hope to continue living out that passion helping you migrate your site to modern Drupal!
A full range of services
Beyond migrating your data, we offer services for site-building, theming, design, and strategy analysis—everything required to ensure a successful migration and future for your new Drupal site.
Get in touch
E-mail us at ask@agaric.coop, call us at +1 508 283 3557, or use this form below, and one of us worker-owners at Agaric will get back to you.
