While trying to integrate Secure Pages' new form protection with an older version of the domain module (7.x-3.4), it became apparent that the form alter for the module assumes a relative url for the form action and chokes on anything else. It became such a mess that I've created an alternative that simply allows the user to toggle whether or not SecurePpages ought to be applied to forms via a new set of radio buttons on the admin menu. In my case, just turning it off allowed me to get the other benefits of the latest version without having to seriously rework the website I've been working on. I've uploaded the patch.
Comment | File | Size | Author |
---|---|---|---|
#3 | securepages-toggle_form_checks-2159507-3.patch | 1.53 KB | mrmikedewolf |
#2 | securepages-toggle_form_checks-2159507-2.patch | 1.68 KB | mrmikedewolf |
#1 | securepages-toggle_form_checks-2159507-2.patch | 1.83 KB | mrmikedewolf |
Comments
Comment #1
mrmikedewolf CreditAttribution: mrmikedewolf commentedComment #2
mrmikedewolf CreditAttribution: mrmikedewolf commentedThis one is better, the filepaths don't start in the docroot.
Comment #3
mrmikedewolf CreditAttribution: mrmikedewolf commentedApologies I missed a couple of lines. Here is the final patch.
The main reason I had to implement this is because the domain access module makes all urls absolute. Allowing the option to turn off form checks is valuable in this case.
Comment #4
mrmikedewolf CreditAttribution: mrmikedewolf commentedSee here if the problems you are having are related to the Domain Access module.