Jump to:
| Project: | CiviNode And Civinode CCK |
| Version: | 5.x-1.2 |
| Component: | CCK Integration |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Drupal 5.7 w/ CiviCRM 1.7
I have a custom content type with 2 CiviNode CCK fields. Both use autocomplete. One is a single required value, the other is an optional multiple-value field. These are for the leader and option co-leaders for a particular event.
When I create a new node, enter a name in the leader field and press save, all is well. When I click on the node's edit tab, the leader values are "upside-down": the value of the leader field is in the bottom-most of the co-leader fields; the leader field is blank. Saving at this point gives me blank leader and co-leader fields.
I've wrestled with the 5.x-1.2 version of this module for 3 days now and am backing up to the 1.1. version now.
I look forward to the next release; I'm willing to help test for this in future updates.
Comments
#1
yes I am having the same problem.
Could it be a dojo error with Civi?
I am using civi
1.9.11960 Drupal PHP5 (3 installs are verified to have this problem)
BUT on another server
1.9.11960 Drupal PHP5 DOES WORK!
#2
I posted else where too.
I copied another folder of civinode / civicrm from a server that was working and all is well.
I can send you those folders.
The versions ALL seemed to match but, and I could be missing something, it did not work.
Send me an email if you want an archive of the civicrm and civinode folders that work.
I am going to test more soon if it is civinode or civicrm that fix/broke the settings.
I have a number of sites using this so I will test on them later today or next week.
Al
#3
Almost certainly a Dojo problem.
I'm inclined to remove the Dojo stuff and replace it with some custom jquery stuff. This has some downsides: in particular, I've seen some problems with IE 6 with the solution I'm considering.
What do folks think about this?
#4
Torenware,
I'd like a little more info on the IE6 problems, but from my experience with using a CCK civinode dojo widget vs using civinode_contact_auto_selector() in a custom form, I *like* how the widget in civinode_contact_auto_selector works better than the dojo widget. In particular, it "seems" to have a faster response time, though I was guessing that's because I don't restrict its results to a CiviCRM group and the CCK civinode widget is restricted to a group. The jQuery widget also has an indicator that a search is taking place, which the dojo widget does not.
I also haven't seen any problems in IE6 using the widget in civinode_contact_auto_selector.
That's my .10 worth.