Last week was my twelfth Drupalversary! The first half dozen years as a volunteer contributor/student, the second half as a full-time contributor/Acquia employee. Which makes this a special Drupalversary and worth looking back on :) 2006–2012The d.o highlights of the first six years were my Hierarchical Select and CDN modules. I started those in my first year or so of using Drupal (which coincides with my first year at university). They led to a summer job for Mollom, working with/for Dries remotely — vastly better than counting sandwiches or waiting tables! It also resulted in me freelancing during the school holidays: the Hierarchical Select module gained many features thanks to agencies not just requesting but also sponsoring them. I couldn’t believe that companies thousands of kilometers away would trust a 21-year old to write code for them! Then I did my bachelor thesis and master thesis on Drupal + WPO (Web Performance Optimization) + data mining. To my own amazement, my bachelor thesis (while now irrelevant) led to freelancing for the White House and an internship with Facebook. Biggest lesson learned: opportunities are hiding in unexpected places! (But opportunities are more within reach to those who are privileged. I had the privilege to do university studies, to spend my free time contributing to an open source project, and to propose thesis subjects.) 2012–2018The second half was made possible by all of the above and sheer luck. When I was first looking for a job in early 2012, Acquia had a remote hiring freeze. It got lifted a few months later. Because I’d worked remotely with Dries before (at Mollom), I was given the opportunity to work fully remotely from day one. (This would turn out to be very valuable: since then I’ve moved three times!) Angie and Moshe thought I was a capable candidate, I think largely based on the Hierarchical Select module. Getting Drupal 8 shipped was hard on everyone in the community, but definitely also on our team. We all did whatever was most important; I probably contributed to more than a dozen subsystems along the way. The Drupal 8 achievement I’m most proud of is probably the intersection of cacheability and the render pipeline: Dynamic Page Cache & BigPipe, both of which have accelerated many billions responses by now. After Drupal 8 shipped, my primary focus has been the API-First Initiative. It’s satisfying to see Drupal 8 do well. Biggest lessons learned:
To many more years with the Drupal community! Originally from Drupal.org aggregator http://bit.ly/2EXTt5X
0 Comments
A few weeks ago, I noticed Drupal VM's PHP 5.6 automated test suite started failing on the step that runs PHP Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 32 bytes) in phar:///usr/bin/composer/src/Composer/DependencyResolver/RuleWatchNode.php on line 40
I ran the test suite locally, and didn't have the same issue (locally I have PHP's CLI memory limit set to Originally from Drupal.org aggregator http://bit.ly/2EZwEPl
Have you ever wanted to preview your new Drupal theme in a production environment without making it the default yet? I did when I was working on my redesign of dri.es earlier in the year. I wanted the ability to add It allowed me to easily share my new design with a few friends and ask for their feedback. I would send them a quick message like this: Because I use Drupal for my site, I created a custom Drupal 8 module to add this functionality. The module is probably too simple to share on Drupal.org so I figured I'd start with sharing it on my blog instead. Like all Drupal modules, my module has a
The module has only one PHP class,
The function Next, we have to tell Drupal about our theme negotiator class
A service is a common concept in Drupal (inherited from Symfony). Many of Drupal's features are separated into a service. Each service does just one job. Structuring your application around a set of independent and reusable service classes is an object-oriented programming best-practice. To some it might feel complex, but it actually promotes reusable and decoupled code. Note that Drupal 8 adheres to PSR-4 namespaces and autoloading. This means that files must be named in specific ways and placed in specific directories in order to be recognized and loaded. Here is what my directory structure looks like:
And that's it! Originally from Drupal.org aggregator http://bit.ly/2EVIgSu Themes improperly check renderable arrays when determining visibilityOne of the many great advantages of being a part of an open source project is that there are so many smart people out there are willing to contribute their time for the betterment of the project. This ability to crowdsource bugs and feature requests that rarely stumps the community is what makes Drupal such a powerful application. While rare, sometimes the community finds a bug that is very difficult to solve. Let me introduce you to [#953034] Themes improperly check renderable arrays when determining visibility. [meta] Themes improperly check renderable arrays when determining visibility I was first introduced to this bug while trying to add a view block in the left sidebar. When the view was empty I expected the block and the sidebar to not be displayed. As you can see below, while the block was empty the sidebar was still being rendered. I then googled and stumbled upon another issued, Empty view causes region to be displayed and it was exactly what I was looking for, but I noticed it was marked as a duplicate issue and linked to [#953034] Themes improperly check renderable arrays when determining visibility. This bug was reported to Drupal 7 core on October 26, 2010. The issue has over 310 comments and 230 followers. You can really tell the severity and complexity of an issue when you see some of the brightest Drupal contributors have been making suggestions and striking out. They include but are not limited to: While I am not a backend developer, I felt like I could still help by highlighting a major issue that maybe someone either inside or outside the community could help find a solution. Please remember to read the complete issue before commenting as so many people have suggested solutions to fix but have ran into a roadblock. [meta] Themes improperly check renderable arrays when determining visibility If you are interested in contributing blog post or want to get more involved with the Atlanta Drupal Users Group (ADUG) please feel free to reach out [email protected] An 8-Year-Old Drupal Core Issue That the Community Needs Help to Solve was originally published in Drupal Atlanta on Medium, where people are continuing the conversation by highlighting and responding to this story. Originally from Drupal.org aggregator http://bit.ly/2EQRhNq
Lights, Camera and Action with Drupal Vasundhra Thu, 12/27/2018 - 11:51
Ah! those days, when copies of movies were sold in the form of DVDs, fast forwarding and rewinding through the scenes made us feel that the power is all in our hands. But with the evolution in technology and internet presence (in terms of marketing a film), the need for a movie website has come a long way after witnessing a growth in streaming services.
And nothing does a better task than Drupal. Often preferred by brands that deal with a high volume of traffic, this CMS platform would offer you effective features and functionalities for your website. What Does Drupal Offer Your Website With?Choosing a Content Management System for your website is like choosing the cast for your movie. And Drupal proves to be the CMS which give the best of “all worlds”. It would provide you with an ample number of functionalities and fulfill all your customer's needs. Starting from: Content AuthoringWhile you are creating your movie website, there might be instances that would lead you to a situation in which you wish to edit your content or any particular page. It may be a change in the movie title or modification in the synopsis. Drupal 8 features bring about an unusual power into the hands of content authors. With modules like WYSIWYG CKEditor, drafting and editing content have become a piece of cake. The use of client-side editors to edit content, installing and integrating choice editor has been made even more simple. It includes HTML editors (i.e WYSIWYG), pseudo-editor (to insert markup into text area) and flash based applications (for production of animation) The WYSIWYG module also presents you with an abstraction layer for other Drupal modules to integrate with the editor which implies that Drupal modules can expose content editing functionality, indifferent of what editor has installed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
April 2023
Categories |