Webform Scheduler is a cool module that allows you to schedule the opening and closing of a given webform. It works similarly to the Scheduler module except it does not publish/unpublish the node but simply opens/closes the webform on the node.
I have come across this module only recently due to a request that was made for webforms to be automatically closed at a specified date. Needless to say, this module worked like a charm for me so I decided to show you.
To get it going real quick, install like usual. With Drush if you go like drush dl webform_scheduler and drush en webform_scheduler -y, you are good to go. Make sure you have the Webform module installed though as it depends on it (drush dl webform && drush en webform -y will take care of that).
To use the webform scheduling functionality, edit the form settings of the webform you want (found at node/[node-id]/webform/configure) and below the Submission Access group you’ll find a new one called Scheduler:
There you can specify at what date the form should be open and at what date it should be closed. And you can rest assured that if you decide to manually close the form, this will take precedence over any scheduling. And you can also choose what happens when the form does get closed due to the scheduling: deny access to the whole page or just the webform itself or even show the webform but hide its components. Now this is some nice features to have.
And you have to admit the module is pretty powerful if you are dealing with a big website that needs to run many forms at the same time with various degree of overlap between their open times.
There is one thing however I needed and the module does not provide. I dread the default Webform drupal_set_message()-like message that appears at the top of the page when you are on a closed webform node. What I needed was a similar message appearing in the same place where the actual form was when it was open. So with some custom code I got rid of the top message (thaank god) and altered the node view to display my message instead of the webform when the latter is closed. Can you think of a better alternative? Drop a line in the comments if you can. Cheers!
Hope this helps.In Cool Modules | Drupal
Drupal 8 Alpha 6 is out and it has a migrate module in there! It even has a few complete migrations: variables to the configuration files owned by system module. Since the last report the configuration of process has changed significantly, this is now documented in the handbook. We have two patches in the core queue, one potpourri of small fixes and one to split migrate into migrate and migrate_drupal, the latter holding the Drupal 6->Drupal 8 and Drupal 7->Drupal 8 migration. I have a third almost ready, this will be our first config entity migration, namely filter formats. This is actually working but the test is currently not doing much and the documentation is lacking -- once these easy problems are fixed, I will submit this as well. There's quite a lot of documentation to be written because this patch will introduce most generic process plugins we planned to write. A lot of code has been written for a fourth, this will be all the variables to configuration files. There's rapid progress, Mike Ryan now participates on a daily basis which means a lot of domain knowledge has been added to the team. marvil07 is working on porting the CCK fields code from migrate_d2d -- yes, the battle plan is that you will be able to migrate CCK fielded nodes to Drupal 8 straight. bdone and Mike is working on expanding the test coverage on two big classes which were straight ported from Drupal 7. YesCT is fixing our doxygen (I worked on this as well because the terminology was very confusing, hopefully now it's less so). My next task is to go over the existing hook_update_6xxx functions and see whether there's special logic that won't be covered by simple entity-to-entity migrations and create issues for them. fastangel have written the bulk of the fourth patch, I fully expect he will pick a lot of these issues, with the rest of the team piling on them once their work is done. With a little luck and perseverance the Drupal 6 -> Drupal 8 migration will be done by the Drupal birthday (January 15).
In the longer term, we will need to do Drupal 7 to Drupal 8 and I will need extra helping hands with multilingual issues. Ryan Weal already voluntereed to help, but I am sure we can use a few more so if you know i18n+migrate both, please don't hesitate to contact me.
Integrating XDebug into your IDE opens up a world of powerful debugging fu, but there's more to XDebug than that. There is an API you can leverage for alternate ways of peering into what's going on during that page load.
In this post I'll demonstrate some basic function tracing and related configurations.
I teach Drupal to a lot of people. One thing I have learned, is that whether I'm teaching people who are so new that they're still learning how to pronounce "Drupal" or I'm teaching current users the intricacies of the Migrate module, there's one common thread: without a solid understanding of Drupal's "Big Five", students will have trouble gaining the confidence that all Drupal developers, themers, site-builders, and anyone else who interacts with Drupal on a daily basis need.
I hate it when waves of closed source fashion hit the open source communities: Purchase such and such an IDE, “it's awesome”. Apart from paying a lot, hey, it's closed source! Forget that! This article is the first in a series that will show you how to get set up with a top of the line, free as in beer and truly open source Drupal IDE (and Project Management system!), complying with the following objectives:
Top of the line free software development IDE with multiple projects and a multitude of plugins, based on Eclipse Kepler.
No vendor lock in.
Support for Web development in general (HTML, CSS, JS, XML, etc.), that is syntax highlighting, autocomplete suggestions with pop-up documentation, mouse-over documentation.
Support for PHP development also.
Support for back-end languages (Java, etc.)
Support for Remote project development, including code highlighting, etc.
Support for Drupal development
Drupal coding standards,
Drupal files immediately editable as PHP code,
Spaces instead of tabs
The right encoding (Unix) so they can be committed to Drupal repositories.