Skip to Content

Drupal

Nikro: Moldcamp 2015 - Session Submissions!

Planet Drupal - 12 May 2015 - 6:56am

If you haven't heard yet, we've announced earlier that Moldcamp 2015 is on it's way! Second edition of the Drupal Camp hosted by a small country in the Eastern Europe - Moldova.

Tags: 
Categories: Drupal

Drupalize.Me: Installing and Configuring Dreditor

Planet Drupal - 12 May 2015 - 6:02am

With DrupalCon Los Angeles underway we thought it might be a good time to introduce (or reintroduce) folks to [Dreditor](https://dreditor.org/) (short for "Drupal editor"). Dreditor is a collection of user scripts, which alter browser behavior on specific pages on the drupal.org domain. The features of dreditor are mostly helpful in the issue queue and during the patch review process.

We have a video [Installing and using Dreditor](https://drupalize.me/videos/installing-and-using-dreditor) if you'd like to follow along, but since recording installation of Dreditor is even easier. Let's take a look at the changes, and how we can use this powerful tool to make interacting with the issue queue easier.

Categories: Drupal

Cocomore: MySQL - Setup

Planet Drupal - 12 May 2015 - 5:58am

When setting up a MySQL Server there are a lot of things to consider. Most requirements depend on the intended usage of the system.

read more

Categories: Drupal

Scald Dailymotion

New Drupal Modules - 12 May 2015 - 4:28am

Scald Dailymotion is a video provider for the Scald module.

Categories: Drupal

Scald Vimeo

New Drupal Modules - 12 May 2015 - 4:14am

Scald Vimeo is a video provider for the Scald module.

Categories: Drupal

ERPAL: Manage agile projects with structure and control

Planet Drupal - 12 May 2015 - 3:45am

In the previous part of our blog series, we talked about unrealistic budgets and deadlines. Today our focus is on structure and control in agile projects.

In software development, there’s a lot of conjuring and experimentation going on with agile projects, and many homemade definitions for the word "agile" are floating around. But agile only means that one reacts to changing project requirements, and is thus flexible during development, with the result being a software product that really provides value when used.

In large projects that extend over a longer period of time, conditions change; it’s natural. In order to maintain the defined project objectives despite these new conditions, the existing requirements need to be checked. To achieve this, it’s necessary to know what’s already been implemented and what’s still outstanding. Scrum and agile approach do not imply that:

  • there’s no planning in advance,
  • there’s no concept, or that
  • there aren’t any acceptances.

An agile project follows the same rules as I’ve described earlier, but changes are allowed. As always, you have to consider that unplanned things cannot be controlled. Often, the billing procedures are controversial. I’ve already written a post on this topic: Agile work at a fixed price. The very concept of an agile project provides a framework within which to move and control changes. This framework ensures that a path that was possibly set wrong from the start – that won’t lead to the defined target – simply is not taken. If the plan in an agile project doesn’t exist in the form of a concept, the current status of the project can’t be determined and evaluated.

 

Other blog posts of this series:

6 steps to avoiding unrealistic budgets and deadlines in projects

6 rules to follow to promote communication in projects

3 things to consider when creating project specifications

Agile projects for a fixed price? Yes you can!

Setting objectives in projects with these 3 rules

These 3 questions help you to ensure satisfactory project results

Categories: Drupal

Scald YouTube

New Drupal Modules - 12 May 2015 - 1:35am

Scald Youtube is a video provider for the Scald module.

Categories: Drupal

Online Theme Editor

New Drupal Modules - 12 May 2015 - 1:05am
Categories: Drupal

Community Media Series

New Drupal Modules - 12 May 2015 - 12:26am

With Community Media Series you can create series and automatically create cm_shows and cm_airings based on specified criteria. The idea is to radically simplify creating recurring shows, without having to add each show and its airings one by one.

Categories: Drupal

Deeson: We're hiring: Creative Director

Planet Drupal - 12 May 2015 - 12:23am
Could you be the one to make your mark here at Deeson?

We're looking for a Creative Director. That's a brand new role for us so you'll be the very first CD to grace our offices.

A lot of expectation? Maybe. But the perfect opportunity to lead our team of talented designers and put your stamp on some award-winning work.  

Why now? 

In short, we've increased our portfolio of clients and our designers are in demand. 

It's a perfect time for someone new to come and join our dynamic leadership team, contributing to key decisions as we enter our next phase of growth.

We're at a stage where we feel ready for a strong-minded Creative Director to help develop the team and help shape the direction of the agency.  

Why me?

We're looking for someone talented, that's a given.

But as well as a killer portfolio, we want someone who has an interest in nurturing the skills of those in their team. Development is really important to us at Deeson; we'll be looking for ideas about how you would grow your team's skills and confidence.    You could be a Senior Designer with tonnes of managerial experience looking for your next move or a Creative Director looking for your next challenge. If you fit the criteria we'd love to hear from you.   What else? A great bunch of people to work with and a progressive agency culture.   A huge range of benefits, including flexi working, team lunches and an unlimited training budget.    Oh, and we're located in one of the UK's most beautiful cities too. Check out our full story here.   Read the full job spec and apply here.       

 

Categories: Drupal

Deeson: Site configuration strategy (or how to manage your settings.php files)

Planet Drupal - 12 May 2015 - 12:10am

Managing site configuration across multiple hosting and staging environments can get complicated, and if each one of these requires a settings.php file making sure that you consistently apply configuration can be a nightmare.

This is especially true when you start requiring different files at different points – it's very easy to lose track of which setting is where.

A typical example here at Deeson might be a site that's usually hosted on Acquia's platform, but that we need to be able to work locally on (we use VDD for this).

That probably gives you 3 settings.php files: one for your local, one for the live domain name and one for Acquia's staging URLs. We'll also have different configuration for each of these. An example is where both reroute email and shield need to be disabled only on live, if our site has 3rd party integrations then we'll configure different API keys on staging and caching is always on on live.

So, how do we solve this?

In much the same way that we don't create a site-wide views feature, and instead we use a modular approach – for example one feature for news and another for events, we should do the same with our configuration and split it up. We don't do this by environment, but by module. So all the performance stuff together, all the security stuff together etc.

For example, you might have a reroute email file, that could read something like this:

$conf['reroute_email_address'] = "rerouted_mail@example.com"; $conf['reroute_email_enable_message'] = TRUE; $conf['reroute_email_enable'] = TRUE; if (SETTINGS_LIVE_DOMAIN) { $conf['reroute_email_enable'] = FALSE; }

This is clearer and less error prone than the situation that can occur where you can't instantly tell which setting will apply in a given situation. And by coding your conditions defensively you'll improve security.

So it's possible that you might still have those three settings.php files, but instead of adding config directly to them all they do is define the database settings and then do something like this:

// e.g. dev, stage or prod or read from $_ENV['AH_SITE_ENVIRONMENT'] on Acquia. // Master.inc could read this instead of the “scopes” concept? define('SETTINGS_ENVIRONMENT', 'prod') // e.g. local or acquia define('SETTINGS_HOSTING', 'acquia'); <?php // TRUE only on the actual live domain - so any testing domains, including the "live preview" should give this FALSE. define('SETTINGS_LIVE_DOMAIN', FALSE | TRUE); foreach (glob('sites/all/conf/*.settings.inc') as $file) { require_once $file; }

See that glob call? Create files in a new dir – sites/all/conf – like thing.settings.inc and place your config in there, using 'if' statements to react to the different envrionments.

Glob sorts by file name, so prefix each of these files with a number if you need them to be in a specific order, e.g 00-master.inc, 10-reroute-email.inc.

Here are some suggestions for files you might create (all to end in .settings.inc):

  • drupal-defaults (Maybe copy settings.default.php in here and update it keep it in sync with core updates?)
  • master
  • warden
  • shield
  • reroute_email
  • mandrill
  • performance (caching, aggregation etc. Only force these on live, if you must)
  • your-api-here

In this manner we can create sets of default settings php files which are likely to be common across projects. This makes initial setup to our standards and best practice simple. Any deviation from the standards can then be configured and described in the main settings file for the site.

Categories: Drupal

DrupalCon News: Session Submission Live!

Planet Drupal - 11 May 2015 - 9:21pm

With the call for papers officially open, we wanted to take a moment to give you all of the details you should know about sessions: what new and cool tracks we are offering, how to submit an awesome session submission, and how session selection works.

 

Categories: Drupal
Syndicate content


Google+
about seo