Releases for BOTCHA Spam Prevention

This branch is a proof of concept declared here: #1932290: Forwardport doctrine - a proposed solution for Drupal major version migration problem.

• #1880810: Flush all caches after upgrade to 7.x-3.x
• [NOISSUE] Split Admin test case to plenty
• [NOISSUE] Fix Simpletest-tests

• #1880882: Fatal error
• #1880812: 'Failed 4 of 5 recipes [1, 1, 1, 1] from "default" recipe book.'

#1833378: Honeypot2 recipe always blocks form submissions on Opera Disabled unstable _botcha_recipe4() (Honeypot2)

Stable release for 6.x

New major release of BOTCHA. You definitely should upgrade since it includes:

• Easy upgrade: You should just enable Module Object Oriented Programming API (which becomes a dependency) first - and then update code to new version. There are no database structure changes since 7.x-2.0 and only a few database content changes since 7.x-1.3. So it would be as easy to upgrade as just a few clicks.
• Selenium-tests for all major browsers (Firefox, Google Chrome, Opera, Internet Explorer plus possibility to extend): It means that JavaScripts-recipes work as expected - always, guaranteed. If you see something strange - you could just launch all Selenium-tests to see what's wrong and post an issue to Drupal.org. Brief Howto-instruction (both installation and usage of Selenium) is inside the Selenium-tests file.

• #1840702: Create a variable which lets (or not) to edit the list of forbidden forms and provide an UI for editing it
• #1840688: What does 'Delete' do?

Dev-branch for the second BOTCHA major release.

Hot-fix2 for critical issue: #1828710: Fatal error during update from 7.x-1.0 to 7.x-1.1
#1829698: Notice: Undefined variable: fail in BotchaRecipebook->handle()

This is the first stable release after the global refactoring completion (see #1804770: [META] Migrate to object-oriented architecture).
The main features are:

• OOP-style. The BOTCHA module is moved to OOP-architecture. It means that all "entities" that take part in BOTCHA functionality are turned into classes. That gives more flexibility to extend and freedom to modify.
• Like MVC-application. The module's internal structure has been changed completely. Now it looks like real MVC-application. It gives a chance to separate logic of the application and the layer of interoperability with Drupal platform - that means that the BOTCHA is going to become more version-independent. I hope in the future we would see a Drupal-version-independent BOTCHA module. It eases maintainership of the module.
• Fully test-covered. Tests covered almost every line of the code. Plus tests' structure has been unified - and now it is really simpler to maintain it. I hope you will enjoy.
• Helpful UI. Now UI lets you to turn on or off recipe applying per each form. It helps to avoid critical situation when one or more recipes doesn't work as you like: you should just turn them off and post an issue to Drupal.org - and your site would not be affected by any discomfort.

[#5308708] Added autocomplete=off to avoid false detects with client's autocomplete
[NOISSUE] Coder style fixes
[NOISSUE] Reworded "Form session reuse detected" message, added "Please try again..."
[NOISSUE] Backported secret key generation cleanup from 7.x-1.x-dev
[NOISSUE] Refactoring: Allow named recipe books other than 'default'; Use form_state to pass '#botcha' value
[NOISSUE] Remove Captcha integration text from help if Captcha module is not present
[NOISSUE] Remove hole in user_login_block protection when accessed via /admin/ path

#1180272: create triggers for blocking events Rules integration - botcha_form_approved, botcha_form_rejected, botcha_rules_action_regenerate_seed

[NOISSUE] Fixed url query string for non-clean URLs
#1024106: On installations in subfolder, user registration page submission returns with "page not found" Fixed problem with Drupal installations in subfolder

#991416: Module cannot be enabled (WSOD upon enabling) Fixed WSOD upon install

[ROADMAP] Addded some configuration settings