Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
contact.module
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
6 Sep 2009 at 22:37 UTC
Updated:
17 Nov 2010 at 05:48 UTC
Jump to comment: Most recent file
Comments
Comment #1
dave reidComment #2
dave reidRevised patch with a period at the end of the contact form checkbox. Also included before & after screenshots along with a screenshot of the flood_control interface.
Comment #3
dave reidMissed one variable name change. Also included a screenshot of the contact page when flood control is limited and these variables are set:
Comment #5
dave reidArg...tests won't run on my machine because of the freaking cache_update table errors. Maybe this one will pass?
Comment #6
dave reidComment #8
dave reidRevised patch now that my testing works again and this one should pass the bot. Note again I'm fully willing to support these contact flood limit/window variables in Flood control module.
Comment #9
dave reidRevised patch with proper variable uninstalls.
Comment #10
dave reidSo summary review:
1: The hourly threshold, has been changed to a hidden variable, just like the login flood limit/window. I've created a new Drupal 7 module to expose an admin interface for the flood control variables at http://drupal.org/project/flood_control.
2: This variable is renamed from contact_hourly_threshold to contact_threshold_limit for consistancy with the login flood variable names. Also added another variable contact_threshold_window (default 1 hour) so we can control the amount of time that people can send e-mails.
3: The enable contact form by default for users moved to admin/config/people/accounts under a new "Contact form" fieldset.
4: Removed
variable_del('contact_form_information');from contact_uninstall() because the variable is no longer used and it is deleted in system_update_7021().Screenshots for the new pages and the Flood control module are in #2.
Comment #11
dave reidFixed 'System' in the update docs and changed it to 'Contact'.
Comment #12
dries commentedI'm comfortable with this patch, but only when we bump the mail threshold from 3 to 5 or something. I had to bump the 3 on a number of my sites, and I don't feel like having to install a separate module for it. Sounds like a deal?
(Bojhan or someone else had a similar patch along these lines elsewhere. Might be useful to dig that up.)
Comment #13
yoroy commentedDeal!
#564576: D7UX IA: Roll back contact module settings page tab
#556192: Remove the UI for 'hourly treshold', replace with a sensible default
#556174: Move 'enable for new users' under Users
Comment #14
dave reidRevised patch with default flood limits set to five messages in one hour.
Comment #15
dries commentedCommitted to CVS HEAD. Thanks!
Comment #16
dave reidAwesome. FYI I updated the Flood control module to account for both these new variables and the new default limit of 5. I should make a note of this in the upgrade docs.
Comment #17
shawn dearmond commentedSo, gone with the admin/structure/contact/settings page is the ability to configure the text that appears above the contact form. Is that somewhere else now? It looks like it's been removed entirely from contact_site_form().
If that functionality is gone, the text on admin/structure/contact directing people there should be removed.
Here's what it says now:
Comment #18
shawn dearmond commentedSorry, meant to attach a patch. This addresses my comment #17, if the contact form text is in fact gone.
Comment #19
dave reidThere is an existing issue to cleanup the contact_help text, because there is a lot of outdated text in there. Contact info was moved to a block-only approach because of proper input formats, etc. Users upgrading should automatically get a new block called 'Contact page help' in system_update_7021().
Comment #20
dave reidPlease followup in #599124: Cleanup contact_help()
Comment #21
shawn dearmond commentedMakes sense. Thanks for the clarification.
Comment #22
dave reidI can't find where exactly this should be documented, so I'm marking this as fixed.
Comment #24
geerlingguy commentedJust FYI, it took me a bit of digging to find this bit of information - it would be nice if it were better documented in the upgrade guide... I couldn't find anything in there. I think I may just do it myself :)
I added a note here: http://drupal.org/node/778208#comment-3719396