Let's see how to update your Drupal site between 8.x.x minor and patch versions. For example, from 8.1.2 to 8.1.3, or from 8.3.5 to 8.4.0. I hope this will help you.
If you are upgrading to Drupal version x.y.z
x -> is known as the major version number
y -> is known as the minor version number
z -> is known as the patch version number.rajamohamed Sat, 03/24/2018 - 10:31
Theme Shapes API provides theme functions that help with the creation of different shapes for use in your theme. This creates div containers and classes based on inputs to generate different CSS shapes. These can be used for things like buttons, badges, backgrounds, and interface elements.
ELMSLN uses this to generate badges and in the future other course navigation visuals.
Acquia Developer Center Blog: A Dozen Reasons Why Developers Will Want to Attend Acquia’s Upcoming Engage Conference
The Tech Talks at Acquia Engage have always been among the most popular sessions, so I’m excited to announce that for Acquia’s upcoming Engage 2016 conference (Nov 1-3 in Boston) we’ve more than doubled the number of Tech Talks.Tags: acquia drupal planet
Back in January this year, we talked about Drupal 8 themes. At that time, there were 86 themes for Drupal 8 on Drupal.org.
9 months later? There are only 133 themes for Drupal 8.
In the whole of 2016, we've added only 47 themes for Drupal 8.
Drupal 8 represents a major shift away from “Drupalisms” to mainstream object-orientated PHP. Experienced developers who are used to other frameworks like Symfony, should find it much easier to pick up Drupal now than they would have in Drupal 7 and previous versions. But this shift presents challenges for those of who are used to the Drupal 7 way of doing things and aren’t necessarily up to speed with all the new PHP best practices.
Over the next few weeks, I’ll be sharing tutorials on some of the key concepts you need to understand in order to master Drupal 8 module development. This week, we are going to look at namespaces.
Third day of DrupalCon and the second day of the sessions was packed with awesome talks and interesting encounters at our Café Amazee booth.Sarah Geissberger Thu, 09/29/2016 - 11:58
Starting off my day with the first talk by Junaid Masoodi on Design Principles for MVP (minimum viable product). He covered the basic UX principles:
- Unity / Harmon
- Scale / Proportion
- Dominance / Emphasis
- Similarity / Contrast
Showing examples like Evernote's or Airbnb’s onboarding screens, that users normally skip very quickly but still aim to give enough information on a company’s unique value and leaving a nice first impression.
The second talk I listened to was by Lauri Eskola about Drupal 8 theming in depth. Starting with an introduction to twig, covering basic syntax he dived deeper into some twig magic such as includes, twig blocks, embeds and building reusable component-based approaches. Stating that “Our deliverables should be systems, including components not pages”, meaning elements that are self-contained and nestable. The talk also included a high-level summary of Drupal 8 theming system and how it works in the backend.
Packed with methodologies and hands-on examples on how to get over some everyday struggles as a frontend developer, I went on to listen to another talk on the frontend track. The speakers Nikhil Sukul and Vidit Anjaria talked about how to Animate your site. They began with a short history of animation on the web: from gifs how it first started to Flash in the nineties and to todays CSS3, Web GL and HTML5 animations. Continuing with the 12 animation principles, they spoke about the performance of specific animation options and attributes and ended their speech with straightforward examples.
Meanwhile, the HoloLens was a big success on our booth, a lot of people came by to search and destroy robots. Never done that? Then come by our booth and give it a try, it’s great fun!
My third day at DrupalCon ended indulging in a very delicious dinner with the whole Amazee DrupalCon crew at Opium. A restaurant in the hub of Wexford Street, serving top-notch Thai and Vietnamese food. Beautiful interior and sparse lighting completed the impression but see for yourself on the picture, or better go check out their fantastic food!
My fingers are trembling typing this. I can't believe it. This morning everyone in Annertech land is thinking "did that really just happen?" It appears it did, we are the web agency of the year!
Last night, to top off the other three awards we won - best arts and culture website, most beautiful website in Ireland, and best website - we then went on to win Best Web Agency 2016.
Speaking to accept the award, Alan Burke thanked the great team we have in Annertech and our fantastic clients who trust us with such important work.
We knew Ireland.ie (built by Annertech on Drupal) was a special website. The design is beautiful thanks to the amazing work of BigO Media, the content, media, and experience is second to none thanks to the the team in the Ireland.ie office at the Department of Arts, Heritage and the Gaeltacht. The implementation is without flaw (if we say so ourselves!).
This module provides bridge between html5lib library and Drupal, so that features of html5lib can be used in Drupal.
For using this module, just copy the HTML5 folder from HTML5Lib Library and put it in sites/all/libraries folder and rename HTML5 folder to html5lib.
After this enable the module.How to use this Module:
You can use Library function to traverse html, like below.
This module provides a field type for the Italian tax code - Codice Fiscale. This field type can be used on any Drupal entity and the module provides its own validation logic for data entered in the field(s).Requirements
This module requires only the core field module.
As a back-end developer, one of the surprising and fun things about this Drupalcon is how much I have learned about front-end and theming in Drupal. This has been my way of "getting off the island" and learning about things a little outside my normal comfort-zone.The kitchen table track at Drupalcon Dublin
There were two things that were the impetus for this. Firstly, I came to Dublin with Pascal https://www.drupal.org/u/hydra who works with us at erdfisch as our front-end development expert. I spent the weekend learning (and documenting) our approach to rendering content in flexible ways to achieve more sophisticated output of content than Drupal usually allows. In a nutshell, this allows us to provide very sophisticated front-end design.
The module driving this is called "seem". We were working on it this morning at the kitchen table.Exam time
The second thing that happened was that Stefan https://www.drupal.org/u/sanduhrs and I decided to jump in and take the Drupal 8 Acquia Certified Developer Exams. Stefan has passed the two Drupal 8 Exams this week (Acquia Certified Drupal 8 Site Builder and Acquia Certified Developer Drupal 8 Front-end Specialist).
I passed the Acquia Certified Drupal 8 Site Builder and am taking the Front-End Specialist exam tomorrow morning. Wish me luck!
All this has, of course, given me lots of motivation to go to sessions related to front-end and theming this Drupalcon. More to come on that in another blog post.Schlagworte/Tags: planet drupalcon dublin Ihr Name Kommentar/Comment Kommentar hinzufügen/Add comment Leave this field blank
This week is DrupalCon Dublin. And as always, Dries gave the keynote address on the first morning of the event.
This year's keynote was broken into two sections: "Drupal 8 Update" and "The Why".
In "Drupal 8 Update", Dries talks about the technical side of Drupal. From minute 27 to minute 42, Dries talks about what's new in Drupal 8.2, which arrives on October 5th. We've covered those new features in previous posts. Then, from minute 42 to 48, Dries discusses features may arrive in future Drupal versions. If you're short on time, watch those 6 minutes. Scroll down in this post, and we'll cover those 6 minutes in detail.
In "The Why", starting at minute 40, there's a much broader focus on the larger purpose of Drupal. This section of personal anecdotes and stories of Drupal in action.
As a former tech journalist I am well experienced in attending conferences all around the world, so I was very excited to attend DrupalCon Dublin on the behalf of Deeson.
With DrupalCon, it was a great opportunity to learn more about Drupal straight from the mouths of a thriving community. But with the ‘Future of Work’ approach being one of a number of reasons I decided to join the company, it was a great opportunity to share our message and the way people can thrive at Deeson with its openness, autonomy, flexible working, paid sabbaticals and paid time to contribute to the community.
DrupalCon Europe was very different to the conferences that I’ve experienced in the past in that instead of the slickness of a warm-up act with sales patter and a costly presentation, I was presented with fun and games from the Drupal community, including a singalong, viking claps, and some Irish dancing. Already I could tell this would be different experience to the tech events I’ve been used to.September 27, 2016
This was great preparation for the day, and the first presentation I saw was a powerful keynote by the founder and lead developer of Drupal Dries Buyteart about how wide and far the community stretched, and how it gave opportunities in terms of a career around the world.
Below is a video of the keynote, and is certainly inspiring for anybody thinking of getting into Drupal, whether it’s as a developer or non-technical person like me as a marketer, a project manager, or business developer.
This is how the rest of the week will shape up.
It is on! DrupalCon Dublin has officially started and it's going to be epic.Sebastian Siemssen Wed, 09/28/2016 - 12:36
The second day at DrupalCon started early with the in-famous prenote. After a long first day setting up our gorgeous booth, exploring the convention center, meeting new and old friends, a lot of hugs and a fabulous finish at the Amazee Storyteller and Gravedigger bus tour the early timeslot of the prenote was a challenge for many. If you missed the prenote, you can watch the recording on Youtube. Look out for the Pot of Gold!
As usual, the Prenote was followed by the Keynote aka the “Driesnote”, in which Dries Buytaert, the founder of Drupal, gave an overview of the state of Drupal and its outlook for the future. You can watch the Keynote on Youtube too.
For me, the rest of the morning was packed with interesting discussions and code sprints around GraphQL for Drupal. If you are interested to hear more about that or get involved, find me at our booth or in the sprints room.
I fueled my sugar addiction with an unhealthy amount of Amazee lollipops at our gorgeous booth during the breaks. If you want one too, come by our booth and find one of our lollipop dealers.
In the afternoon the sprinting continued and I got to show off our Microsoft HoloLens to a couple of people.
If you are interested and want to give it a try, come by our booth. It's fun, I promise!
In the past, after every major release of Drupal, most innovation would shift to two areas: (1) contributed modules for the current release, and (2) core development work on the next major release of Drupal. This innovation model was the direct result of several long-standing policies, including our culture of breaking backward compatibility between major releases.
In many ways, this approach served us really well. It put strong emphasis on big architectural changes, for a cleaner, more modern, and more flexible codebase. The downsides were lengthy release cycles, a costly upgrade path, and low incentive for core contributors (as it could take years for their contribution to be available in production). Drupal 8's development was a great example of this; the architectural changes in Drupal 8 really propelled Drupal's codebase to be more modern and flexible, but also came at the cost of four and a half years of development and a complex upgrade path.
As Drupal grows — in lines of code, number of contributed modules, and market adoption — it becomes harder and harder to rely purely on backward compatibility breaks for innovation. As a result, we decided to evolve our philosophy starting after the release of Drupal 8.
The only way to stay competitive is to have the best product and to help people adopt it more seamlessly. This means that we have to continue to be able to reinvent ourselves, but that we need to make the resulting changes less scary and easier to absorb. We decided that we wanted more frequent releases of Drupal, with new features, API additions, and an easy upgrade path.
To achieve these goals, we adopted three new practices:
- Semantic versioning: a major.minor.patch versioning scheme that allows us to add significant, backwards-compatible improvements in minor releases like Drupal 8.1.0 and 8.2.0.
- Scheduled releases: new minor releases are timed twice a year for predictability. To ensure quality, each of these minor releases gets its own beta releases and release candidates with strict guidelines on allowed changes.
- Experimental modules in core: optional alpha-stability modules shipped with the core package, which allow us to distribute new functionality, gather feedback, and iterate faster on the modules' planned path to stability.
Now that Drupal 8 has been released for about 10 months and Drupal 8.2 is scheduled to be released next week, we can look back at how this new process worked. Drupal 8.1 introduced two new experimental modules (the BigPipe module and a user interface for data migration), various API additions, and usability improvements like spell checking in CKEditor. Drupal 8.2 further stabilizes the migration system and introduces numerous experimental alpha features, including significant usability improvements (i.e. block placement and block configuration), date range support, and advanced content moderation — among a long list of other stable and experimental improvements.
It's clear that these regular feature updates help us innovate faster — we can now add new capabilities to Drupal that previously would have required a new major version. With experimental modules, we can get features in users' hands early, get feedback quickly, and validate that we are implementing the right things. And with the scheduled release cycle, we can deliver these improvements more frequently and more predictably. In aggregate, this enables us to innovate continuously; we can bring more value to our users in less time in a sustainable manner, and we can engage more developers to contribute to core.
It is exciting to see how Drupal 8 transformed our capabilities to continually innovate with core, and I'm looking forward to seeing what we accomplish next! It also raises questions about what this means for Drupal 9 — I'll cover that in a future blog post.