Closed (fixed)
Project:
Corresponding node references
Version:
6.x-3.2
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
25 Aug 2009 at 03:57 UTC
Updated:
25 Nov 2010 at 12:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
domidc commentedI cant duplicate your problem. Can you give me an sql dump from the corresponding node reference table in your database, so I can examine this problem more in detail.
Comment #2
philpro commentedThanks, I actually ended up using a different process for linking related nodes using views.
Comment #3
domidc commentedComment #4
jbomb commentedI'm having the same problem.
I did a bit of digging in the module and found that $query_values is always empty in corresponding_node_references_settings_form_submit()
Comment #5
domidc commentedI dont receive any more data about the issue so I m closing it down
Reactivate when more specifics are available.
Comment #6
steveray commentedSame problem here;
See attached SQL dump per request in #1 above.
Is it related to trying to set a relationship between two nodes of the same type?
It seems this was once disallowed for some reason, but the option is presented on the config page and that's the relationship I need.
Thanks.
Comment #7
steveray commentedI forgot to set status back to active, per #5
Comment #8
domidc commentedThis sql dump doesnt contain any table entries just the create statement. You should select in phpmyadmin to export the data aswell.
I ve tried to duplicate the problem using node references on the same node. Everything seems to be working fine.
Can you also list the content types and the node reference instances you are using.
Comment #9
steveray commentedThe Corresponding Node Reference table is empty... there is no data there.
The content type is custom via CCK, including file fields, date fields, email fields text fields.
Comment #10
domidc commentedIs it possible to have a complete dump of your database and code?
I m really puzzled here, everyone else got this module working...
Comment #11
domidc commentedComment #12
raphaelhuefner commentedHi!
I've got the same issue here.
DB dump is attached, but my code dump is around 5 MB (issue attachments are limited to 1 MB), therefore via external D/L:
http://cnr.raphaelhuefner.com/cnr-6.x-3.2-issue-558612-codedump.tar.gz
The MySQL Server version is: 5.1.37-1ubuntu5 (Ubuntu)
phpinfo() output is attached.
What further info do you need?
Comment #13
raphaelhuefner commentedI "found something":
The checkboxes with those really long names conflict with the PHP extension "Suhosin Patch 0.9.7". "Growing" those settings:
(on Ubuntu in config file /etc/php5/apache2/conf.d/suhosin.ini) beyond the default value of 64 did the trick to bring the checkboxes back into the
$_POSTarray.See also http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_...
Maybe putting those really long names into the values of the checkboxes could be one remedy?
Or putting them into hidden fields, which could be related to the checkboxes via some shorter names?
Sorry for not coming up with a patch for that right now, my deadline is right around the corner. I'll stay with configuring suhosin for now.
Comment #14
arianek commented+1 on this issue. just set it up using the instructions on the project page, and exact same issue. as this means the module is totally unusable, i'm going to set this to critical (but of course, feel free to veto).
Comment #15
arianek commentedit appears we've also got the same Suhosin Patch applied as described in #13 (demoting back to normal, as i'm assuming this isn't affecting *everyone* who tries to use the module.
Comment #16
domidc commentedMake checkbox names shorter
Comment #17
domidc commentedComment #18
domidc commentedThis issue is solved in version 6.4 which is currently in dev
Comment #19
domidc commented