Needs work
Project:
Contact form blocks
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
8 Feb 2012 at 19:13 UTC
Updated:
4 Mar 2017 at 16:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
andypostPatch and marked as duplicate #1308720: Undefined index: 1 in contact_form_blocks_content() line 73
12) fixed path in hook_admin_path
13) fixed wrong permission name
14) fixed css selector
Comment #2
fuerst commentedandypost, Thanks for the work!
@cr0ss: Any word on this patch?
Comment #3
cr0ss commented@fuerst, seems like patch is able to improve 7th version of module, so it can be applied.
@andypost, thank you for your great work!
Comment #4
andypostLet's get this in and roll a stable or rc release - by this way the module gets more attention and testing because users does not read code and likes stable releases
Comment #5
juliekj commentedI get the error "Undefined index: 1 i contact_form_blocks_content()" on my site using the Contact form block module (7.x-1.x-dev).
According to this issue: http://drupal.org/node/1308720 it should be fixed here...
Do I need to add a patch to my copy? Or is there a new version coming out soon with the patch includede?
Not to steady with coding things (designer) so I'd rather not mess with the code - patch issue myself ;)
Comment #6
fuerst commentedTried the patch using a vanilla Drupal 7 and 3 different Contact form blocks at one page. What I found so far:
$form['cid'] = array('#type' => 'value', '#value' => $category);in contact_form_blocks_content() does not have any effect.Comment #7
JoshOrndorff commentedIt looks like several different issues are covered in this one patch, and an issue with one of them is keeping the rest from being committed.
Could we split it into several patches, or get an update to get the whole thing applied? I'd be happy to test a new dev if the patch is applied.
I think andypost is right about getting a beta or rc. More people will be willing to give the module a shot if it is more stable.
Let me know if I can help at all. Thanks,
-Josh Orndorff
Comment #8
fuerst commentedYou are right: one patch per problem would be easier to handle. And for every patch one issue in the module's issue queue. That way we can close this issue and work at the others.
Comment #9
kaizerking commentedGood work , Thanks , this works nice!!!
Comment #10
oschuetze commentedAre these patches still up-to-date? Or is this already merged into the repository?