Create a D7 release
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | cnr_201102162.tar_.gz | 6.03 KB | czigor |
| #13 | cnr_20110216.tar_.gz | 6.35 KB | czigor |
| #12 | corresponding node references - drupal 7 version | 6.3 KB | czigor |
Create a D7 release
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | cnr_201102162.tar_.gz | 6.03 KB | czigor |
| #13 | cnr_20110216.tar_.gz | 6.35 KB | czigor |
| #12 | corresponding node references - drupal 7 version | 6.3 KB | czigor |
Comments
Comment #1
ryan.armstrong commentedsubscribe!
Would love to see this happen. It's the last big piece of the puzzle for a site I've been toying around with to move to D7.
Comment #2
p4trizio commentedIt would be great to have this module on Drupal 7!!! I cannot use anymore node_reference without this module.
I'm ready to help.
Comment #3
domidc commentedWell I m working on a 6.4 release which will solve the issues this module has. After that I ll start working on the D7 release. I think its best to finish 6.4 and have the solved issues in the D7 release.
I m not sure how the new field api works in D7 and since this module relies heavily on the content api which doesnt exist anymore I m expecting quit a bit of work. If you want to help you could do so by figuring out how we can use the field api to handle the corresponding node references.
Also I believe the structure of how data about fields and tables is stored has changed too, so this will have to be remade aswell.
The new pieces I m planning to put in the 6.4 are :
- the batch api to update existing refs (should remain the same in D7)
- drush integration to update the existing refs (should remail the same in D7)
- Unit test support (unknown?)
These feature I like to have in the D7 module aswell.
Comment #4
domidc commentedJust to inform you guys. The D6.4 release is finished and i ve set up a D7 branche on the module, there is nothing in it yet but all is ready to begin development. My energy will now be focused on the D7 release.
Comment #5
ryan.armstrong commentedAwesome news! ;)
Comment #6
to.stepan.kuzmin@gmail.com commentedSubscribing!
Comment #7
jcarlson34 commentedWow. Just stumbled on this module. Looks awesome. Subscribing for D7. :)
Comment #8
TimelessDomain commentedDrupal 7 has the ability to have fields on terms. So you now you can now reference a node from a term & a term from a term. They call this "term reference" which is similar to node reference, except it is with terms. D7 CNR should have the ability to have corresponding term/term, node/term, and node/node references. This would solidify CNR's value to the community long-term, as this feature will be needed by many. Thanks
EDIT: User Reference is also a field now. Current reference fields: Term; Node; and User. (Add any others that exist, though i can't currently think of any other that could have a 2-way relationship). So instead of just corresponding node references (CNR), this module should become corresponding entity references (CER), or corresponding references (CR)
Comment #9
Unnamed commentedSubscribing!
Comment #10
czigor commentedI started working on a drupal 7 version. I hope I will have something working later this week. Is there anyone else who has already something? I would like to avoid inventing the wheel.
Comment #11
ryan.armstrong commentedThere is the Relation module: http://drupal.org/project/relation
But as of right now all it does is provide a node relationship field like what was in CCK, it doesn't to back references. But it is looking like it might be the goto module for doing node relationships, rather then the ported version of nod ref from CCK, so it could be worth checking out.
Comment #12
czigor commentedThanks, I knew about the Relation project, but as it is not working yet and also there are sites using node_reference module I thought this port might still be useful.
For me the module is working now under Drupal 7, except for the bulk update part ("Update existing node" menu). I will try to handle it later this week. Comments are welcome!
Comment #13
czigor commentedThis one has the Updating work as well. Settings moved to Configuration.
Comment #14
czigor commentedSorry, I am quite new at this. The same as before, but after Coder module has seen it.
Comment #15
czigor commentedComment #16
domidc commented@czigor if you apply for a cvs account I ll add you to the maintainers list.
By this I confirm czigor will become a maintainer for cnr.
Comment #17
czigor commentedThis is the sandbox project page where the latest code can be accessed.
Comment #18
domidc commented@czigor I added you you the project so you can create a release.
Comment #19
czigor commentedSince the release is out, I mark this as fixed. Please create additional issues if you find a bug etc.
Comment #21
TimelessDomain commentedThis may become deprecated in d8 (replaced by http://drupal.org/project/ref_field ) - unless it can expand to handle corresponding entity references - #1182686: Corresponding Entity Reference Fields
Comment #22
domidc commented@TimelessDomain I have seen an effort has been made in cer by adding a syncing option to the entity refs. Is there a need to help you guys out with anything? I dont think it is useful to have the same functionality twice, unless moving it to a separate module would be needed?