Planet Drupal

Subscribe to flux Planet Drupal
Drupal.org - aggregated feeds in category Planet Drupal
Mis à jour : il y a 39 min 8 sec

GVSO Blog: [GSoC 2016: Social API] Week 10: A Social Post implementer

mer, 03/08/2016 - 07:42
[GSoC 2016: Social API] Week 10: A Social Post implementer

Week 10 is over, and we are only two weeks away from Google Summer of Code final evaluation. During these ten weeks, we have been rebuilding social networking ecosystem in Drupal. Thus, we created the Social API project and divided it into three components: Social Auth, Social Post and Social Widgets.

gvso Wed, 08/03/2016 - 01:42 Tags Drupal Drupal Planet GSoC 2016
Catégories: Elsewhere

Galaxy: GSoC’ 16: Port Search Configuration module; coding week #10

mer, 03/08/2016 - 00:47

Google Summer of Code 2016 is into its final lap. I have been porting the search configuration module to Drupal 8 as part of this program and I am into the last stage, fixing some of the issues reported and improving the module port I have been doing for the past two months.
Finally, I have set up my Drupal blog. I should have done it much more earlier. A quick advice to to those who are interested in creating a blog powered by Drupal and run it online, I made use of the openshift to host my blog. It gives the freedom to run maximum of three applications for free. Select your favorite Drupal theme and start blogging.
So, now lets come back to my project status. If you would like to have a glance at my past activities on this port , please refer these posts.
Last week I was mainly concentrating on fixing some of the issues reported in the module port. It was really a wonderful learning experience, creating new issues, getting reviewed the patches, updating the patches if required and finally the happiness of getting the patches committed into the Drupal core is a different feeling. Moreover, I could also get suggestions from other developers who are not directly part of my project which I find as the real blessing of being part of this wonderful community.

The module is now shaping up well and is moving ahead in the right pace. Last week, I had faced some issues with the twig and I was resolving it. The module is currently available for testing. I could work on some key aspects of the module in the past week. I worked on the namespace issues. Some of the functions were not working as intended due to the wrong usage of the PSR namespace. I could fix some of these issues. Basically, PSR namespaces helps to reuse certain standard functions of the Drupal API framework. They are accessed using the 'use' keyword. We can name the class locations using the namespace property.
For instance, if I want to use the Html escape function for converting special characters to HTML format,
use Drupal\Component\Utility\Html;
Now, $role_option s= array_map('Html::escape', user_role_names())
Hope you got the idea. Here I could have written the entire route/path of thee escape function. But through the usage of the namespace, I just need to define the route at the beginning and later on it can be used for further implementations n number of times.
The user_role_names() retrieved the names of the roles involved. This is an illustration of the usage of namespace. This is really an area to explore more. Please do read more on this, for better implementation of the Drupal concepts.

In the coming days, I would like to test the various units of the module ported, fix the issues if any and bring up a secure, user friendly search configuration module for Drupal.
Hope all the students are enjoying the process and exploring the Drupal concepts. Stay tuned for the future updates on this port process.

Tags: drupal-planet
Catégories: Elsewhere

Cocomore: „Memories“ and more: These new features make Snapchat even more attractive for businesses

mer, 03/08/2016 - 00:00

Until recently one of the biggest contradictions in social media was called: Snapchat and consistency. In early July Snapchat put an end to this. The new feature "Memories" now allows users to save images. Next to "Memories" Snapchat further developed the platform also on other positions. We show what opportunities the new changes offer for businesses.

Catégories: Elsewhere

Janez Urevc: Release of various Drupal 8 media modules

mar, 02/08/2016 - 22:36
Release of various Drupal 8 media modules

Today we released new versions of many Drupal 8 media modules. This release is specially important for Entity browser and Entity embed modules since we released the last planned alpha version of those modules. If there will be no critical bugs reported in next two weeks we'll release first beta versions of those modules.

List of all released modules:

slashrsm Tue, 02.08.2016 - 22:36 Tags Drupal Media Enjoyed this post? There is more! We had great and productive time at NYC sprint! Sam Morenson is thinking about media in Drupal core Presentations about various Drupal 8 media modules

View the discussion thread.

Catégories: Elsewhere

Phponwebsites: Multiple URL alias for a node in pathauto - drupal 7

mar, 02/08/2016 - 16:38
   As we discussed in my previous post, clean URL is one of the option to improve SEO. We've module called pathauto to clean URLs in drupal 7. It can allow us to set alias for content types, files, users & taxonomies. But we can set only one URL alias for a content type in drupal 7. You can set URL alias for a content type at admin/config/search/path/patterns. It looks like below image:




   Suppose you need two path for a content. For instance, the URL alias for a article need to node title and also article/node-title. Is it possible to set multiple path alias for a content type in drupal 7? Yes it is possible in drupal 7. We can set multiple URL alias for a conten type programmatically using pathauto module in drupal 7. We need to insert our path alias into the "url_alias" table while inserting & updating a node and remove path alias When delete a node.

Add URL alias programmatically when insert and update a node using pathauto module in drupal 7:
    For instance, I've choosen article content type. We need to insert & update a URL alias into the "url_alias" table using hook_node_insert() & hook_node_update() in drupal 7.


/**
 * Implements hook_node_insert()
 */
function phponwebsites_node_insert($node) {
  if ($node->type == 'article') {
    //save node alias
    _phponwebsites_insert_update_alias($node);
  }
}

/**
 * Implements hook_node_update()
 */
function phponwebsites_node_update($node) {
  if ($node->type == 'article') {
    //update node alias
    _phponwebsites_insert_update_alias($node);
  }
}

/**
 * Insert and update alias for course
 */
function _phponwebsites_insert_update_alias($node) {
  module_load_include('inc', 'pathauto');
  $title = pathauto_cleanstring($node->title);

  $values['source'] = 'node/' . $node->nid . '/article';
  $values['alias'] = 'article/' . $title;

  $all_values = array($values);

  foreach ($all_values as $all) {
    $query = db_merge('url_alias')
      ->fields(array('source' => $all['source'], 'alias' => $all['alias'], 'language' => LANGUAGE_NONE))
      ->key(array('source' => $all['source']))
      ->execute();
  }
}



Where,
 pathauto_cleanstring is obey the pathatuo module's rules which is mentioned at admin/config/search/path/settings. To know more details of pathauto_cleanstring, please visit http://www.drupalcontrib.org/api/drupal/contributions!pathauto!pathauto.inc/function/pathauto_cleanstring/7

After added the above code into your custome module(clear cache), you will create a article. You just test your url at admin/config/search/path in the pathauto's list. It looks like below image:




Now you could access the article by both node-title as well as article/node-title.





Delete URL alias programmatically when delete a node using pathauto module in drupal 7:
     We've inserted 2 URL alias for a node. So we need to delete those from "url_alias" table when delete a node. We can trigger it using hook_node_delete() in drupal 7. Consider the below code:



/**
 * Implements hook_node_delete()
 */
function arep_node_delete($node) {
  if ($node->type == 'article') {
    //delete node alias for ceu and non-ceu course
    module_load_include('inc', 'pathauto');
    $source[0] = 'node/' . $node->nid . '/article';

    foreach ($source as $s) {
      $path = path_load(
        array('source' => $s)
      );
      path_delete($path['pid']);
    }

  }
}

Where,
  path_load returns the details of a URL alias like source, alias, path id  & language. To know more details of path_load(), please visit https://api.drupal.org/api/drupal/includes!path.inc/function/path_load/7.x.

After added the above code into your customer module(clear cache), you will delete a node and check your URL alias at admin/config/search/path. Now tt should not be displayed here.

Now I've hope you know how to set multiple URL alias for a content type.

Related articles:
Remove speical characters from URL alias using pathauto module in Drupal 7
Add new menu item into already created menu in Drupal 7
Add class into menu item in Drupal 7
Create menu tab programmatically in Drupal 7
Add custom fields to search api index in Drupal 7
Clear views cache when insert, update and delete a node in Drupal 7
Create a page without header and footer in Drupal 7
Login using both email and username in Drupal 7
Catégories: Elsewhere

Zivtech: You Don't Know Git!

mar, 02/08/2016 - 15:57
I’m going to put it out there. This blog is not for senior developers or git gurus; I know you know git. This post is for the noobs, the career-changers like me. If I could go back in time, after I had graduated from my three month web development bootcamp, I would tell myself, “You don’t know git!”

I can hear myself saying, “But I know the workflow. I know to pull from master before starting a new branch. I know to avoid merge conflicts. I git add -A. I know what’s up.”

No. No. No. Fix Your Workflow
If there’s one command you want to know, it’s this: <code> git add -p </code> This command changed my entire workflow and was tremendously helpful. In bootcamp, you learn the basics of git and move on. You generally learn: <code>git add -A</code> or <code>git add .</code> This stages all the changes that you’ve made to the repository or all the changes you’ve made from your current directory. This worked during bootcamp because the changes were small, and I was often just committing to my own repository. Once I switched over to Drupal and started working with Features, I realized that after I would make updates, not all of the files that were showing up in code were things I had changed. How could that be?! Work with Your Team
I was working on a project with other developers who were also working on the same feature. I had to learn -p so that I could be a responsible member of the team and only commit what I had changed. That’s why it’s so important to use this command: <code>git add -p</code> If you’re ever unsure about a command in git, just type this command: <code>git add --help</code> The git manual will then show you all the options you can use, like this: -p, --patch Interactively choose hunks of patch between the index and the work tree and add them to the index. This gives the user a chance to review the difference before adding modified contents to the index.
Essentially, it allows you to review each file to determine what changed, and if you want to stage it or not.
In the example above, I made changes to my .gitignore file. I deleted the line in red, and added the line in green. Then it asks you what you want to do with those changes. If you type in ‘?’ and push enter, it will explain what your options are.

Not only does it help by preventing you from staging code that isn’t yours, it’s also helpful as a new developer to see what changed. In Drupal, you can think that you’re making a small change in the UI, but then see a ton of altered files. Using -p has helped me figure out how Drupal works, and I’m a lot more confident about what I’m staging now.

Now go out there and <code>git add -p</code> all of your changes and be the granular committer I know you can be!
Catégories: Elsewhere

OSTraining: How to Use Entity Print in Drupal 8

mar, 02/08/2016 - 14:04

An OSTraining member asked us how to configure the Entity Print module with Drupal 8.

This module allows you to make a PDF version of your nodes

I would recommend that you install Entity Print using Drush, because you will need to install also need to install a composer package. This package contains the library to create PDFs.

Catégories: Elsewhere

ComputerMinds.co.uk: Drupal 8 Namespaces - class aliasing

mar, 02/08/2016 - 14:00

Class Aliasing is the simple, but very useful solution to the problem of needing to use two classes (from different namespaces) with the same name.

Catégories: Elsewhere

Talha Paracha: GSoC'16 – Pubkey Encrypt – Week 10 Report

mar, 02/08/2016 - 02:00

I started this week’s work by finishing the integration of cookies into my module. To give you some context, Pubkey Encrypt now uses cookies for temporarily storing the Private key for any user upon login. Previously, we were using sessions for this purpose, but we’ve just shifted to this new approach because Pubkey Encrypt aims to protect a website’s Data-at-Rest in compromised servers. Since sessions get stored in the servers too, the module cannot rely on sessions for keeping any secret information.

Catégories: Elsewhere

Jeff Geerling's Blog: Hide the page title depending on a checkbox field in a particular content type

mar, 02/08/2016 - 00:55

In Drupal 8, many small things have changed, but my willingness to quickly hack something out in a few lines of code/config instead of installing a relatively large module to do the same thing hasn't :-)

I needed to add a checkbox to control whether the page title should be visible in the rendered page for a certain content type on a Drupal 8 site, and there are a few different ways you can do this (please suggest alternatives—especially if they're more elegant!), but I chose to do the following:

  1. Add a 'Display Title' boolean field (checkbox, using the field label as the title, and setting off to 0 and on to 1 in the field settings) to the content type (page in this example).

Catégories: Elsewhere

myDropWizard.com: A Survey! Is Drupal Hard?

mar, 02/08/2016 - 00:04

I attended Drupal Camp WI at the University of Wisconsin-Madison this weekend.

There was a fantastic presentation called "Why Is Drupal So Hard?" by Joe Shindelar at Drupalize.me

It got me thinking about myDropWizard, our clients, and what path people are taking at this current crossroad of Drupal 6 -> Drupal 7 -> Drupal 8 versus going a different path. Sometimes when you are too close to a question, you shouldn't be the one answering it. So, I'd like to ask "you," the world!

I'll share the results in a future blog post, and I'll share my thinking about what the results mean.

If you have any criticisms of the survey, please share those with me! I think this is just the first of a few surveys that we can do.

I hope this is fun, and I know it's not "scientific". However, I am hoping that it continues the discussion within the Drupal Community in regards to what we should do?

Without further ado: Here is the survey!

Catégories: Elsewhere

Drupal Association News: Changes for the Drupal Association Engineering Team

lun, 01/08/2016 - 21:06

This article is the next part in our series about recent changes at the Drupal Association. I'll be focusing on what these changes mean for the Engineering team and the impact that will have on the work we're doing for the Drupal Community.

Our mission is to "unite a global open source community to build and promote Drupal." There are two audiences implicit in that mission - the community of contributors that build Drupal, and the customers and end-users for whom Drupal is the solution they need.

In the run-up to the release of Drupal 8, our strongest imperative was to support the contribution journey on Drupal.org -- that is, to maintain, refine, and enhance the developer tools that allowed our community to ship Drupal 8.

Following the release of Drupal 8, our imperative now is to support the adoption journey on Drupal.org -- and specifically to support those evaluators with ambitious digital needs, who will benefit from the kind of solution that Drupal can provide.

This change in our imperative also comes in a time when our engineering team is shrinking from a team of nine to a team of five. These positions handle all the technical needs of Drupal.org and the subsites: from answering support tickets from the community; to infrastructure maintenance; to managing services like updates, composer, and DrupalCI; to architecture and engineering to create solutions for the evolving needs of the project.

Our Roadmap

For the next 12 months the engineering team's focus will be:

1. Supporting the sustainability and fiscal health of the Association.

This means focusing on work that promotes both the mission and the revenue model of The Association. This might be anything from finding ways to promote DrupalCon attendance on Drupal.org, to creating placements for partners who may be interested in sponsoring specific parts of the tooling or infrastructure that we maintain.

2. Transforming the adoption journey for Drupal evaluators.

Shifting our focus to the Drupal evaluators means transforming the home page of Drupal.org. We need  to reach end-users and customers who are looking for solutions that Drupal is uniquely suited to solve. Building this adoption journey means highlighting Drupal success stories. These stories might be about higher education, government, non-profit, or other markets - but in every case these will be real stories of concrete needs solved with concrete solutions built in Drupal.

3. Sustaining the tools the community needs to continue porting modules and making point releases of Drupal 8.

We will continue to sustain the tooling and infrastructure that the community uses every day to build Drupal. From taking Drupal.org's Composer repositories from from beta to stable, to fixing bugs in DrupalCI, to maintaining the issue queues—keeping the basic machinery of contribution of Drupal.org running smoothly is still our mandate. However, we won't be introducing new features or transformative changes [quite yet].

4. Studying our developer tools and planning the work we want to do to continue to improve the contribution journey, when we have the resources to do so again.

While we're not going to be transforming the developer tools on Drupal.org in the near term, we are going to be studying those tools. Under the direction of the Drupal Association Board, we have formed a Technical Advisory Committee consisting of a few staff and community members to plan a tooling study, with 2 goals: 1) To improve the developer experience on Drupal.org. 2) Explore options for monetization, perhaps by offering private repositories, testbots, or similar.

And beyond these 4 cornerstones of our roadmap, we will continue to support Drupal.org community initiatives. Great work has been done and is still being done with the help of the community to advance DrupalCI, Composer, Documentation, the Project Applications process, and more. We want to continue to support the community in helping us to make Drupal.org a better home.

By the wayside… for now

There is some work that we no longer have the capacity to do. While we will look for opportunities for incremental improvements in these areas if and when our other work coincides, we will not make this work our priority:

  • New developer tools
    • While we are conducting the study alluded to above, we do not have short-term plans to create new developer tools.
  • Ongoing implementation of the content strategy
    • Support section
    • News & Events section
    • Governance section
    • etc.
  • Feature improvements for subsites like events.drupal.org and jobs.drupal.org
  • Staff contributions to the community-lead D8 initiatives (such as Blocks and Layouts and Workbench and Deploy)

That said, no part of Drupal.org exists in a vaccuum, so as we make the changes that are prioritized you will see some ripple effects throughout the rest of the site. Two recent changes come to mind as examples. Firstly, the change in follow button styles. This small change in iconography was part of deploying the last of our work on the new documentation tools for Drupal.org - but it was important for us to apply that change globally, providing a consistent metaphor for following content throughout the site. Secondly, the recent change to move user links to a user menu in the header of Drupal.org. This change was done to support upcoming editorial changes to the front page of Drupal.org, but with very little extra effort we've applied that improvement throughout the rest of the sub-sites.

How you can help As an individual or small group of volunteers:

You can help us make incremental improvements. If you see small changes on Drupal.org that would make a big impact, you can request a Drupal.org development site, and submit a patch. If you're looking for a way to make a contribution, take a look at issues that have been tagged for Drupal.org. You can also reach out to me through my Drupal.org contact form, on IRC as hestenet, or on the Drupal Slack as hestenet.

If you would like to propose a larger initiative to make a change on Drupal.org, you can submit a Community Initiative proposal. Past and present community initiatives have included collaboration with DA staff on work such as: developing DrupalCI, adding two-factor authentication, supporting Composer on Drupal.org, creating a security advisory content type on Drupal.org, and revamping the Project Applications process.

As an organization that uses Drupal:

You can join the Drupal Association as an organization member or a supporting partner. Your partnership directly supports the tooling and infrastructure that helps the community build Drupal, and supports our effort to reach out to customers and end-users who have yet to discover Drupal.

If you would like to make an even greater impact, you can directly sponsor the Drupal.org roadmap. In fact, our work on Drupal.org's Composer support was sponsored by Appnovation in partnership with a world-leading life sciences company. By choosing to fund a particular item on our roadmap you'll be credited as a sponsoring organization, and we'll post a case study explaining how your sponsorship enabled us to better support the community. If your organization is interested in roadmap sponsorship, please don't hesitate to reach out.

About Tim

Tim Lehnen (hestenet) joined the Drupal Association in November of 2014 as Project Manager. He now leads the engineering team and helps coordinate community initiatives on Drupal.org. You'll see Tim in the issue queues, on IRC, or at DrupalCon.

When he's not heads down in a scrum board, Tim can be found writing code for Arduino or novels for young adults. He lives in Portland, OR, USA.

Catégories: Elsewhere

Cryptic.Zone: Slack Chat: Chatting with Visitors on a Drupal Site

lun, 01/08/2016 - 17:34

Since we switched to Slack as the primary means of communication at work, Slack has grown to be my favorite chat application. Not only does it have a very pleasant interface, but it also offers great ways to integrate it with your application. As a matter of fact, their API is among the least restrictive ones in my experience. As a result of the joy of working the Slack API, Slack chat module was born to serve as a proof of concept for embedded Drupal-to-Slack chat functionality.

Catégories: Elsewhere

lakshminp.com: Drinking the Drupal-Composer Kool-Aid?

lun, 01/08/2016 - 17:31

Do you want to manage modules and dependencies the PHP way instead of the "Drupal" way? Don't know how to use composer with Drupal? Are you planning to ditch drush make approach and adopt a composer based workflow?

If you answered yes to any of the above questions, then you should read this post.

Compose what?

Composer is PHP equivalent of Python's pip, Ruby's bundler and Node's npm. It helps manage projects and dependencies for a PHP project.

Why Composer?

The average PHP developer wrote 3.5 frameworks in their lifetime. This was before the era of package management. Then came along PEAR. PEAR did the job, but had some flaws. To point out one, for instance, PEAR installs packages globally instead of installing them on a per-project basis. So, if you install Acme libary v1.2, you had to use Acme v1.2 throughout all of your projects. Thankfully, Composer has succeeded PEAR as the de facto package manager for PHP.

The Drupal context

Modules and themes in Drupal are managed by drush, specifically drush make. Both composer and drush make do the same thing, i.e. download and install specific versions of Drupal modules and themes. Composer has an extra ingredient called autoload. This automagically figures out where your dependency files are there and includes them in your code as needed. Drupal 8 core adopted composer as the dependency manager. So if composer is great, why isn't everybody using it? To bridge this gap, Drupal 8 brought in a module called composer manager. This module helps manage composer dependencies of contrib modules. This might otherwise be done by editing Drupal 8 core's root composer.json and adding our module's composer dependencies there(which amounts to hacking the core).

So, if module acme depends on package foo, it will have a composer.json in the module's root directory with foo added as a dependency. Composer manager will add foo to Drupal's vendor directory. Starting with Drupal 8.1, we no longer need Composer manager to manage module dependencies. It can be done by composer alone. Let's take a look at how we pull this off.

Make sure you have Drupal 8.1.x installed and setup. Let's download the address module using composer.

/v/w/h/drupal-8.1.1↪ composer require drupal/address "8.1.*@dev Warning: This development build of composer is over 60 days old. It is recommended to update it by running "/usr/local/bin/composer self-update" to get the latest version. ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an installable set of packages. Problem 1 - The requested package drupal/address could not be found in any version, there may be a typo in the package name. Potential causes: - A typo in the package name - The package is not available in a stable-enough version according to your minimum-stability setting see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details. Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems. Installation failed, reverting ./composer.json to its original content.

Add packagist as a repository in your composer.json for the lookup to succeed.

NOTE this is a one time thing and you needn't do it for every module.

/v/w/h/drupal-8.1.1↪ composer config repositories.drupal composer https://packagist.drupal-composer.org/

Your `composer.json` will have an entry for `repositories.drupal`.

"repositories": { "drupal": { "type": "composer", "url": "https://packagist.drupal-composer.org/" } }

Now, another shot at it.

/v/w/h/drupal-8.1.1↪ composer require drupal/address "8.1.*@dev" ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Nothing to install or update Generating autoload files > Drupal\Core\Composer\Composer::preAutoloadDump > Drupal\Core\Composer\Composer::ensureHtaccess

NOTE that this might take a bit of time if you have a lot of composer dependencies cached.

Enable address module, either via the UI or using drush.

/v/w/h/drupal-8.1.1↪ drush en address -y The following extensions will be enabled: address Do you really want to continue? (y/n): y address was enabled successfully. [ok] address defines the following permissions: administer address formats, administer zones

All set to rock!

So, what happened behind the scenes?

Address module had a composer.json which reads like this:

{ "name": "drupal/address", "type": "drupal-module", "description": "Provides functionality for storing, validating and displaying international postal addresses.", "homepage": "http://drupal.org/project/address", "license": "GPL-2.0+", "require": { "commerceguys/intl": "dev-master", "commerceguys/addressing": "dev-master", "commerceguys/zone": "dev-master" }, "minimum-stability": "dev" }

The above commerceguys/* dependencies got installed in the main vendor/ directory by composer.

What are the shortcomings of using composer alone to manage modules? For one, it would be too developer focused, in the sense that site builders(common audience for Drupal) won't be able to use it because of the complexity involved. When they have to download a module and enable it(a very common operation in Drupal), they can't do it entirely through the UI and have to run composer commands in the backend.

How to update modules using composer? We shall talk about that in the next post.

Drupal, Drupal 8, Drupal Planet
Catégories: Elsewhere

TimOnWeb.com: Creating content blocks programmatically in Drupal 8

lun, 01/08/2016 - 15:06

Let's picture this: you've created a custom content block type (let's say, Ad block) in your shiny new Drupal 8 installation and you want to automaticaly create a fresh new block of that type each time you create a taxonomy term (Ad group), so that every ad group has a ...

Read now

Catégories: Elsewhere

Cocomore: Configuration of Sitecore Analytics Dashboards part 1: It’s not that easy after all

lun, 01/08/2016 - 00:00

Who doesn’t love them, the colorful graphics and charts that deliver a mass of information to understand our users better. Analytical tools help to continually improve websites based on complex statistical data. One of those analytical tools is the Sitecore Analytics Dashboard. We will talk about our experience with it here.

Catégories: Elsewhere

Out & About On The Third Rock: A product owner’s guide to writing acceptance criteria for user stories

sam, 30/07/2016 - 23:41
‘I want to create a practical guide for product owners to facilitate them in writing acceptance criteria for user stories so that their output is of value to the scrum team’   You’ll find pages after pages describing what an acceptance criteria is and how to write a good one, what it should include or […]
Catégories: Elsewhere

DrupalEasy: DrupalEasy Podcast 183 - Higher Ed - Shawn DeArmond

sam, 30/07/2016 - 18:00

Direct .mp3 file download.

(Shawn DeArmond) is a web architect at UC Davis in Sacramento, California. Ryan and Anna interview Shawn about the Drupal Higher Ed summits at DrupalCon and BADCamp, and discuss news from the past week, including Dreamweaver, Drupal 7.50, the "boy who cried wolf" nature of a recent security advisory, picks of the week, and five questions.

Interview DrupalEasy News Three Stories Sponsors Picks of the Week Upcoming Events Follow us on Twitter Five Questions (answers only)
  1. Brew Beer
  2. 1Blocker on iOS
  3. Skydiving
  4. Australian Fruit Bat
  5. Ben Shell
Intro Music

Too Sexy for my Code by Larry Garfield (crell) from DrupalCon NOLA PreNote.

Subscribe

Subscribe to our podcast on iTunes, Google Play or Miro. Listen to our podcast on Stitcher.

If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.

Catégories: Elsewhere

ActiveLAMP: Adding pURL Multidomain XMLSitemap

sam, 30/07/2016 - 04:00

On a recent project, we had to create multiple sitemaps for each of the domains that we have setup on the site. We came across some problems that we had to resolve because of the nature of our pURL setup.

Read more...
Catégories: Elsewhere

Drupal core announcements: Drupal 8 core release window on Wednesday, August 03, 2016

sam, 30/07/2016 - 02:41
Start:  2016-08-02 12:00 - 2016-08-04 12:00 UTC Organizers:  xjm catch Event type:  User group meeting

The monthly core patch (bug fix) release window is this Wednesday, August 03. Drupal 8.1.8 will be released with dozens of fixes for Drupal 8. Drupal 8.2.0-beta1 will also be released sometime during the week to begin preparation for the upcoming minor release in October. There will be no Drupal 7 bugfix release this month.

To ensure a reliable release window for the patch and beta releases, there will be a Drupal 8.1.x and 8.2.x commit freeze from 12:00 UTC Tuesday to 12:00 UTC Thursday. (The beta release window may extend later if needed.) Now is a good time to update your development/staging servers to the latest 8.1.x-dev code and help us catch any regressions in advance. If you do find any regressions, please report them in the issue queue. Thanks!

To see all of the latest changes that will be included in the patch release, see the 8.1.x commit log.

Other upcoming core release windows after this week include:

  • Wednesday, August 17 (security release window)
  • Wednesday, September 07 (patch release window)
  • Wednesday, October 5 (scheduled minor release)

Drupal 6 is end-of-life and will not receive further releases.

For more information on Drupal core release windows, see the documentation on release timing and security releases, as well as the Drupal core release cycle overview.

Catégories: Elsewhere

Pages