Planet Drupal

Syndicate content - aggregated feeds in category Planet Drupal
Updated: 57 min 18 sec ago frontpage posts for the Drupal planet: Drupal 7.31 and 6.33 released

Wed, 08/06/2014 - 18:35
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item evenp style=position: inherit;Drupal 7.31 and Drupal 6.33, maintenance releases which contain fixes for strongsecurity vulnerabilities/strong, are now available for download. See the a href= 7.31/a and a href= 6.33/a release notes for further information./p div style=float: right; margin: 0 0 1em 1em; text-align: center; a href= class=link-button style=margin: 0 0 0.6em 0;spanDownload Drupal 7.31/span/abr /a href= class=link-buttonspanDownload Drupal 6.33/span/a/div p style=position: inherit;stronga href=/upgrade/Upgrading/a your existing Drupal 7 and 6 sites is strongly recommended./strong There are no new features or non-security-related bug fixes in these releases. For more information about the Drupal 7.x release series, consult the a href= 7.0 release announcement/a. More information on the Drupal 6.x release series can be found in the a href= 6.0 release announcement/a./p !--break--div style=float: right; padding: 0 0 2em 1em; margin-left: 2em; width: 35%; border-left: 1px solid #cdcdcd; h2Security information/h2 pWe have a a href=/securitysecurity announcement mailing list and a history of all security advisories/a, as well as an a href=/security/rss.xmlRSS feed with the most recent security advisories/a. We strongstrongly advise Drupal administrators to a href=/securitysign up/a/strong for the list./p pDrupal 7 and 6 include the built-in Update Status module (renamed to Update Manager in Drupal 7), which informs you about important updates to your modules and themes./p h2Bug reports/h2 pBoth Drupal 7.x and 6.x are being maintained, so given enough a href=[]=8amp;categories[]=1bug fixes/a (not just a href=[]=1amp;categories[]=1bug reports/a) more maintenance releases will be made available, according to our a href= release cycle/a. /p/div h2Changelog/h2 pDrupal 7.31 is a security release only. For more details, see the a href= release notes/a. A complete list of all bug fixes in the stable 7.x branch can be found in a href= git commit log/a./p pDrupal 6.33 is a security release only. For more details, see the a href= release notes/a. A complete list of all bug fixes in the stable 6.x branch can be found in a href= git commit log/a./p h2Security vulnerabilities/h2 pDrupal 7.31 and 6.33 were released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory:/p ullia href= /ulpTo fix the security problem, please upgrade to either Drupal 7.31 or Drupal 6.33./p h2Update notes/h2 pSee the a href= and a href= release notes for details on important changes in this release./p h2Known issues/h2 pNone./p /div/div/divdiv class=field field-name-taxonomy-vocabulary-34 field-type-taxonomy-term-reference field-label-abovediv class=field-labelFront page news:nbsp;/divdiv class=field-itemsdiv class=field-item evena href=/taxonomy/term/903Planet Drupal/a/div/div/divdiv class=field field-name-taxonomy-vocabulary-5 field-type-taxonomy-term-reference field-label-abovediv class=field-labelDrupal version:nbsp;/divdiv class=field-itemsdiv class=field-item evena href=/taxonomy/term/102Drupal 6.x/a/divdiv class=field-item odda href=/taxonomy/term/120Drupal 7.x/a/div/div/div

Forum One: NVDA Screen Readers and Invisible Elements

Wed, 08/06/2014 - 16:02
pHere#8217;s an interesting bug#8230;/p pIt is a pretty common practice to hide from view text that is meant for visually impaired users to read via a screen reader. In Drupal, required fields will get a value that is hidden in this way via CSS in the field#8217;s label elements. By default, this text reads #8220;This field is required#8221; however the text is translated, so it may vary depending on the language of the page. Visually, this text is hidden; sighted users will still see a red star character next to these fields, but it is only meant as a cue for users utilizing screen readers./p pA common method of hiding these #8216;Cur#8217; elements is to set the element#8217;s width and height to 1px and use the the clip property. This method can be seen a href= this blog post/a and is briefly hit upon in a href= WebAIM article/a./p blockquotep.element-invisible {/p pposition: absolute !important;/p pheight: 1px;/p pwidth: 1px;/p poverflow: hidden;/p pclip: rect(1px 1px 1px 1px); /* IE6, IE7 *//p pclip: rect(1px, 1px, 1px, 1px);/p p}/p/blockquote h2The Problem/h2 pI#8217;ve come across an issue that can hamper accessibility. Users employing the NVDA Screen Reader with Firefox and using the screen reader viewer will see elements styled like this with the spaces removed, e.g., #8220;Thisfieldisrequired.#8221; This does not appear to be an issue in Chrome, and I have not tested in other browsers. The screen reader view renders as:/p pa class=image-link href= class=aligncenter wp-image-3700 size-large src= alt= width=700 height=368 /br / /a/p h2The Solution/h2 pIt seems that this spacing is caused by how Firefox is interpreting the width property. Using a larger width here seems to resolve the issue, and a good threshold for this seems to be 9px. I tried it with 8, but oddly, that width leaves some words still missing spaces while correcting others. This may cause some layout issues, however. (I spend more of my time in back-end development, so I am not a CSS expert by any means.) Here is the result of changing the element’s width to 9px:/p pa class=image-link href= class=aligncenter wp-image-3703 size-large src= alt= width=700 height=369 //a/p pnbsp;/p pnbsp;/p pspan style=color: #000000;Thus, it seems changing the pixel size of these invisible elements could be one small step towards improving accessibility of this screen reader in Firefox./span/p

Promet Source: p dir=ltr style=line-height:1

Wed, 08/06/2014 - 15:28
p dir=ltr style=line-height:1.15;margin-top:0pt;margin-bottom:0pt; /p

Acquia: Drupal 8's new theming layer – Joël Pittet and Scott Reeves

Wed, 08/06/2014 - 15:09
div class=field field-name-body field-type-text-with-summary field-label-hidden div class=field-items div property=content:encoded class=field-item evenpDrupal 8 theming layer co-maintainers Joël Pittet and Scott Reeves sat down with me at NYC Camp 2014 at United Nations Headquarters in New York City to talk about how Twig and the new theming layer in Drupal 8 empowers front- and back-end developers, convergence and contribution in PHP, and more./p /div /div /div span property=dc:title content=Drupal 8#039;s new theming layer – Joël Pittet and Scott Reeves class=rdf-meta/span

Amazee Labs: How to write Sass within Chromes DevTools using Workspaces and Auto-reload

Wed, 08/06/2014 - 12:48
span class=field field-node--title field-name-title field-type-string field-label-hiddenHow to write Sass within Chromes DevTools using Workspaces and Auto-reload/spandiv class=field field-node--field-lead field-name-field-lead field-type-text-long field-label-hidden div class=field-items div class=field-itempThere is this feature in Chromes’ DevTools that allows you to directly edit your local Sass files without ever leaving your beloved browser. Even better, it will refresh your CSS files as soon as Compass has compiled them for you (kinda like a href=!). And to go even further, it will show you where the CSS definitions really come from (the original Sass files), instead of that generated gibberish./p/div /div /div div class=field field-node--body field-name-body field-type-text-with-summary field-label-hidden div class=field-items div class=field-itemh2Intro/h2 pSo to start, you'll obviously have to be working with Sass/Compass for this to work (pardon the pun!). I won’t go into detail on how to install these lovely things as this could take up an entire post itself. So if you know how to install Sass/Compass on your machine or have a handy co-worker you can annoy (preferably a sys-smonkey/s admin) you’re good to go./p pWith Sass and Compass there are as always issues if you're not working with certain specific versions. The most reliable combination that worked for me was this one:/p ulliSusy 1.0.9/li liRuby 1.9.3/li liSass 3.3.0.alpha.134 (i suppose Sass 3.3.x will work fine too)/li liCompass 0.12.4.sourcemaps/li /ulh2The thing about source maps/h2 pFor Compass you need an entirely different version from the one that you probably have, its called “compass-sourcemap”./p pIn order to get that juicy source map action you'll have to open up your shell and type in the following:/p pre sudo gem install compass-sourcemaps --pre/prepThis will install a compass version with source map, in the future source map will (a href= be included in the regular compass versions./p pSo what is compass-sourcemap exactly you ask? Well first of it’s super fantastic, even if you don't want to have all the workspace/auto-reload mayhem you should take a look at it./p pFor example, on a casual day while you’re working with that sassy generated CSS, the inspector can’t really tell you where the real definitions are coming from. It only shows you the line within the generated CSS file. This is where source maps comes in, it generates an additional .map file for every .css file and tells your browser where the CSS definition is coming from. There are 4 things you'll have to do after you've installed all the necessary tools:/p olliEnable “CSS source maps” in the General Chrome DevTools Settings under “Sources” ulli pre img alt= data-editor-file-uuid=b440d62d-8743-4a36-9b08-8de83bd64d75 height=281 src=/sites/default/files/inline-images/Screen%20Shot%202014-08-06%20at%2013.59.53_1.png width=326 //pre/li /ul/li liEnable it in your config.rb file, just add the following line (make sure its not already there) ulli pre sass_options = {:sourcemap =gt; true}/pre/li /ul/li liIn the shell, run your compass just like you always have ulli pre compass watch/pre/li /ul/li liEnjoy it! ulliimg alt= data-editor-file-uuid=4ad87309-c03d-41f3-8113-19a39c851511 height=308 src=/sites/default/files/inline-images/Screen%20Shot%202014-08-06%20at%2014.03.19.png width=601 //li /ul/li /olh2Prepare your Drupal/h2 pDisable the “Aggregate and Compress CSS files.” option in your Drupal 7 Installation in “YOURSITE/admin/config/development/performance”./p pNext up: download and enable this small module: a href= pThis will remove that pesky query behind your .css files, normally this would be a bad thing and you should strongemnever/em/strong use this on a production site. However, for Chrome to properly track your local files it needs to have a permanent link to them, in other words a path that doesn't change. I got the code from an issue queue (i think…) on a href= but i can’t remember which one, I simply put it inside a module for easy handling. So credits go to the unknown contributor, thank you very much (and sorry)!/p pBefore:/p pimg alt= data-editor-file-uuid=eb7ccd03-e58f-44ba-9550-80a13a3d5552 height=75 src=/sites/default/files/inline-images/before.png width=731 //p pAfter:/p pimg alt= data-editor-file-uuid=7fef5575-4c32-464a-9e00-eb1e991e0430 height=77 src=/sites/default/files/inline-images/after.png width=690 //p h2Prepare your Chrome/h2 pGo back to your general DevTools settings and enable “Auto-reload generated CSS”, its right below the source maps option:/p pimg alt= data-editor-file-uuid=26bbdd14-f618-48a7-823b-59f62daf7fe4 height=281 src=/sites/default/files/inline-images/Screen%20Shot%202014-08-06%20at%2014.07.42.png width=304 //p pAfter that open up your local project with Chrome and navigate to “Sources” in DevTools. You should see something that looks a little like this:/p pimg alt= data-editor-file-uuid=651890ea-2268-4bb0-b713-19d3f4fe79b8 height=358 src=/sites/default/files/inline-images/Screen%20Shot%202014-08-06%20at%2014.09.20.png width=585 //p pWhat you’re gonna do next is adding your local site as a workspace inside Chrome, this will remain in there until you manually remove it. I like to take the entire theme folder; you could also add the entire site, that’s all up to you. If you've picked the folder you want, right click and pick “Add folder to workspace”. Navigate to the exact same folder on your local machine and select it./p pimg alt= data-editor-file-uuid=f16c4364-a192-41dd-8709-9ad4221ced29 height=505 src=/sites/default/files/inline-images/Screen%20Shot%202014-08-06%20at%2014.10.42_0.png width=1206 //p pAt this point Chrome will ask you for writing permissions, just oblige and never think of it again. I mean it’s Google; what could possibly go wrong, amiright?/p pimg alt= data-editor-file-uuid=fcc7b9e2-40bc-437b-be00-eb28de58b55c height=95 src=/sites/default/files/inline-images/Screen%20Shot%202014-08-06%20at%2014.12.24.png width=822 //p pYou should now see a new folder at the bottom of the sources tab inside your DevTools, it’s named after the folder you've just picked. Navigate to where the main .css file is (or any other .scss file), right click and select “Map to Network Resource”/p pimg alt= data-editor-file-uuid=5f6c8209-d826-463a-813b-59694925150b height=539 src=/sites/default/files/inline-images/Screen%20Shot%202014-08-06%20at%2014.17.09.png width=438 //p pChrome will now bring up a selection of files from your site, match it to your local file./p pimg alt= data-editor-file-uuid=5f08c7e7-e4cc-420e-8307-7c0189b35627 height=177 src=/sites/default/files/inline-images/Screen%20Shot%202014-08-06%20at%2014.18.18_0.png width=787 //p pAnd finally Chrome will ask you if it’s okay to reload DevTools; you are totally fine with that so pick “ok” - and you're done!/p pYou can open any .scss files from your workspace or use the inspector to directly open a file and make all the changes you want. You can save using your standard cmd+s and even open files using cmd+o. Everything will be saved just as if it was done within a proper IDE, except its Chrome!/p h2But there’s one more thing/h2 pIf you right-click on any of your .scss files you can select “Local Modifications”; this will bring up a general “History” of all your changes and you can even revert them!/p pimg alt= data-editor-file-uuid=9facf0b6-9679-4008-9300-eb155baf2fa3 height=173 src=/sites/default/files/inline-images/history.png width=718 //p p /p /div /div /div

KYbest: Exporting image field defaults in D7

Wed, 08/06/2014 - 10:32
pWe all love image fields' defaults: it's so easy to have a hero image for a product or a colleague's profile even when the editor does not provide one, with all the niceties such as displaying it with various image styles in a list, in the teaser or on the actual page. We all love a href= module as it allows us to export Drupal 7 content types with all its settings./p

Modules Unraveled: 114 What PHPStorm brings to Drupal Developers with Maarten Balliauw - Modules Unraveled Podcast

Wed, 08/06/2014 - 06:00
div class=field field--name-field-image field--type-image field--label-hiddendiv class=field__itemsdiv class=field__item evenimg typeof=foaf:Image src= width=200 height=200 alt=Photo of Maarten Balliauw //div/div/divspan class=submitted-byPublished: Wed, 08/06/14/spandiv class=field field--name-field-podcast-file field--type-file field--label-hiddendiv class=field__itemsdiv class=field__item evendiv class=mediaelement-audioaudio src= class=mediaelement-formatter-identifier-1407307858-0 controls=controls /audiodiv class=mediaelement-download-linka href= this episode/a/div/div/div/div/divdiv class=field field--name-body field--type-text-with-summary field--label-hiddendiv class=field__itemsdiv class=field__item even property=content:encodedh2PHPStorm/h2 ulliI’ve recently started using Sublime Text, how would you compare PHPStorm to other text editors?/li liWhat is an “IDE”?/li liWhat are some of stand out features of PHPStorm?/li liWhere can people find out more about how to use the features of PHPStorm?/li liWhat is the pricing structure?/li /ul!-- Last chance to send in questions using the hashtag: #MUP114 --pPHPStorm and Drupalbr / * What integrations does PHPStorm have with Drupal 7, right now?br / * What will PhpStorm do for Drupal 8?/p h2Questions from Twitter/h2 ullia href= Drummond/abr / Really enjoy using a href= Always interested in learning how to get more out of my use of it./li /ul/div/div/divdiv class=field field--name-field-items-mentioned field--type-link-field field--label-abovediv class=field__labelEpisode Links:nbsp;/divdiv class=field__itemsdiv class=field__item evena href= rel=nofollow target=_blankMaarten on Twitter/a/divdiv class=field__item odda href= rel=nofollow target=_blankMaarten on GitHub/a/divdiv class=field__item evena href= rel=nofollow target=_blankMaarten’s blog/a/divdiv class=field__item odda href= rel=nofollow target=_blankPHPStorm Website/a/divdiv class=field__item evena href= rel=nofollow target=_blankPHPStorm Tutorials/a/divdiv class=field__item odda href= rel=nofollow target=_blankPhpStorm hands-on/a/div/div/divdiv class=field field--name-field-tags field--type-taxonomy-term-reference field--label-abovediv class=field__labelTags:nbsp;/divdiv class=field__itemsdiv class=field__item evena href=/tags/development typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=Development/a/divdiv class=field__item odda href=/tags/editors typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=Editors/a/divdiv class=field__item evena href=/planet-drupal typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=planet-drupal/a/div/div/div

Drupal Association News: What the Association Board Does, and Why You Should Run!

Wed, 08/06/2014 - 04:39
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item evenpOne of the things that sets the Drupal community apart from other open source projects is our big, amazing, and very diverse community. The Association board is structured to help represent our community with two community elected seats. After a an a href= to our bylaws this May/a, we now elect one board member per year to a two-year term. These seats are open to all community members, and we need you to fill them! Our next election will be held in early 2015, and we need your help finding great candidates./p pAs we shared in the a href= election wrap up presentation/a at the DrupalCon Prague public board meeting, we have a couple of challenges when it comes to public elections. The first is fielding a diverse candidate pool. We had some great candidates, but very few women, people of color, or candidates from outside the US. In our next election, we'd like to see more diversity in the candidate pool. Secondly, we have very low turn out for the elections. Anyone with a user account created before nominations open and with at least one login in the last year can vote. Yet, we had just 668 votes in the last election - not even a full percent! /p pSo now we're on a mission to make sure that the community understands the role of the board in the Drupal Project, the work that the board undertakes, and what it takes to serve on the board yourself. On Tuesday, 5 August, we held a webcast that outlines what the board does, how the elections work, and how to run. You can watch the whole thing here, and check out some of the key points, below./p piframe allowfullscreen= frameborder=0 height=360 src=// width=640/iframe/p h3  /h3 h3 What does the Board Do?/h3 pAssociation board members, like all board members for US-based organizations, have three legal obligations: a href= of care, duty of loyalty, and duty of obedience/a. In addition to these legal obligations, there is a lot of practical work that the board undertakes. These generally fall under the a href= responsibilities/a of the board and include:/p ulli Overseeing Financial Performance/li li Setting Strategy/li li Setingt and Reviewing Legal Policies/li li Fundraisng/li li Managing the Executive Director/li /ulpTo accomplish all this, the board meets each month for two hours, and comes together for the two-day retreats, usually scheduled to coincide with the North American and European Cons as well as one January or early February meeting. As a board member, you can expect to spend a minimum of five hours a month./p h3 How do Nominations and Elections Work?/h3 pThe first elections were held in 2012 after a lengthy community discussion was held to determine the specifics of who should be able to run, how voting would work, and who would be eligible to vote (among other details). The a href= discussion/a that surfaced most of these issues is a great background read. The result is a nomination and voting process that is still in use today. /p pNominations are only accepted as self-nominations in our elections. You may not nominate another person. We accept those nominations during a short (two to three week) window, and after much outreach into the community. To nominate yourself, you need only complete a short form that asks for information such as your bio, your interest in running, what makes you a good candidate, as well as a photo and contact information./p pFor voting, we use the a href= Run Off/a method. The method of voting ensures that whoever wins is supported by a majority of voters. Voters rank candidates according to their preferences, and do not have to rank every candidate to complete their votes. Voting will be open for a week to two weeks, and any individual with a account before nominations open and who has logged in at least once in the prior year may vote./p pOh, and in case you're wondering, we use the a href= Module/a to make this all happen./p h3 Who Can Run? How do I Run? What do I do?/h3 pAnyone can run for the board, and we welcome all candidates. However, we do want to point out that serving on the board is very different than many of the other opportunities to contribute to the Drupal community. The board works at a strategic level, not a tactical one, and is often thinking one to three years out at a time. We want new board members to find ways to contribute and have a voice as quickly as possible, so we recommend that you have (or that you find) experience with any of the following types of areas:/p ulli Other board experience/li li Reading financial documents/li li Drupal community committee experience/li li Strategic planning/li li Policy development/li /ulpHowever, I want to stress that NONE of these are REQUIRED to run for or serve on the board. There are many great and free resources at a href= and the a href= Group/a about board service and board skills. And because elections are not for six months, you have plenty of time to get some reading under your belt!/p pAll completed candidate self-nomination forms are published at the end of the nomination period. We call this phase Meet the Candidates and community members will be able to ask questions of you on your candidate profile page. Additionally, we will set up several webcasts for candidates to address community questions live, in a variety of time zones. /p h3 When are the next elections?/h3 pIn prior years, we held elections in the fall. This was difficult because it meant that most of the recruitment and meet the candidate work was done in August, when many humans in the northern hemisphere are on vacation. We've switched to a beginning of the year format which allows us to elect and ratify a candidate with plenty of time to get the onboarded and prepped to attend the DrupalCon North America retreat. Here is the schedule for the next election:/p ulli Community Discussion (August/September 2014)/li li Technical Setup (December/Jan)/li li Nominations (February 1-20)/li li Meet the Candidates (Feb 21 - March 6)/li li Voting (March 9 - 20)/li li Ratification amp; Communication (March 25)/li /ulpHave more questions? Never fear! We are always happy to answer them. Leave them in the comments or a href=mailto:holly@association.drupal.orgsend me an email/a./p /div/div/div

Symphony Blog: FAQ Field vs FAQ module in Drupal

Wed, 08/06/2014 - 04:20
div class=field field-type-text field-field-introtext div class=field-items div class=field-item odd pWe had been always using a href= module/a to create Frequently Asked Questions for any of our projects. But on our latest theme, a href=/drupal-theme/bizreviewBizReview/a, we switch to a new module, a href= Field/a./p /div /div /div pstrongFAQ/strong is a classic module, it is there since Drupal 6. So when we have to build a FAQ section, using this module is a no brainer. This is the FAQ module in action on our a href= theme./p p class=rtecentera href= alt=Velocity FAQ section scr=/system/files/images/blog/velocity_faq-page.jpg src=/system/files/images/blog/velocity_faq-page.jpg //a/p pnbsp;/p pa href= target=_blankread more/a/p