Closed (fixed)
Project:
Contact form blocks
Version:
6.x-1.2
Component:
User interface
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Nov 2011 at 12:21 UTC
Updated:
21 Mar 2012 at 16:50 UTC
When I assign a contact form block into a region and specify the block to only appear on a certain node path then instead of loading the page with the node and the contact form in the region, I am redirected to the (baseurl)/contact path. In other words the node where the specified block should appear is inaccessible and I am redirected to the contact page where the block is rendered in the region instead, although that was wasn't specified in the block visibility settings.
The url link points to the correct node. Really strange...hehe
Comments
Comment #1
TomtomVer commentedchange assignment
Comment #2
ben coleman commentedI'm seeing this also upon upgrading from 6.x-1.1 to 6.x-1.2. Pages configured via a contact form block's Page Visibility Settings to have a contact form block shown on them are instead redirected to (baseurl)/contact. In our case, that's just about every page except /admin/*, which practically shuts down our site (except for people wanting to fill out the contact form). For the moment, we've backed off to 6.x-1.1.
Comment #3
grey_ commentedStill no fix for the 6 branch? Breaks my site, marking this as critical.
Comment #4
rcharles commentedSimilar error where any/all/admin/content links redirect to http://sitename.tld/contact .
Reviewing modules installed I thought possibly a conflict.
With two (2) test Contact "categories" set-up for testing I reviewed the MySQL blocks table and it seems "Form block" and "Contact Form Blocks" are overlapping features.
Solutions:
Good luck.
Comment #5
ben coleman commentedWe don't have Form Blocks installed here(nor Contact Form On Node), so at least here the problem isn't a Contact Form Blocks/Form Blocks conflict.
Comment #6
ben coleman commentedAs ancym notes in http://drupal.org/node/1441620#comment-5611140, this is a problem in Contact Forms. There is a patch for it in http://drupal.org/node/233024#comment-5700950. Apply that patch, and this problem goes away. We've been able to upgrade to CFB 6.x-1.2 without problems after applying that patch.