Skip to Content

Newsfeeds

Drupal core announcements: Drupal core updates for September 4, 2014

Planet Drupal - 4 September 2014 - 2:59am
What's new with Drupal 8?

It has been a month since the last update on Drupal core development. In the meantime we met and worked hard together at TCDrupal and Drupalaton at the start of August triaging outstanding critical issues and resolving some. Also we collaborated on making Drupal's frontend better at Frontend United at the end of the month.

We've been doing such a great job taking care of the beta blocker issues that we are currently down to only one beta blocker as of this writing. What does this mean? Once we are down to no beta blockers left, a final alpha release is published. If there are no more beta blockers identified during a two-week window, the first beta release is published. Then we'll focus on resolving the hundred or so remaining critical issues to get to release candidates (once all of them are resolved).

Right now, help with the remaining beta blocker as well beta deadline and beta target issues is most welcome. Beta target issues may get in anytime later, but beta deadlines may not unless re-evaluated for inclusion regardless.

The best opportunity to get to work with Drupal developers in person is the 9 (nine) days of sprint opportunities coming up at the end of September at and around DrupalCon Amsterdam. It is the best way to learn Drupal 8 hands-on and help on the way.

Where's Drupal 8 at in terms of release?

Last week, we fixed 8 critical issues and 12 major issues, and opened 4 criticals and 7 majors. That puts us overall at 104 release-blocking critical issues and 644 major issues.

Where can I help? Top criticals to hit this week

Each week, we check with core maintainers and contributors for the "extra critical" criticals that are blocking other work. These issues are often tough problems with a long history. If you're familiar with the problem-space of one of these issues and have the time to dig in, help drive it forward by reviewing, improving, and testing its patch, and by making sure the issue's summary is up to date and any API changes are documented with a draft change record, we could use your help!

More ways to help
  • Pick a critical issue or beta deadline issue, take the time to thoroughly read the issue (including doing some background reading if necessary to understand the problem space), and then update the issue summary for the issue. Include a summary of the current status and remaining tasks for the issue, and identify any API changes the issue would introduce. Consider whether the change would require a change record or updates to existing change records. Consider what the implications of not resolving the issue would be, or of resolving it after the first beta or after release.
  • We also need help writing help text for core modules like Field UI, Image, Taxonomy and Toolbar. This is an easy way to learn the Drupal Core contribution process and start contributing to Drupal Core.

As always, if you're new to contributing to core, check out Core contribution mentoring hours. Twice per week, you can log into IRC and helpful Drupal core mentors will get you set up with answers to any of your questions, plus provide some useful issues to work on.

You can also help by sponsoring individual Drupal core development.

Notable Commits

Some of the best of git log --since "August 4, 2014" --pretty=oneline (277 commits in total):

  • Issue 1510544 by swentel, Bojhan, Gábor Hojtsy, merlinofchaos, Cottser, Wim Leers, plopesc, aspilicious, sannejanssen, larowlan, tim.plunkett, nod_: Fixed Show previews in front-end theme, able to select different view modes. This was a long time coming. Finally, your node preview will not appear on the backend!
  • Issue 2248767 by effulgentsia, beejeebus, alexpott: Use fast, local cache back-end (APCu, if available) for low-write caches (bootstrap, discovery, and config). Improves performance for some critical data a great deal.
  • Issue 2224761 by Gábor Hojtsy, alexpott, pfrenssen, effulgentsia, xjm, mlncn: Add a generic way to add third party configuration on configuration entities and implement for field configuration. Resolved a beta blocker by adding a facility for configuration entities to support third party settings. To be used for node types and other things as needed as well. Provides a simple solution when a full-on plugin architecture as in views is not suitable, but extension mechanisms are needed for configuration.
  • Issue 1966436 by naveenvalecha, cesarmiquel, Berdir, mr.york, jlbellido, segi, vasi1186, Leksat, Gábor Hojtsy, Schnitzel, grisendo, Aron Novak, likin, penyaskito, vijaycs85, kfritsche, fago: Fixed Default *content* entity languages are not set for entities created with the API. Now made Drupal properly create entities in the right language regardless of through the UI or API (eg. when adding a tag or uploading a file). Also makes entities created from the creation of the site be in the right language always.
  • Issue 2295469 by Cottser, dawehner | effulgentsia: Add support for static permission definitions with *.permissions.yml. Makes it possible to simply define permissions in a simple YAML file making this system consistent with several other in Drupal 8.
  • Issue 2271529 by attiks, alexpott, Lowell, YesCT, Jelle_S | mdrummond: Move breakpoint settings to theme and module *.breakpoints.yml files at root level. Improves developer experience providing breakpoints.
  • Issue 2317085 by pfrenssen | rteijeiro: Added the possibility to create a REST export when creating a new view. Makes it much easier to create simple web service views of Drupal content.
  • Issue 2250119 by ParisLiakos, Devin Carlson: Run updates in a full environment. Now that updates are not supposed to operate in API-incompatible environments, their implementation was unified with any other Drupal environment.

You can also always check the Change records for Drupal core for the full list of Drupal 8 API changes from Drupal 7.

Drupal 8 security

With the API stabilizing we are focusing on security again. In our last issue we already reported on Twig autoescape now being on, sometimes resulting in unwanted HTML strings appearing on the page because of double escape bugs. Please check the meta issue if you see these.

  • The router service is now access aware so there is no need now to separately access check the routes returned from it.
  • Building on this, now menu links, shortcuts and link fields use a unified path validator service..
Drupal 8 Around the Interwebs Drupal 8 in "Real Life" Whew! That's a wrap!

Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.0.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. Read more about how you can volunteer to help with these posts!

Categories: Drupal

Unlock Your Creative Star Power - by Shelly Warmuth

Gamasutra.com Blogs - 4 September 2014 - 2:42am
The only way to make your mark as a developer, or for your games to make their mark in the world is to explore the abilities of your tools and employ them in new and ingenious ways.
Categories: Game Theory & Design

This Week in Archmage Rises: The Move - by Thomas Henshell

Gamasutra.com Blogs - 4 September 2014 - 2:25am
Building a top-notch team and returning to civilization
Categories: Game Theory & Design

PAX Prime: an orange post-mortem - by Alex Nichiporchik

Gamasutra.com Blogs - 4 September 2014 - 1:51am
Let's do PAX Prime we said, it's going to be fun we said. Chronological post-mortem of 10 days of PAX Prime Insanity.
Categories: Game Theory & Design

tanay.co.in: Telize - Simple IP-based Redirection Module for Drupal Sites

Planet Drupal - 4 September 2014 - 12:54am

Was working with a customer who required simple IP-based redirection for Drupal Sites.

Was analyzing the various existing options:

  • Smart IP : Looks good. But sets sessions which break Varnish Caching. Most Drupal sites run from behind Varnish Reverse Proxy and using Smart IP would mean either forgoing varnish caching or having to add complex VCL rules.

  • Geo-Redirect : Again, would not work well with Varnish. The first redirection will be cached on Varnish and all subsequent users from different countries might be redirected to the cached redirection. Requires additional GeoIP.dat file to be downloaded and this should be updated frequently.

  • Using MaxMind API : Most hosts like Acquia allow the Maxmind API to be integrated on the balancers so that Varnish maintains country code in the cache (preventing the same redirection to be cached). The country code is added to the headers in both request and response. This is the ideal way to implement GeoIP for any enterprise site. But it requires dedicated load balancers, and there is no plug-and-play module to utilize the API requiring custom development.

  • And a plethora of other modules that break varnish in similar ways..

What I wanted:

  • Simple country-based redirection

  • Should not break caching / varnish

  • Should not require GeoIP datafiles to be downloaded and maintained

  • Should be simple and light-weight

  • Good-to-have, though not mandatory : Zero or Low subscription cost

A hour-long search resulted in nothing significantly useful for Drupal.

Finally found this API : http://www.telize.com/ . Sounded promising.

  • The API powering the site is opensource

  • There is no rate limit of any sort at the moment, and the service is free for everyone to use.

  • Used GeoLite data created by MaxMind

The API was exciting but still it was not something that could be plug-n-play’ed on Drupal.

Built this module - https://www.drupal.org/project/telize

  • Simple Country-based redirection

  • Redirection happens at front-end through JS. Works on top of Varnish

  • Does not set any session cookies. Won’t break your Varnish

  • No subscription required

  • No additional files/libraries required

Try it out of you have simple GeoIP redirection requirements.

 
Categories: Drupal

Cross Platform Considerations for Designers - by Ulyana Chernyak

Gamasutra.com Blogs - 4 September 2014 - 12:44am
Multi platform releases are becoming more popular with technological advances making development viable. For today's post we're going to examine some of the details to keep in mind when moving a game from one platform to the other
Categories: Game Theory & Design

Don't Sit Idly By - The Wake Of "GamerGate" - by Mary Lee Sauder

Gamasutra.com Blogs - 3 September 2014 - 10:16pm
How the gaming community can step up and handle these issues correctly this time.
Categories: Game Theory & Design

REST API

New Drupal Modules - 3 September 2014 - 2:12pm

Provides tools and an API for developers to leverage to rapidly build out RESTful services. More to follow

Categories: Drupal

osCaddie - Google Cloud Storage

New Drupal Modules - 3 September 2014 - 1:53pm
Overview
Categories: Drupal

Visiting China and Japan

Dries Buytaert - 3 September 2014 - 10:55am
Topic: Drupal

After spending the summer in Boston, I'm ready to fly across the world ... literally, as I'm leaving on a two week trip to China and Japan later this week. I'm very excited about it as I've never had the opportunity to see either of these countries.

I will arrive in Beijing on Saturday, September 6th, for the Young Global Leaders Annual Summit. A private path from where I'll be staying leads to a non-restored section of the epic Great Wall of China. Exploring this truly untouched piece of Chinese history still in its original landscape should be a special experience! Stay tuned for photos.

Following my time in Beijing, I'll transfer to Tianjin to attend Summer Davos. In addition to that, we're organizing a meetup with the local Drupal community - https://groups.drupal.org/node/434658. If you are in the area on September 10th, please stop by for a drink. I'd love to meet you and learn about the state of Drupal in China.

I'll end my two week trip in Tokyo, Japan. My time will be split between meeting the local Drupal community - https://groups.drupal.org/node/440198, understanding the adoption rate of Drupal in the Japanese market, and attending private meetings with digital agencies, Acquia partners and others to learn about the state of the web and digital in Japan.

Xièxiè and dōmo arigatō to those that have helped plan these events and gather the Drupal community for some fun evenings!

If you aren't able to make either Drupal meetup, feel free to leave your thoughts in the comments.

Categories: Drupal

Dries Buytaert: Visiting China and Japan

Planet Drupal - 3 September 2014 - 10:55am
Topic: Drupal

After spending the summer in Boston, I'm ready to fly across the world ... literally, as I'm leaving on a two week trip to China and Japan later this week. I'm very excited about it as I've never had the opportunity to see either of these countries.

I will arrive in Beijing on Saturday, September 6th, for the Young Global Leaders Annual Summit. A private path from where I'll be staying, Commune by the Great Wall, leads to a non-restored section of the epic Great Wall of China. Exploring this truly untouched piece of Chinese history still in its original landscape should be a special experience! Stay tuned for photos.

Following my time in Beijing, I'll transfer to Tianjin to attend Summer Davos. In addition to that, we're organizing a meetup with the local Drupal community - https://groups.drupal.org/node/434658. If you are in the area on September 10th, please stop by for a drink. I'd love to meet you and learn about the State of Drupal in China.

I'll end my two week trip in Tokyo, Japan. My time will be split between meeting the local Drupal community - https://groups.drupal.org/node/440198, understanding the adoption rate of Drupal in the Japanese market, and attending private meetings with digital agencies, Acquia partners and others to learn about the state of the web and digital in Japan.

Xièxiè and dōmo arigatō to those that have helped plan these events and gather the Drupal community for some fun evenings!

If you aren't able to make either Drupal meetup, feel free to leave your thoughts in the comments.

Categories: Drupal

Elder Scrolls Online developer hit with post-launch layoffs

Social/Online Games - Gamasutra - 3 September 2014 - 10:04am

Elder Scrolls Online progenitor Zenimax Online Studios has suffered an unknown number of layoffs today as the studio restructures to support the game in the wake of its April launch. ...

Categories: Game Theory & Design

Cruiskeen Consulting: Yet Another Drupal News Source

Planet Drupal - 3 September 2014 - 9:55am

The world is full of Drupal news sources - Planet Drupal, Drupal Fire, Groups.Drupal.Org, and many many more.  So of course we've decided to build another one. 

Why?  Because we can. And because we've been spending a lot of time playing around with Rebelmouse.  So - aggregating content from all over the planet, we bring you Drop News

Categories: Drupal

Sunken Ship

New RPG Product Reviews - 3 September 2014 - 9:14am
Publisher: DramaScape
Rating: 4
Fancy a swim?

This battlemap (presented in the usual multi-page print out and stick together format with no grid, hex grid or square grid plus a massive single JPEG for virtual table top use) shows scattered debris of a suken ship for your party to explore. The accompanying text describes it as being deep but the colourscheme just doesn't work for that, it looks far more shallow. Light tails off pretty quickly when you dive - 10 fold with every 75 m of descent if I recall my training correctly - yet the colours look like no more than a metre or so of water over sand in direct sunlight! If this is a deep wreck the scene needs to be darker and more blue.

The wreck itself is lying on the surface of the sea bed, and is remarkably debris-free although there isn't much left. There are also six sea mines scattered around, so care needs to be taken when moving around the area. A devilish GM could be inventive with underwater currents pushing divers or the mines around even if they are (as shown in the cover illustration) tethered by chains to the seabed.

Useful if your plot involves retrieving something from a wreck or finding out why a ship sunk... lay in a supply of shark miniatures or perhaps a few octopi!
Categories: Game Theory & Design

Phase2: Better Development Through Emotional Intelligence

Planet Drupal - 3 September 2014 - 9:11am

I am unabashedly an engineer. I obsess over the pursuit of finding the most efficient solution to any problem.

In the realm of open source software, this approach has served me well. We read, reverse-engineer, fork, improve, and share. I want my process to be faster, more flexible, and maintainable for the long haul.

As I’ve investigated different methodologies, one characteristic I constantly underestimate is the team dynamic. I tend to pigeon-hole my mind into thinking that the solution to a problem is the most important goal.

Hey look! There’s a problem! I must find a solution for it.

  • What if complex problems can’t be solved by me?
  • What if, when I suggest a tool or a programming philosophy, it masks the need to dive deeply into other factors?

The more I researched my approach, I came across a concept that is vital to team effectiveness when solving complex problems: emotional intelligence.

Emotional Intelligence, sometimes referred to as EQ (emotional intelligence quotient) to complement IQ (intelligence quotient), is the ability to be aware of, express, control, reason, and interpret emotions appropriately.

Within a team, many, many, many studies have shown that EQ, more than IQ, is the key to solving complex problems.

The team dynamic is engrained with the DNA of open-source projects. Any Drupal issue queue or Packagist library commit log supports that.

The better question I ask myself, however, is:

  • Are the teams I work on the most emotionally intelligent?
  • If not, what am I doing to improve that metric?

Peeling back this onion revealed the societal constructs that affected how I view an effective team.

Typically, I look to the most technical people I know for answers. In some cases, I follow the stereotypical engineer playbook of positing a hypothesis, demanding evidence, and playfully browbeating a decision.

Put another way, how many times have I jokingly used the phrase ” Are You  doing it wrong?” and is that the most effective solution?

As the research suggested, this emotionally oblivious approach was philosophically incongruent with proven science!

  • How could I call myself an engineer?!?!
  • How could I obsess about the pursuit of efficiency and solution, when my own attitude was blunting my team’s effectiveness?

I needed to do better.

I needed to find something, rooted in math and science, that helped me understand how to refactor my way of thinking.

I then learned about perspective and heuristic techniques. Perspective is how one looks at a problem. Heuristic is the mental shortcut one uses to arrive at a solution. Both are shaped by experience and knowledge, but the nuance in process from a variety of individuals is key.

Dr. Scott Page elaborates :

The diversity of an agent’s problem-solving approach, as embedded in her perspective-heuristic pair, relative to the other problem solvers is an important predictor of her value and may be more relevant than her ability to solve the problem on her own. Thus, even if we were to accept the claim that IQ tests, Scholastic Aptitude Test scores, and college grades predict individual problem-solving ability, they may not be as important in determining a person’s potential contribution as a problem solver as would be measures of how differently that person thinks.

It opened my eyes to how I’ve been going about solving complex problems all wrong.

In the context of a complicated problem, there is a higher likelihood of finding a global optimum (the best solution) when you have a diverse set of team members with local optimum (their best solution). Put simply, I needed to engage more (not less) with people who were different than me.

In essence, given the right conditions, diversity trumps ability!

What’s interesting about this research, however, is the fact that communication among members with different perspectives is very difficult.

In fact, as Dr. Page continues:

Problem solvers with nearly identical perspectives but diverse heuristics should communicate with one another easily. But problem solvers with diverse perspectives may have trouble understanding solutions identified by other agents.

Thus, we’ve come full circle to why EQ is so important.

If team members are not in-tune with each other, the benefits gained from their diversity can be lost. It is vital, therefore, in my unabashed obsession to being an engineer, that I not only need to improve my EQ, but surround myself with colleagues who have a high EQ and learn from them.

So what are the characteristics of high EQ individuals? Statistically, who has high EQ?

Some of our thought leaders here at Phase2 have answered that question.

If you’re interested in learning more, find me as I share my ideas on a building a more inclusive community at various conferences and camps!

Categories: Drupal

Dwellers In Nightmare

New RPG Product Reviews - 3 September 2014 - 8:37am
Publisher: Aegis Studios
Rating: 4
This is a collection of pre-generated characters mostly suitable for use as NPCs in a Glimpse the Beyond game. One or two could be used as player-characters if you need one in a hurry, but most are more suitable to NPC/monster use.

The introductory notes, as well as harbouring a small rant about respect and consent, suggests that these are just a framework, a basis which can be messed around with as much as individual players or the Talespinner (GM) might want before using them.

A standard layout is used. There's a page giving the character's backstory including how their life has been changed by the magical chaos that struck the world, showing both what they did before and what they are doing now. Brief notes about how each character might fit in and what you might want to change (generally mechanics rather than story) are included, and then there's a full-page character sheet ready filled out. There is also a sketch of the character.

It's a useful resource, particularly if you don't enjoy character creation, but the characters themselves - or at least their backstories - are quite limited. Of course, those are open to being changed!
Categories: Game Theory & Design

Michael J. Ross: Drupal 8 Core's Own Directory

Planet Drupal - 3 September 2014 - 8:08am

By

This article was published in the print magazine Drupal Watchdog, Volume 4 Issue 1, 2014-05, on page 21, by Tag1 Publishing. The magazine was distributed at Drupalcon Austin, 2014-06-02.

Prior to Drupal 8, the core directories (includes, misc, modules, profiles, scripts, and themes) were located in the installation's root directory. Drupal 8 consolidates them into a new "core" subdirectory, which tidies up the root directory and should make it easier to track changes to core versus contrib or custom files. There are still three root subdirectories for modules, profiles, and themes, which can be used for custom and contrib projects. Each directory initially contains only a README.txt file explaining the repurposing and how developers can still use the pre-D8 "sites/all" scheme.


Figure 1. Drupal 8 root directories and files

Copyright © 2014 Michael J. Ross. All rights reserved.

Categories: Drupal

Michael J. Ross: Drupal 8 Core Theme Improvements

Planet Drupal - 3 September 2014 - 8:07am

By

This article was published in the print magazine Drupal Watchdog, Volume 4 Issue 1, 2014-05, on page 21, by Tag1 Publishing. The magazine was distributed at Drupalcon Austin, 2014-06-02.

When custom and contributed themes are added to a fresh Drupal installation, the core themes often fade into the background, even though they are valuable, particularly for learning theming. In Drupal 7, those core themes are: Bartik (enabled by default), Garland (Drupal 6's default), Seven (optimized for site administration), and Stark (minimalist and thus useful for module output debugging). The sole template engine is the venerable PHPTemplate. Drupal 8 adds Twig as the canonical template engine. Garland is gone, while Bartik, Seven, and Stark have been HTML5-ified and Twig-ified.


Figure 1. Drupal 8 core themes

Copyright © 2014 Michael J. Ross. All rights reserved.

Categories: Drupal

Michael J. Ross: Drupal 8 Core Module Changes

Planet Drupal - 3 September 2014 - 8:05am

By

This article was published in the print magazine Drupal Watchdog, Volume 4 Issue 1, 2014-05, on page 20, by Tag1 Publishing. The magazine was distributed at Drupalcon Austin, 2014-06-02.

Compared to its predecessor, Drupal 8 offers website builders far more capabilities without the use of contributed modules, because it incorporates many of the most popular ones into core (e.g., Actions, CKEditor, Configuration Manager, Entity, and Views), as well as useful field types (e.g., Datetime, E-mail, Entity reference, Link, Options, and Telephone). Conversely, less popular core modules (e.g., Dashboard, OpenID, Overlay, PHP, and Poll) have been dropped. These improvements greatly increase the range of websites that can be built with vanilla Drupal, and reduce the time spent downloading commonly-used modules and scrolling past rarely-used ones.


Figure 1. Drupal 8 core modules sample

Copyright © 2014 Michael J. Ross. All rights reserved.

Categories: Drupal

Michael J. Ross: Admin Toolbar Changes in Drupal 8

Planet Drupal - 3 September 2014 - 8:03am

By

This article was published in the print magazine Drupal Watchdog, Volume 4 Issue 1, 2014-05, on page 20, by Tag1 Publishing. The magazine was distributed at Drupalcon Austin, 2014-06-02.

In Drupal 7, site administrators can utilize its core Toolbar module for speeding navigation. Drupal 8's equivalent improves upon it, sporting a more readable interface, with clear icons. Admin menu items are grouped into: "Manage" (encompassing the menu items of its predecessor, with "Modules" renamed to "Extend"), "Shortcuts", and a user menu for profile management and logging out. The toolbar is responsive to the device's screen width, switching to a vertical orientation for narrow displays — which can be forced by clicking the arrow button on the far right of the toolbar's (white) second level.


Figure 1. Drupal 8 admin toolbar vertical

Copyright © 2014 Michael J. Ross. All rights reserved.

Categories: Drupal
Syndicate content


Google+
about seo