Planet Drupal

Syndicate content - aggregated feeds in category Planet Drupal
Updated: 56 min 37 sec ago

Drupal core announcements: Ghent critical issue sprint recap

Tue, 01/06/2015 - 23:08
pLast month, 13 sprinters a href= in Ghent, Belgium/a for a very focused sprint designed to accelerate work on issues blocking the release of Drupal 8. The sprint was a great burst of momentum for the core critical queue -- we went from 115 critical issues at the start of the sprint to only a href=;status%5B%5D=1amp;status%5B%5D=13amp;status%5B%5D=8amp;status%5B%5D=14amp;status%5B%5D=4amp;priorities%5B%5D=400amp;categories%5B%5D=1amp;categories%5B%5D=2amp;version%5B%5D=8.0.x-devamp;issue_tags_op=%3D81 as of today/a. That means we have 30% fewer critical issues than we did a month ago./p pa href= title=Ghent sprinters by xjm., on Flickrimg src= width=640 height=259 alt=Ghent sprinters //a/p pDuring the 5-day sprint, we worked on an impressive 51 critical issues, 28 of which are already fixed. Of particular note are the a href=;priorities%5B%5D=400amp;version%5B%5D=8.0.x-devamp;issue_tags_op=all+ofamp;issue_tags=Ghent+DA+sprint%2C+D8+upgrade+path18 upgrade path blockers that we moved forward/a (that's 70% of the issues blocking a a href= upgrade path/a during that time)./p h3Sprint goals: Accomplished!/h3 pBefore the sprint, we a href= some goals/a for the progress we wanted to make on upgrade path blockers for the Entity Field API, Configuration system, and Views. Here's how we did on each of these goals:/p h4Views data structure and Entity Field API integration/h4 pWe a href= Views' entity field data from the SQL table structure/a by storing entity field information in the view configuration. This will make it possible for Views to detect when the entity field schema has changed and a href= to the changes/a (as well as allowing better support for non-SQL databases). We also defined the entity schema changes that Views will need to support, and work is underway to support them./p h4Content and configuration dependencies in Views/h4 pWe a href= content and configuration dependencies to Views/a so that Views that use entity display modes, field formatters, user roles, and so on can be safely deployed. We also a href= how to store deployable references to entities/a (for example, the taxonomy term displayed at the top of codetaxonomy/term/*/code listings) based on the shared needs of Views and Entity Reference. A patch to a href= the proposed API in Views/a is nearly ready./p h4Global settings.php overrides/h4 pWe had a fruitful discussion that clarified the problem space and culminated in splitting the issue into two steps. We a href= and a href= the original issue into the second step, and began work on the a href= step/a. While getting an initial patch for the first step to pass tests, we uncovered several blocker issues, each of which has now been committed. The patch for this issue is now up for review./p h4Configuration schema/h4 pAll hidden configuration schema issues are now fixed and will not regress, because all tests now have strict schema checking enabled by default!br / To help people get started with config schemas, Gábor Hojtsy also created a a href= handy cheat sheet/a that provides the most crucial information at a glance./p pa href= src= alt=Drupal 8 Configuration schema cheat sheet //a/p h4Data integrity on module uninstallation/h4 pThe two critical bugs in this problem space are now fixed:/p ul liModules that define content entity types (e.g., node.module, comment.module) a href= no longer be uninstalled if the site has existing entities of that type/a. Instead, the site administrator must first delete the entities via normal channels (UI, Drush, etc.), so that deletion hooks and the corresponding reference cleanups happen./li liModules that define field storages (e.g., path.module) a href= no longer be uninstalled if the site has existing entities with data for that field/a. Instead, the site administrator must first either delete those entities or update them to have empty values for that field./li /ul pTo implement both of the above, we created a new a href= We also have a non-critical issue to a href= integrate those validators when a module is being uninstalled as part of a configuration import/a./p h4NOT NULL constraints for entity base fields/h4 pThanks to fast collaboration between plach, amateescu, yched, and fago (which was greatly assisted by having them all together in-person), a patch that fixes a href= fatal error bug/a has now been committed. This required resolving some trickiness with entity reference fields, whose target_id property is simultaneously required but not known while in the process of referencing a not-yet-saved entity. The solution results in a a href= semantically correct API/a and better delineation of responsibilities between field types, field definitions, and storage handlers for identifying and implementing required-ness./p h3The UN of Chocolate/h3 pWe worked hard at the sprint, but also managed to fit in some international chocolate comparisons, with Swiss, Hungarian, and Belgian sweets to power all that coding. Contributor pfrenssen also a href= not to shave until 8.0.0/a (1 cm of beard per beta?), and Berdir shared a href= how brimming with criticals his issue tracker became/a. We even learned a bit about the history of Ghent, thanks to swentel and his father-in-law./p pa href= title=The Leie by xjm., on Flickrimg src= alt=The Leie //a/p h3Sponsors/h3 pThe sprint was sponsored by the a href= Association/a and a href= pThe following organizations also contributed their employees' time to participate in the sprint:/p ul lia href= lia href= 3/a/li lia href= lia href= amp; kaas/a/li lia href= Systems/a/li linuvole/li lia href= Agency/a/li /ul pFinally, thanks to all the sprinters: alexpott, amateescu, Berdir, bircher, dawehner, fago, Gábor Hojtsy, pfrenssen, plach, swentel, Wim Leers, xjm, and yched!/p h3What's next?/h3 pWith the record-breaking productivity of our sprint, we know that more sprints like these will a href= get Drupal 8 done/a. The Drupal Association's a href= Accelerate progam/a will include more critical issue sprints in 2015. Watch for an upcoming sprint on menu and routing criticals at a href= New Jersey/a later this month!/p

Marzee Labs: Blueprinting Drupal projects

Tue, 01/06/2015 - 21:00
p class=lead Planning the structure of a Drupal project is important. At Marzee Labs, we've developed some pretty robust methodologies over time to approach new Drupal projects, and in this post we'll outline some of these tools and processes that help us get off the ground in no time. While some of the topics are probably familiar (Drupal makefiles, installation profiles and such) you might learn some new tips and tricks to make your next Drupal project just that tiny bit more automated and run smooth. /p h3 id=the-blueprint-of-any-drupal-project-the-makefileThe blueprint of any Drupal project: the makefile/h3 pAny project we start has to have a makefile. Full stop. Requiring that every module, library or theme we use - be it from, github, or any other source - is documented in a single file, is a great way to quickly get the gist of any drupal project./p pEven though you might want to version your contributed modules (more on this below), the Drupal makefile should form the backbone of your website./p pAs an example, check out the makefiles of our a href= profile/a, our boilerplate profile that can be used to kickstart a new project. For a Drupal profile that can be contributed and packaged on, we typically have 3 different Makefiles, but now we’re only interested in codemz.make/code./p pHere are the instructions to make the codelink/code module./p precodeprojects[link][version] = 1.3 projects[link][subdir] = contrib /code/pre pEveryone inspecting the site running this profile now knows that you are using the 1.3 version of the Link module./p pNeed to patch the codelink/code module because you encountered a bug or missing functionality? Sure thing. First we scan the issue queue for patches. An example is a href= issue/a, with a working patch. We add this to our makefile, with a one-liner comment and a link to the issue on d.o./p precodeprojects[link][version] = 1.3 projects[link][subdir] = contrib ; Provide the original_url when loading the field. ; @see projects[link][patch][] = /code/pre pAnd we rebuild our project to test the patch in our Drupal sandbox, passing code--projects=link/code (and also code--no-core/code since we don’t want to rebuild Drupal core)/p precodedrush make profiles/mz/mz.make --projects=link --no-core . /code/pre pOr we download the nifty a href= Patchfile/a to apply patches directly and work with a patch file (our makefile, in this case)./p pIf you want to use the latest development version of a module, you can also do that. If you do however, always specify the revision hash as well (you find it in the a href= log/a), so you make sure you’re working with that specific development release that you tested./p projects[link][version] = 1.x-dev precodeprojects[link][subdir] = contrib projects[link][revision] = 7dc306c /code/pre pFeel the power of this? You can quickly evaluate community contributed patches, roll your own (and contribute them as a a href=http://gist.github.comGist/a if they don’t fit on, and not be dependent anymore on the module maintainers to publish that new release./p pSince you also document every patch used, you’re making this knowledge available to the other developers in the team, to the reviewer of your Pull Request (if you are using the a href= branching model/a), or generally as part of the Git history of your project. You can often revisit your makefile to remove patches if they’ve been rolled out in a new release, and update your modules. Make this a habit and it will pay off eventually./p h3 id=bundling-using-profilesBundling using profiles/h3 pAll your custom code and modules, themes and libraries to be installed should be bundled as an a href= profile/a, so your site can be a href= over and over/a./p pIf you haven’t started organizing your sites as Drupal profiles, you probably should. Have a look at our boilerplate a href= profile/a. We use it to bundle our favourite contributed modules, but it also has some custom features and part of our common worfklows we find often useful. Other examples of great Drupal profiles are a href= Kickstart/a or a href= Commons/a./p h3 id=organizing-your-code-in-a-git-repositoryOrganizing your code in a git repository/h3 pIt’s time to dive in the organization of your git repository (we love a href= If you’ve followed along so far, contributed code is documented in your makefile, while your custom features and code lives in your profile. It would be enough to version these, and that is the recommended way if you want to package your code as a profile or a base profile upon which to build new sites./p pHowever, most of the time, you will also need to deploy off this repository directly, so we suggest that you store strongall your code/strong - including Drupal core amp; contrib - in the git repository. Your directory structure could look like/p precodeprofiles/mz/modules/contrib profiles/mz/modules/custom profiles/mz/modules/features profiles/mz/libraries profiles/mz/themes ... sites/default/settings.php sites/default/ sites/default/settings.test.php sites/default/ ... index.php ... /code/pre pWe also store codesettings.php/code in the git repository, and include an if statement to load the right codesettings.php/codedepending on the environment that is available./p pAnother advantage of versioning environment-dependent settings is that you can force certain variables to be set in code, e.g. for production you might want to add/p precode// Caching settings $conf['page_cache_without_database'] = TRUE; $conf['page_cache_invoke_hooks'] = FALSE; /code/pre pto your, making all these settings directly available in git and thus for review by your peers, and it avoids having to wonder what setting is active on which environment/p pFinally, create a codesettings.local.php/code file that is loaded from codesettings.php/code, with your local database settings./p precode// For local development if (file_exists('./sites/default/settings.local.php')) { include_once('./sites/default/settings.local.php'); } /code/pre h3 id=whats-nextWhat’s next?/h3 pNow that we have given an overview of our favourite project architecture in Drupal (makefiles, profiles, and github), some of the next topics we’d like to talk about our setting up a continuous integration pipeline (using a href= CI/a), writing a couple of Behat tests to assert your site works fine, and reviewing our worfklows with Github (pull requests, issues, releases)./p pDid you miss our “Coding as a Team” series? Check out a href= automation workflow using Phing/a, a href= 2: using content fixtures/a and a href= 3: code workflow/a./p pemFeatured image credit: brianbutko / Flickr/em/p

Drupal core announcements: This Month in Drupal Documentation - December 2014

Tue, 01/06/2015 - 18:46
pHere's an update from the a href= Working Group (DocWG)/a on what has been happening in Drupal Documentation in the last month or so. Sorry... because this is posted in the Core group as well as Documentation, comments are disabled./p pIf you have comments or suggestions, please see the a href= home page/a for how to contact us. Thanks!/p h3Thanks for contributing!/h3 pSince November 28, (a href= previous TMIDD post/a), 232 contributors have made 733 total documentation page revisions, including 8 people that made more than 20 edits (lolandese, Francewhoa, webchick, kreynen, YesCT, Pierre.Vriens, Wim Leers, and PsyCode) -- thanks everyone! Most of these people are seasoned Drupal contributors, but PsyCode is a Google Code-In participant who has been editing pages. That's great -- we love it when our old friends come back to help, and when new people get involved!/p pIn addition, there were many many commits to Drupal Core and contributed projects that improved documentation -- these are hard to count, because many commits combine code and documentation -- but they are greatly appreciated too!/p h3Documentation Priorities/h3 pThe a href= documentation priorities page/a is always a good place to look to figure out what to work on, and has been updated recently./p pstrongOf special note: We're trying to get the Help pages inside Drupal 8 updated -- check the priorities page and events section below on this page for details./strong/p pIf you're new to contributing to documentation, these projects may seem a bit overwhelming -- so why not try out a a href= contributor task/a to get started?/p h3Upcoming Events/h3 ul lia href= Sprint Weekend/a is coming up on January 17-18, worldwide! a href= Brighton/a is having a documentation sprint that weekend, and we've also posted a href= on how anyone, anywhere can participate by reviewing Drupal 8 help/a./li lia href= title= - DrupalCon Latin America, Bogotá, Columbia, Feb 10-12, 2015/li /ul h3Report from the Working Group/h3 pThe Working Group meets monthly via Google Hangouts, and our next meeting is January 14. a href= Boris/a if you'd like to join the meeting. We're currently discussing how we and the community can address several big problems:/p ul liThe lack of documentation for Drupal in languages other than English./li liThe difficulty of locating documentation that answers specific Drupal questions./li liThe overwhelming size of Drupal documentation for newcomers (not knowing where to start)./li /ul

Blink Reaction: Getting up and VMing

Tue, 01/06/2015 - 18:32
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encodedp dir=ltrLast time we overviewed virtualization and its advantages for a href= target=_blankDrupal/a developing. It was all theory stuff, so I’m sure you’re itching to actually get a VM going. Let’s get started./p/div/div/div

Gábor Hojtsy: 2014 in review from a multilingual Drupal perspective

Tue, 01/06/2015 - 16:30
div class=field field-name-body field-type-text-with-summary field-label-hidden view-mode-rssdiv class=field-itemsdiv class=field-item evenpWhew! 2014 was a fantastic year for the Drupal multilingual team. We had some great events with huge sprints, including but not limited to: a href= Sprint Weekend/a, the amazing a href= Dev Days Europe/a, a href= Camp/a, a href= Austin/a, a href= Amsterdam/a and a href= pA fun fact about people on the multilingual team is that even though we usually turn out in big numbers at sprints, there are numerous great mentors among us, so we don't work on code that much at mentored sprints. We do a great job helping people get started and move into more serious core work though. Our most famous mentee this past year is 2014th Drupal 8 core contributor Holly Ross, Executive Director of the Drupal Association who contributed her first and second core patches fixing multilingual issues./p /div/div/div

Conocimiento Plus: Drupal 8 Web Services and Context Core (WSCCI) Initiative

Tue, 01/06/2015 - 14:07
Web services and mobile are more important than ever, and with that comes the need to have more flexible page and layout capabilities #8211; Dries Buytaert Introduction The future is a world where content management systems need to output data to many more devices and integrate with more and more systems and services. Drupal 7 [#8230;]img alt= border=0 src=;blog=49138767#038;post=595#038;subd=conocimientoplus#038;ref=#038;feed=1 width=1 height=1 /

Evolving Web: Iterating over trees in PHP

Tue, 01/06/2015 - 14:00
img typeof=foaf:Image src= width=243 height=220 alt=Screenshot of a directory tree. title= Processing recursive data structures in PHP /pAs a good Drupal developer, one of your New Year's resolutions should be to learn more PHP features. Today, we'll talk about iterating over tree-structured data using the awkwardly-named class a href= a href= more/a

IXIS: Looking forward to a Drupaltastic 2015

Tue, 01/06/2015 - 13:20
div class=field field-type-filefield field-field-blogimage div class=field-items div class=field-item odd img src= alt=teaser image for blog post title=Space Invaiders class=imagecache imagecache-blogfull imagecache-default imagecache-blogfull_default width=435 height=253 / /div /div /div p dir=ltrIt was an exciting and busy year here at Ixis in 2014 as we continued to build our portfolio of a href=;clients/a.nbsp;/p p dir=ltrHighlights have included a href= our tenth birthday/a and building on and growing the teamrsquo;s expertise which has allowed the company to win more clients across a variety of sectors. We also celebrated one of our best financial quarter since Ixis was founded in 2004.nbsp;/ppa href= target=_blankread more/a/p

Blair Wadman: How do you create a single on/off checkbox field?

Tue, 01/06/2015 - 11:29
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encodedpSimple on/off checkbox fields where you want the user to select or deselect a checkbox are a common requirement. Yet it is not so obvious how to create them in Drupal./p pOn/off checkbox fields are often used to toggle for things like:/p/div/div/div

Drupal Association News: Get Ready for the 2015 Community Elections

Tue, 01/06/2015 - 06:31
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item evenpimg alt= src= style=width: 240px; height: 188px; border-width: 0px; border-style: solid; margin: 5px; float: left; /During the holidays I met some folks who used to work at other open source projects. One of them asked me, What's your favorite part of your job? Lucky for me, I have a lot of great things to choose from, but the thing that always stands out is the global nature of our community. All the customs, cultures, and values are tough to navigate, but I love learning about the variety of perspectives you all bring to the table. I sincerely believe that this diversity of experince makes our community that much stronger./p pThat diversity is also why we have two At-Large positions on the Association Board of Directors - positions that are self-nominated and elected by the community. Simply put, the At-large Director position is specifically designed to ensure community representation on the Drupal Association board. If you are interested in helping shape the future of the Drupal Association, we encourage you to read this post and be prepared to nominate yourself between 1 February and 20 February, 2015./p h3 How Do Nominations and Elections Work?/h3 pSpecifics of the election mechanics were decided through a href= community-based process/a in 2012 with participation by dozens of Drupal community members. More details can be found in a href= proposal/a that was approved by the Drupal Association board in 2012 and adapted for use this year./p h3 What Does the Drupal Association Board Do?/h3 pThe Board of Directors of the Drupal Association are responsible for financial oversight and setting the strategic direction of the Drupal Association. New board members will contribute to the strategic direction of the Drupal Association. Board members are advised of, but not responsible for matters related to the day to day operations of the Drupal Association, including program execution, staffing, etc./p pDirectors are expected to contribute around five hours per month and attend three in-person meetings per year (financial assistance is available if required). You can learn more about what’s expected of board members by reviewing the a href= member agreement/a. You can also check out the a href= and summary/a we shared this summer./p h3 Who can run?/h3 pThere are no restrictions on who can run, and you don't need anyone to nominate you./p h3 What will I need to do during the elections?/h3 pDuring the elections, members of the Drupal community will ask questions of candidates. They'll post comments on candidate profiles here on and to the public Drupal Association group at a href= We'll also organize at least two all-candidates meetings (which will be announced on the Drupal Association group and blog), where community members and candidates will be able to ask questions and share information. The more you can participate, the more Drupal community members will be able to find out what you would bring to the Drupal Association board./p h3 How Do I Run?/h3 pCandidates needed! If you are considering running, please read the entirety of this post, and then be prepared to complete a self-nomination form. This form will be open on 1 February, 2015 through 20 February, 2015 at midnight UTC. You'll be asked for some information about yourself and your interest in the Drupal Association Board. When the nominations close, your candidate profile will be published and available for Drupal community members to browse. Comments will be enabled, so please monitor your candidate profile so you can respond to questions from community members./p h3 Who can vote?/h3 pVoting is open to all individuals who have a account by the time nominations open and who have logged in at least once in the past year. These individuals' accounts will be added to the voters list on and they will have access to the voting./p pTo vote, you will rank candidates in order of your preference (1st, 2nd, 3rd, etc.). The results will be calculated using an instant runoff method. For an accessible explanation of how instant runoff vote tabulation works, a href= videos linked in this discussion/a./p h3 Elections process/h3 pVoting will be held from 9 March, 2015 through 20 March, 2015. During this period, you can review and comment on candidate profiles on and engage all candidates through posting to the a href= Association group/a. We'll also be scheduling and announcing two phone-in all candidates meetings, where community members and candidates can ask questions and get to know each other./p pemstrongHave questions? /strong/emPlease contact Drupal Association Executive Director a Ross/a. Many thanks to a href= for pioneering this process and documenting it so well last year!/p pemstrongFlickr photo: a href= Views/a/strong/em/p /div/div/div

Nextide Blog: Standalone Drupal 8 script using Guzzle

Tue, 01/06/2015 - 00:24
p/ppDrupal 8 will have web services as part of core which will provide native support for all entity types including custom entity types. Drupal 8 will have support for different serialization formats like HAL+JSON, XML and JSON./p pA couple good article references:/p

Pivots recommendations: Drupal Recommender API: Roadmap for 2015 and beyond

Mon, 01/05/2015 - 19:54
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item evenpI have seen slow but steady adoption of the new release of Drupal a href= API module/a over the past few weeks after a href=/node/692the announcement/a. This post will explain my plans about future development of a href= API/a in order to help the audience make informed decisions. This is also an update to an older post on a href=/node/6812012-2013 roadmap/a./pp /ppI will categorize all my development plans into three tiers./p/div/div/divdiv class=field field-name-node-link field-type-ds field-label-hiddendiv class=field-itemsdiv class=field-item evena href=/blog/drupal-recommender-api-roadmap-2015-and-beyondRead more/a/div/div/div

Lullabot: Lullabot's 2014 Year In Review

Mon, 01/05/2015 - 19:43
pWow! What a Year!/p pAs we throw away the empty champagne bottles and start retraining ourselves to write a different year on our checks, it’s always a good time reflect upon the past year. 2014 was Lullabot’s 9th year in business and it was our biggest year ever. We contributed to projects for MSNBC, Pac-12,, Bravo TV, Saturday Night Live, Tesla Motors, NAMM, CNBC, Hotwire, Harvard University, American Booksellers Association, Intel, Comcast, GE, Qualcomm, and Teach For America, amongst others./p pimg src= style=float:right;margin: 0 0 0 10px /Our project with The Tonight Show Starring Jimmy Fallon won a a href= Arts Emmy/a for Outstanding Interactive Program./p pNext month’s GRAMMY night will mark Lullabot’s 5th year as part of a href= Over the years, we have been responsible for development and site performance. This year, however, Lullabot's design team takes charge of the GRAMMYs' site design and UX. It’s been really rewarding to work with the Recording Academy for so many years on such a high-profile project./p

Blink Reaction: Virtualizing your Drupal Dev Environment for Cleanliness and Consistency

Mon, 01/05/2015 - 18:52
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encodedp dir=ltrToo many versions of PHP on your system? MAMP got you down? Can’t find that .ini file? Don’t fret, go Vagrant! Many Drupal developers use a web developer stack such as WAMP, Acquia Dev Desktop, or MAMP to host their projects locally. When working with multiple clients, your hard drive can turn into a dorm room nightmare of multiple copies of PHP, MySQL, and Apache in order to assure compatibility with the client. Instead, simplify and standardize your workflow — and your team’s — by using freely available virtualization tools./p/div/div/div

Tyler Frankenstein: DrupalCamp Michigan 2015

Mon, 01/05/2015 - 18:43
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encoded pimg alt= class=media-image height=308 style=width: 300px; height: 308px; float: right; margin: 0em 0em 1em 1em; width=300 typeof=foaf:Image src= /Let's get together for DrupalCamp Michigan 2015. This year the camp will be hosted at Henry Ford College in Dearborn, MI on Saturday January 31st. Please visit the camp's website for more details:/ppa href= are only $15.00, The deadline for a href= proposals/a is January 11th, and sessions will be chosen on the 12th. JetBrains will be giving away 3 personal PHPStorm licenses at the camp, so be sure to attend for a chance to win./ppWe hope to see you there, cheers and happy coding!/div/div/div

Appnovation Technologies: Understanding Personalization

Mon, 01/05/2015 - 18:32
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encoded pIn recent weeks I have had the opportunity to work closely with some great opportunities along side our sales team allowing me time to explore some potential solutions way ahead of any full blown development cycle can kick off./p/div/div/divdiv class=field field-name-field-blog-header-image field-type-image field-label-hiddendiv class=field-itemsdiv class=field-item evena href=/blog/understanding-personalizationimg typeof=foaf:Image src= width=700 height=200 alt= //a/div/div/divdiv class=sharethis-buttonsdiv class=sharethis-wrapperspan st_url= st_title=Understanding Personalization class=st_facebook/span span st_url= st_title=Understanding Personalization class=st_twitter/span span st_url= st_title=Understanding Personalization class=st_sharethis/span script type='text/javascript'var switchTo5x = false;/scriptscript type='text/javascript' src=''/scriptscript type='text/javascript'stLight.options({publisher:dr-75626d0b-d9b4-2fdb-6d29-1a20f61d683});/script/div/div

ThinkShout: The Power of a Collaborative Community

Mon, 01/05/2015 - 18:00
pemOriginally published on a href= on December 10th, 2014./em/p pstrongMy Year in Drupal/strong/p pI’ve been fortunate to attend some of the biggest Drupal events in the U.S., and I always walk away from them with plenty of food for thought. Months ago, NTEN afforded me the space here to sing the Drupal community’s praises and I haven’t stopped since. I’m constantly reminded of how much I value its existence. More recently, I flew down to San Francisco to take part in the Nonprofit Summit at BADCamp that I’d co-coordinated, where I got to hear from the Bay Area folks about Drupal and nonprofits in their neck of the woods. /p pstrongOnce Again, The Drupal Community is Awesome/strong/p pEvents like BADCamp remind of the value of discussion and the exchange of ideas. Struggling to find a solution? Look to your community. One of the reasons I so appreciate the Drupal community specifically is how wonderfully they collaborate. Out of resources? Speak up in your discussion group or start a thread on a forum and watch the outpouring of support and ideas. The next thing you know, you’re looking at a list of new modules and tools that you’ve never heard of, and they might be exactly what your site needs. /p pThere’s something wonderfully exciting about being in a room full of people with the same idea: emlet’s create and use technology to help people/em. This kind of collaborative atmosphere can make even the tallest of technological hurdles seem surmountable. If you enjoy events like BADCamp for networking and learning about nonprofit tech, then there are a couple of other events you#39;ll want to put on your calendar./p pstrongNYC Camp/strong/p pIf you are a fan of BADCamp, then a href= Camp/a is just your speed. It#39;s a free, week-long Drupal conference in New York City from March 16-22, 2015. There#39;s also a nonprofit summit on the Friday of that week, which you definitely won#39;t want to miss./p pstrongDrupal Day at NTC/strong/p pFor the last three years, we#39;ve been coordinating a href= Day/a at NTEN#39;s Nonprofit Technology Conference, so I may be a little biased when I say this is an excellent opportunity to learn more about Drupal for nonprofits. You#39;ll hear from Drupal experts as well as nonprofit technologists sharing their Drupal stories and successes. This is a chance to learn about what exactly goes into building a Drupal site and how you can leverage it to further your organization’s mission with case study-style presentations throughout the day. But it’s not just about code - it’s about everything else that goes into making a successful website: content strategy, user experience, responsive design, infrastructure, the whole nine yards. If you’re curious about taking that first step toward Drupal, this event is a great place to start - and get ready for a whole lot of excellent information./p pemThis year, join us on March 3rd, the day before NTC, in Austin, Texas. Registration for Drupal Day is free when you purchase a ticket to NTC. If you’ve already registered for the NTC, but didn’t sign up for Drupal Day, never fear - just contact NTEN event staff and ask to be put on the registration list./em/p pstrongNever Stop Learning/strong/p pI never cease to be amazed at how much I still have left to learn. I know I’ll never truly be done learning, as is the nature of technology. It’s always in motion, always evolving with us and our ideas. I’m constantly surprised by even the simplest of tools. For instance, if you’re organizing a meetup or hosting a summit of your own, it’s a great idea to provide attendees with a site for collective notes, like and etherpad. This is especially helpful if you have multiple sessions happening concurrently. That way, even if your attendees can’t attend every session, they can read their peers’ notes. One of the most rewarding parts of the BADCamp Nonprofit Summit for me was opening up our once-blank etherpad after the summit and finding pages and pages of notes, tools, and URLs from discussions throughout the day. In a matter of hours, we created an amazing nonprofit tech resource. /p pI really hope you’ll take the time to immerse yourself in a Drupal Camp or Drupal-themed event and really immerse yourself in this community. These camps are often highly affordable (or free, in the case of BADCamp and NYC Camp), so it’s just a matter of finding one near you. Need help with that part? a href=’s/a got you covered. Yes, that same site I mentioned months ago offers online Drupal training as well as a calendar of Drupal events all over the world./p pI also hope those of you who are NTC-bound will consider adding Drupal Day to your schedule - it’s a wonderful introduction to the Drupal Community. Even if you can’t make it to NTC or Drupal Day, take a chance on a Drupal Summit. Meet new peers, exchange ideas and concerns, and join in on this ongoing conversation. When you speak up, you become part of the change we all need to make this community, and Drupal, even better./p

Code Enigma: Google Analytics Custom Events

Mon, 01/05/2015 - 17:23
Many Drupal sites use Google Analytics to capture statistics on page views, but often, that#039;s as far as it goes. That#039;s fine if the only events that you#039;re interested in are page loads, but what about all the other user interactions that happen on pages? With a bit of extra work, we can capture statistics on those too using the custom events feature built into the Analytics API.

Drupalize.Me: The Creative Process is Scary and That's Ok

Mon, 01/05/2015 - 17:00
div class=field field-name-body field-type-text-with-summary field-label-hidden text-content text-secondarydiv class=field-itemsdiv class=field-item evenpStaring at a blank screen, notebook, or any other space flooded with emptiness can conjure feelings of worry, confusion, and definitely fear. Yet this is a ritual anyone who considers themselves a creative willingly puts themselves through on a regular basis. Some may dread these less than pleasant feelings, but I am sure there are also many who embrace them, and I am one of them. Full disclosure, creating something is a scary process for me, and that's ok. From beginning to final product there are plenty of uncomfortable moments that I find extremely beneficial and rewarding to a successful creative process. Hopefully after I share how these often referred to as negative emotions are helpful, you, too, will see how essential they are to your creative process, and why they should be embraced and not avoided. /p /div/div/divdiv id=comment-wrapper-nid-1999/div

Drupal core announcements: No Drupal 6 or Drupal 7 core release on Wednesday, January 7

Mon, 01/05/2015 - 16:30
pThe monthly Drupal core bug fix release window is scheduled for this Wednesday. However, the last bug fix release was two months ago, and there haven't been enough changes to the development version since then to warrant a new release./p pUpcoming release windows include:/p ul liWednesday, January 21 (security release window)/li liWednesday, February 4 (bug fix release window)/li /ul pFor more information on Drupal core release windows, see the documentation on a href= timing/a and a href= releases/a, and the a href= that led to this policy being implemented./p