Proposal: One anti-spam module to rule them all

As I prepared to turn on comments and forums, I researched the anti-spam techniques out there for Drupal. There are a lot of great tools, but then it occurred to me: There is a lot of redundancy, and no coordination. See the wonderful list of anti-spam modules.

Would it be a good idea to have a module to coordinate all of these modules, and bind them?

It seems that all of these modules do some or all of the same basic five things:

  • Detect spammy behavior (especially bots).
  • Block spammy behavior.
  • Cache information about potential sources of spam.
  • Report sources of spam to a central repository.
  • Clean up spammy accounts and content.

Now, they all do this in different ways, particularly the detection part.

However, it seems to me that there could be some sort of "Grand Central Bad Behavior Blocker" (GCBBB) module. It would coordinate all of the actions above amongst different modules. Individual modules would provide one or some of the above services, but wouldn't need to provide all of them.

Drupal 8 - In-place editing?

Hi, I was just wondering if there will be "build-in" in-place editing in Drupal 8?

If so, will it be in the core of Drupal or is it a distribution just like Spark actually?

If anyone have any infos on the subject, let me know! :)


Simon-Pierre Beliveau

Creating a simple Drupal module project

This is a tiny but interesting project. We need a Drupal module that integrates Acobot ( with Drupal.

Required features.

  1. Allow site owner to install Acobot chat box with the installation key, without copying/pasting the HTML code. (Similar to, detailed instructions included with admin UIs)
  2. Enable site owner to set the chat box visibility, with an UI same as block visibility settings.
  3. Transfer the email address of registered users to Acobot. See

The developer is expected to

  • Write the codes and full user documentation.
  • Test the modules thoroughly.
  • Create a project on, with full project pages.
  • And get the project published on


  • You may choose to join our affiliate program and receive 30% of payments from customers referred with the modules. You will maintain the project on a continuous basis. See
  • OR you can choose a one time payment. You will need to maintain the project (handling issues, fixing bugs, etc.) for 30 days after it's published. Give a quote if you prefer one time payment.

Installing the drupal source code downloaded from git

I downloaded Drupal 8.x source code from git. To test the code I tried to install it to my localhost. When I run the install page it works fine up to Installation profile. After installing all 40 modules it gives page not found error. To be specific the page "http://localhost/drupal/core/install.php?langcode=en&profile=standard&id...". When I reload it goes to "configure site" as expected. Adding all the details required on that page when I click the submit button It again gives a page not found error for the page "http://localhost/drupal/core/install.php?langcode=en&profile=standard". But when I reload the page it goes to "Finished" page. When I click the "visit your new site" url it directs to the log in page(But not logged on as the user I created in the installation). By entering username and password in the relevant text fields and clicking the log in button It again gives a page not available error for the page "http://localhost/drupal/node?destination=node". When I reload it goes again to log in page.

I tried to install this several times, but every time same thing happens. I downloaded Drupal 7.21 (not from the git) and is installed normally.

I'm using
OS - Windows 7 ultimate
Server - wampserver 2.2
Apache version - 2.2.22
PHP version - 5.3.13
MySQL version - 5.5.24

A Much Better Drupal

In this article I might be wrong at any of the parts as Drupal is huge and my knowledge might be not up to date and I might be wrong anyways. These are my thoughts currently that I want to share them with the Drupal Community...

I really think Drupal has a few issues. These are mainly related to previous generations of Drupal. Current Drupal versions come with pretty much relations to previous ones.

I started using Drupal like 2 years ago. Maybe earlier. I really loved its idea however before finding drupal I've started writing my own CMS. When I didn't even know about the expression 'CMS'. This thing doesn't mean much. It only means i really understand the basic reason why it was made.

My belief is that things can be much easier. Here I am about putting some idea together how Drupal can be (and hopefully will be) much better.

  1. No exceptions: Each and every node type info (publishing options, display settings) should be normal fields. With all the options a field gives: Widgets, Formatters, etc. On Entity Type Properties there are Title, Author, etc now. Great. We need all the rest I believe.

More Intuitive Manage Fields & Manage Display Interface for a Content Type

I think a few things can improve user experience and reduce learning curve. These are:


Subscribe with RSS Subscribe to RSS - Drupal 8.x