Newsfeeds

This module provides a cash payment method for Drupal Commerce.

This method is intended to be used from the administration terminal, and is not intended to use through the traditional user checkout.

Did you upload, to a remote server, a complete Drupal-based website, or update one with the latest Drupal core, and now the site is waving the white flag — that is, the White Screen of Death (WSoD)? It might be coughing up only a single error message, informing you that a critical Drupal function is missing. If so, here is one way to begin your troubleshooting efforts and possibly find an easy fix.

Whenever you are using FTP to upload Drupal files to a remote web server, or to download some to a local server, there is a chance it will result in a Drupal near-death experience — or at least a close approximation. Recently I was upgrading a remote client website to the latest Drupal security release. It worked perfectly on a local mirror of the site. But after the file transfer completed, the client's homepage was replaced by a white screen listing only an error message that a commonly-used core module function could not be found.

In such a situation, one's first thought — aside from finding a less stressful career — might be that a core or contrib module version is now out of sync with the rest of the site, or that the author of a contrib module is using an outdated function name, or that some contrib code is trying to access a function that simply does not exist. In my experience, the problem and solution are, frequently and thankfully, rather straightforward: During the file transfer, it is possible that the FTP client program inadvertently emptied a target file by freeing the space allocated to its old contents, but failed to write the new contents and close the file. Sadly, most if not all FTP programs do not verify that the contents were written to and saved in the file (which admittedly would slow FTP transfers considerably), or even that the file sizes on the source and target machines are identical. In other words, FTP can fail silently but continue transferring files as fast as it can, without any warnings or error messages.

Below is a simple PHP script that searches for and reports, in alphabetical order, any zero-byte files in the current directory and all its subdirectories, recursively. The code is offered as is, with no warranty, implied or otherwise. It is intended to be run in a web browser, but works fine on the command line, although in that case you may want to remove the break tag on line 13. Obviously it would make no sense to try to package this modest utility as a Drupal module, because as long as Drupal is choking with a fatal PHP function-loading error, then it is not bootstrapping and certainly would not see any contrib module code.

So if a Drupal site stops working immediately after an FTP operation, consider first looking for empty files created by one or more faulty file transfers.

<?php list_empty_files( '.' ); function list_empty_files( $dir_path ) { foreach ( scandir( $dir_path ) as $file_name ) { if ( ! in_array( $file_name, array( '.', '..' ) ) ) { $file_path = ( ( $dir_path == '.' ) ? null : "$dir_path/" ) . $file_name; if ( is_dir( $file_path ) ) { list_empty_files( $file_path ); } elseif ( filesize( $file_path ) == 0 ) { echo $file_path . "<br />\n"; } } } }

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

Overview

Provides admin page for updating status of orders in bulk using Drupal batch process. Order status, order comment, admin comment and send email notification can be set for all selected orders.

Requirements

• Drupal 6.x
• Ubercart 2.x

Installation

1. Copy the extracted uc_bulk_update_orders directory to your Drupal sites/all/modules directory.
2. Login as an administrator. Enable the module at the http://www.example.com/?q=admin/build/modules
3. This is optional, configure permission "bulk status update orders" at http://www.example.com/?q=admin/user/permissions
4. Bulk status update orders form can be found at http://www.example.com/?q=admin/store/orders/bulk_update

Experimental module.

Related to my fieldset summary problem: autocomplete fields do not trigger the change event in Javascript, for some reason. I wound up stealing part of a patch I found somewhere (I would link to it if I could find it in my browser history) in order to override the autocomplete prototype function and trigger a new autocompleteSelect event when the user chooses an item in an autocomplete field. Just drop this function into a Javascript file in your module or theme:

(function ($) { /** * Puts the currently highlighted suggestion into the autocomplete field. * Overridden from misc/autocomplete.js to add an event trigger on autocomplete */ Drupal.jsAC.prototype.select = function (node) { this.input.value = $(node).data('autocompleteValue'); // Custom: add an event trigger $(this.input).trigger('autocompleteSelect', [node]); }; })(jQuery);

Note that this goes inside the (function ($) {})(jQuery); block that appears in most Drupal Javascript files. If you're pasting into an existing file that already has them, you can omit the first and last line, and paste the function in between them.

Then you just bind to that event. Here's an example for the node author field on the node add/edit form:

$('input[name=name]', context).bind('autocompleteSelect', function() { // Value chosen in autocomplete field. // Do whatever you need to do. var chosen_value = $(this).val(); });

Please excuse the long title: it took me a while to figure this one out, so I want to make sure that other people can find this when they need it.

On my current project, I'm changing the node author field based on the value of a user reference field on the node type: when a content admin sets the node reference field, the node author field is changed to match that user reference field value. Since the author field is shown in a fieldset, I wanted the summary on that fieldset to update when this change was made. It took me a while to figure out how, but it's pretty simple:

// Update the field summary if vertical tabs are in use var tab = $('fieldset.node-form-author', context).data('verticalTab'); if (tab) { tab.updateSummary(); }

Topic: DrupalAcquiaSpark distribution

When we first announced the Spark authoring experience initiative for Drupal in May of last year, we chose Drupal 7 as our target in order to develop the features and get them in front of testers as quickly as possible. After DrupalCon Munich in August, the team shifted efforts towards Drupal 8 core instead, in order to more directly improve the experience of Drupal itself. Since then, we have successfully worked with the community to drive home a redesigned and mobile-friendly toolbar, support for draft revisions, in-place editing, numerous mobile improvements, and have WYSIWYG and unified in-place editing on the way.

This has kept the team pretty busy, however, and so the Drupal 7 version of Spark has not been receiving many updates in the meantime. Olivier Friesse (noisetteprod) of Radio France graciously offered to sponsor work to help things along. Thanks to this sponsorship, we were able to have Théodore Biadala (nod_) of Acquia's Professional Services team spend 3 weeks on getting the in-place editing feature production-ready for Drupal 7, including:

• Full backport of Drupal 8 code, including Create.js/VIE.js integration
• Integration with CKEditor module to provide WYSIWYG support for rich text areas, which resulted in numerous upstream improvements
• Removed requirement on jQuery 1.7 so that Edit module can work on stock Drupal 7 installations without jquery_update module
• Removed requirement on PHP 5.3 so Edit module can also work in PHP 5.2 environments
• Basic support for Views/Panels in-place editing
• Numerous bug fixes to help further stabilize the code base

Working towards a stable release for Drupal 7 naturally identified bugs with the Drupal 8 implementation of inline editing, which are being tracked in this issue: https://drupal.org/node/1894454.

In short, the needs of Radio France have brought tremendous value for the entire community, in both Drupal 7 and Drupal 8. If you'd like to try out the work that we've done, download the 7.x-1.0-alpha7 release of Spark or Edit 7.x-1.0-alpha6!

Thanks once again, Olivier and Radio France, for your support! If other companies would like to sponsor further work on Spark, please let me know.

When we first announced the Spark authoring experience initiative for Drupal in May of last year, we chose Drupal 7 as our target in order to develop the features and get them in front of testers as quickly as possible. After DrupalCon Munich in August, the team shifted efforts towards Drupal 8 core instead, in order to more directly improve the experience of Drupal itself. Since then, we have successfully worked with the community to drive home a redesigned and mobile-friendly toolbar, support for draft revisions, in-place editing, numerous mobile improvements, and have WYSIWYG and unified in-place editing on the way.

This has kept the team pretty busy, however, and so the Drupal 7 version of Spark has not been receiving many updates in the meantime. Olivier Friesse (noisetteprod) of Radio France graciously offered to sponsor work to help things along. Thanks to this sponsorship, we were able to have Théodore Biadala (nod_) of Acquia's Professional Services team spend 3 weeks on getting the in-place editing feature production-ready for Drupal 7, including:

• Full backport of Drupal 8 code, including Create.js/VIE.js integration
• Integration with CKEditor module to provide WYSIWYG support for rich text areas, which resulted in numerous upstream improvements
• Removed requirement on jQuery 1.7 so that Edit module can work on stock Drupal 7 installations without jquery_update module
• Removed requirement on PHP 5.3 so Edit module can also work in PHP 5.2 environments
• Basic support for Views/Panels in-place editing
• Numerous bug fixes to help further stabilize the code base

Working towards a stable release for Drupal 7 naturally identified bugs with the Drupal 8 implementation of inline editing, which are being tracked in this issue: https://drupal.org/node/1894454.

In short, the needs of Radio France have brought tremendous value for the entire community, in both Drupal 7 and Drupal 8. If you'd like to try out the work that we've done, download the 7.x-1.0-alpha7 release of Spark or Edit 7.x-1.0-alpha6!

Thanks once again, Olivier and Radio France, for your support! If other companies would like to sponsor further work on Spark, please let me know.

 

Personal blog tags: Drupal Global Training Days

For people who don't do website and web application development regularly it can become easy to get lost in the process. For example, they may want a design for a page with look and feel before they even know what content will be on that page. To help product owners, content owners, and those involved in development who aren't familiar the ins and outs I've put together a diagram and process to help walk them through what's happening and what's needed.

This process is meant to be a simplification bordering on over simplification. Let me break down each of these parts.

Continue Reading »

In response to Mark's post, Converting Views List Into Responsive Stacked Columns, we've teamed up to create a module for just this sort of thing. Views Responsive Grid is a views display format plugin designed to give you the proper HTML structure for creating CSS grids. Although still a sandbox project, we're working to get it through the application queue quickly.... Read more

Working with Lightbox2 and Colorbox

In this series, Lightboxes and Drupal 7, Kyle Hofmeyer walks you through working with two popular lightbox modules in Drupal 7: Lightbox2 and Colorbox. The first video in the series is free, and explains what a lightbox is, and some things to consider when selecting which module to use.

For contributing to the Drupal community by developing your own module or theme you first have to contribute "a useful and working module or theme as a sandbox project, and go through a one-time approval process to get permission to promote it (and future projects) to a full project".

Weiterlesen

Tuesday, 29th January 2013drop.coop podcast episode 1 - Drupal Drop In Sprint London Saturday 26th January 2013

drop coop podcast episode 1 - Drupal Drop In Sprint London Saturday 26th January 2013 from Steve Purkiss on Vimeo.

Audio & Video tracks  also available on Archive.org

drop.coop podcast episode 1 - Drupal Drop In Sprint London

 

1. Robert Castelo
   • History of Drupal London group
   • Drupal Drop In Sprints
   • Drupal maturing as a product
   • Global Sprint Weekend 9/10 March inc. London & Brighton
   • Drupal for NGOs
   • Core Office Hours
   • DrupalCon Prague
2. Stefan van Hooft
   • Drupal Somerset
3. Pedro Cambra
   • Commerce Guys
   • Drupal Association
   • DevDays Dublin in June
   • CxO Barcelona in March
   • FrontEnd United in London
4. Steve Parks
   • Wunderkraut & Wunderroot
   • Drupal Radar
   • High Profile UK Sites this year!
5. Leon Tong
   • DrupalCamp London in March - a marriage made in…
   • drop.coop - Europe vs. U.S. ways of doing business

tags: Drupal PlanetPlanet Drupalcooperativesprintlondoninterviewsdrupalcondrupalcamp

The Shield module is a quick and simple solution for locking down websites with an Apache authentication username and password. It requires no changes to the .htaccess file (.htaccess modification is required if running on CGI or FastCGI) or configuration to an Apache vhost. Just install the module and configure it from Drupal's administration section. This module is very useful for locking down development and staging versions of a website.

In this short video, we'll cover the following:

• How to configure Shield
• Demonstration on how to use the module

Episode Number:  96

Spam is always something you need to consider when developing a Drupal website. One tool that makes spam detection and prevention extremely easy is the Drupal 7 Mollom module. This module uses the Mollom service to give your Drupal website capabilities to add captchas to forms, or even analyze text for content that looks like Spam. The service has a completely free version so you can easily get started preventing Spam on your Drupal 7 website.

In this episode you will learn:

DDoD Video: 

read more

About the Tarot-based Fortune's Fool RPG.