Skip to Content

Newsfeeds

Kickstarter updates terms: 'The creator must complete the project'

Social/Online Games - Gamasutra - 19 September 2014 - 4:33pm

The popular crowdfunding site has added some serious new stipulations to its terms of service -- which are designed to ensure backers get what they back. ...

Categories: Game Theory & Design

Video: Perfectly pitching your game in three sentences or less

Social/Online Games - Gamasutra - 19 September 2014 - 1:54pm

Speaking at GDC Europe 2014 earlier this year, Vlambeer co-founder Rami Ismail shared some useful advice on how developers can perfect the art of pitching their game. ...

Categories: Game Theory & Design

Don't Miss: The Gamasutra community's game developer flashcards

Social/Online Games - Gamasutra - 19 September 2014 - 12:10pm

Developers from across Gamasutra's community contributed to this quirky taxonomy of personalities and situations that you're likely to encounter if you spend much time in the game industry. ...

Categories: Game Theory & Design

Jonathan Brown: Generating safe markup in Drupal 8

Planet Drupal - 19 September 2014 - 11:29am

The most insecure part of a Drupal website is typically the theme. Drupal 8 is using Twig as its template layer. This is a massive leap forward. It's no longer possible to put SQL queries in a template file!

Furthermore, Drupal 8 is now taking advantage of a security feature of Twig: autoescape. Every variable in a Twig template will be escaped if it is not marked as safe. This makes it much harder to introduce XSS vulnerabilities.

Unfortunately any HTML that your module produces will end up being double-escaped and the HTML itself will be visible instead of the browser's rendering of it. The quick and dirty way to fix this problem is to wrap your string with \Drupal\Component\Utility\SafeMarkup::set:

<?php
$output = SafeMarkup::set('<div class="my-module">' . $my_variable . '<div>');
?>

But this defeats the whole point of using autoescape. The correct approach is that all HTML created by a module should be declared in a Twig template. This means that all the variables are guaranteed to be escaped. It is also very easy to implement.

First you need to declare the template in your hook_theme():

<?php
function my_module_theme(array $existing, $type, $theme, $path) {
  return array(
    'my_module_my_template' => array(
      'template' => 'my-template',
      'variables' => array(
        'variable1' => NULL,
        'variable2' => NULL,
      ),
    ),
  );
}
?>

You then need to create a Twig template file, for example my_module/templates/my-template.html.twig:

{#
/**
* @file
* Default theme implementation for my template.
*
* Available variables
* - variable1: The first variable.
* - variable2: The second variable.
*/
#}
<div class="my-template">
  This is the first variable: <b>{{ variable1 }}</b>.
  This is the second variable: <i>{{ variable2 }}</i>.
</div>

When you need to generate your html you should use the drupal_render() function:

<?php
$render = array(
  '#theme' => 'my_module_my_template',
  '#variable1' => t("First"),
  '#variable2' => t("Second"),
);

$output = drupal_render($render);
?>

Strings returned by drupal_render() are automatically marked as safe and will not be escaped again.

Categories: Drupal

Appnovation Technologies: Straight from the Source: Achieving Your Goals with osCaddie

Planet Drupal - 19 September 2014 - 11:02am
See why global non-profit organization Teach For All chose our osCaddie solution var switchTo5x = false;stLight.options({"publisher":"dr-75626d0b-d9b4-2fdb-6d29-1a20f61d683"});
Categories: Drupal

Drupal core announcements: Today there are zero Drupal 8 beta blockers! Here's what's next.

Planet Drupal - 19 September 2014 - 10:17am

As of 06:58 UTC today, September 19, there are zero Drupal 8 beta blockers. This means that, after more than nine months of focused effort, we are almost ready to release the first Drupal 8 beta!

When will Drupal 8.0.0-beta 1 be released?

Today (September 19), we have released one more Drupal 8 alpha, Drupal 8.0.0-alpha15. This alpha can be treated as a "beta release candidate". If no additional beta blockers are identified in the next 10-14 days, we will then tag the first beta! (If we do discover additional beta blockers, then we will evaluate them and adjust our timeline.)

What does beta mean?

Betas are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs, and who are prepared to rebuild their test sites from scratch if necessary. Beta releases are not recommended for non-technical users, nor for production websites.

See Dries' original announcement about the beta for more information on the beta and the criteria for beta blockers. The explanation of the Drupal 8 release management tags explains the differences between critical beta blockers and other issues impacted by the beta phase.

How can I help? Help stabilize the beta

The beta is an important milestone for Drupal 8. Help test the final alpha for critical and potentially beta-blocking bugs, and take extra care to avoid introducing regressions during this pre-beta window.

Beta deadline issues (complete by September 28)

This final pre-beta window is our final chance to complete beta deadline issues. As a reminder, changes to the following have a beta deadline:

  1. Non-critical changes to the core data model. (See the beta-to-beta upgrade path and data model stability policy and the beta-to-beta-upgrade path critical task for ongoing discussion of what is included in the Drupal 8 data model, how we will handle small data model additions, and when we will support a beta-to-beta upgrade path).
  2. Non-critical, backward-compatibility-breaking changes to the public APIs of the following critical subsystems:
    • The Configuration system
    • The Entity Field API
    • The Plugin API
    • The Menu and Routing APIs
  3. Other broad, non-critical changes that significantly break backward compatibility, at core maintainer discretion.

Beta deadline issues can be committed up until Sunday, September 28, after which there will be a freeze to ensure stability. If you have questions or concerns about completing a particular change, speak to a core maintainer about it soon.

If you know of issues that would introduce any of these changes, add the "beta deadline" issue tag so that contributors can find and help complete them before the beta. The following issues are particular priorities:

(Also see the full queue of known beta deadline issues.)

Keep in mind that API and schema additions may still be made during the beta phase, at core maintainer discretion. Limited API and data model changes will also happen during the beta phase, though core maintainers will try to isolate these changes to non-fundamental APIs or critical bug fixes. (See the ongoing beta-to-beta-upgrade path discussion.)

Beta target issues

"Beta target" issues are issues that we hope to complete early during the beta phase, but can still be added to Beta 2 or later. These are the next priority after important beta deadline issues. We especially need to work on:

(Also see the full queue of known beta target issues).

Thank you!

Many thanks to the 234 contributors who have helped resolve our 177 beta blockers in Drupal 8, and to the incredibly dedicated Drupal 8 branch maintainers. Your focus and effort is helping us build a solid Drupal 8 beta and, going forward, a better release.

Categories: Drupal

Get your app featured by Apple, here's who to contact & how - by Kyle Waring

Gamasutra.com Blogs - 19 September 2014 - 9:03am
Getting featured on the App store is a critical step in marketing your game. By getting featured by Apple, you’re getting the holy grail of advertising: wide visibility, lots of installs and subsequently– revenue! Learn how to pitch and who to contact!
Categories: Game Theory & Design

Bluespark Labs: Cleaning our repository history

Planet Drupal - 19 September 2014 - 8:49am

In our daily work we all make mistakes in our git commits. Sometimes this errors can easily be repaired just by reverting our commits. But if we are working in a public repository and we have accidentally pushed some sensitive information, we now have a problem.

That sensitive information is in our repository history and anybody who has the enough time to explore can gain access to that. Our clients or even ourselves are now dealing with a privacy issue.

We can always try to repair that commit in our local environment and push our code again using the --force parameter. But we know, when you do that, a kitten dies. And if your team members already pushed something, everything in the repository will be messed up.

So the best option is to try and fix this in a more elegant way that allow us to erase all the traces of our mistake, but preserves repository integrity.

Git provides the filter-branch command, but sometimes this powerful tool becomes too complicated and slow. In trying to find an easier way to do it, finally came across the BFG Repo-Cleaner.

This tool is an alternative to git filter-branch that provides a faster and easier way to clean git repositories. It is written in Java, so you need to make sure you have JRE 6.0 or above installed. To clean your repository you only have to follow the steps below:

Clone your repository using the --mirror option. Beforehand, you should repair manually your mistakes in the repository.

1 $ git clone --mirror git://example.com/my-repo.git

Now, download BFG and execute it against your cloned repository.
1 $ java -jar bfg.jar --strip-blobs-bigger-than&nbsp;1M&nbsp;my-repo.git
This step will remove all the blobs bigger than 1MB from your repository.

Once the index has been cleaned, examine your repository's history and then use the standard git gc command to strip out the unwanted dirty data, which Git will now recognise as surplus to requirements:
1 2 3 $ cd my-repo.git $ git reflog expire --expire=now --all $ git gc --prune=now --aggressive

Finally, once you're happy with the updated state of your repo, push it back up
1 $ git push

If everything went well, your repository won't include any of the accidentally committed files.

Here you have some common examples to use with Drupal:
Delete all files named 'id_rsa' or 'id_dsa' :
1 $ java -jar bfg.jar --delete-files id_{dsa,rsa} &nbsp;my-repo.git

Delete database dumps:
1 $ java -jar bfg.jar --delete-files *{mysql,mysql.gz}

Delete files folder:
1 $ java -jar bfg.jar --delete-folders files

We have to remark that BFG assumes that you have repaired your repository before executing it. You need to make sure your current commits are clean. This protects your current work and gives you peace of mind knowing that the BFG is only changing your repo history, not meddling with the current files of your project.

Finally, here you have some useful related links:

Tags: Drupal Planet
Categories: Drupal

First PCT GameDevs Meeting - by Tony Yotes

Gamasutra.com Blogs - 19 September 2014 - 8:44am
I hosted the first game development club meeting at the Pennsylvania College of Technology on Thursday and it went really well. Students are excited to focus on aspects of development not covered in our generic IT classes.
Categories: Game Theory & Design

Studio behind Moshi Monsters craze hit by layoffs, says report

Social/Online Games - Gamasutra - 19 September 2014 - 8:18am

UK-based Mind Candy, the company behind popular kid-friendly online game Moshi Monsters, saw a number of layoffs, according to a TechCrunch report. ...

Categories: Game Theory & Design

How I got into Gaming, Part 3 - Let the Games Begin - by William Anderson

Gamasutra.com Blogs - 19 September 2014 - 7:37am
How I got into Gaming, Part 3 - Let the Games Began
Categories: Game Theory & Design

How I got into Gaming, Part 2 - The Interview - by William Anderson

Gamasutra.com Blogs - 19 September 2014 - 7:28am
How I got into Gaming, Part 2 - The Interview with Virgin Games
Categories: Game Theory & Design

How I got into Gaming, Part 1 - by William Anderson

Gamasutra.com Blogs - 19 September 2014 - 7:23am
How I personally got into game development back in the early days of gaming.
Categories: Game Theory & Design

One more time!: The role of self-determination and gamer identity in persistence - by Wai Yen Tang

Gamasutra.com Blogs - 19 September 2014 - 7:22am
A study examining into the role of self-determination and gamer identity on persistence in gaming
Categories: Game Theory & Design

OG Rebuilder

New Drupal Modules - 19 September 2014 - 7:05am

The OG Rebuilder module rebuilds the group's child nodes permissions whenever the group access configuration is changed.

Development sponsored by DRI Discovery/Reinvention/Integration/

Categories: Drupal

Re-aligning the elements of charted Space – an addict’s analysis of Destiny. - by Jedrzej Czarnota

Gamasutra.com Blogs - 19 September 2014 - 7:04am
This blog post discusses Bungie's Destiny and the array of its breakthroughs. Those incremental innovations add up to form a new experience for consoles, one that integrates influences from many genres, and MMOGs in particular.
Categories: Game Theory & Design

floskelwolke

New Drupal Modules - 19 September 2014 - 6:12am

Floskelwolke is a block Mudule, which imports the CSV data of the Web application Floskelwoke.de, a project of Udo Stiehl and Sebastian Pertsch.

Code comes as soon as possible...

Categories: Drupal

Code Karate: Drupal 7 Honeypot Module

Planet Drupal - 19 September 2014 - 5:48am
Episode Number: 169

In this tutorial you will learn about the Honeypot module. The Honeypot modules is a SPAM prevention module that uses a hidden form field to catch SPAM bots from posting onto your site. This tutorial shows you how to configure the module to work on various forms on your site.

Tags: DrupalFormsWebformDrupal 7Drupal PlanetSpam Prevention
Categories: Drupal

A DC Developer’s View from the White House Game Jam - by Christopher Totten

Gamasutra.com Blogs - 19 September 2014 - 5:23am
How participating in a Game Jam at the White House brought our new American University Game Lab together and taught us about game development in the Washington, DC area.
Categories: Game Theory & Design
Syndicate content


Google+
about seo