By a_c_m on

Background : I am using the module to link 2 ubercart nodes for an mp3 shop, product_track and product_album.

For this the module is perfect in all but 2 respects.

1. I want to be able to re/order the children, ideally with ajax to avoid many page refreshes (track listings are order sensitive), similar request to http://drupal.org/node/132176
2. I am a little concerned about the adding existing nodes method, when the site has a full catalog of tracks (say 2000) that add screen is going to get very full, perhaps an auto-complete field here instead? Similar request to http://drupal.org/node/132082

I do have a budget for this, around $50 for both.

(also posted to feature request for module : http://drupal.org/node/206235)

Anyone interested ?

⋅ Categories: Drupal 5.x

Comments

andredw’s picture

andredw commented

I need this feature as well. I am willing to contribute $50 for both as well.

a_c_m’s picture

a_c_m commented

So thats now $100 for the 2 features.

a_c_m’s picture

a_c_m commented

No one interested ?

a_c_m’s picture

a_c_m commented

Is $100 not enough for this kind of development, and/or is there a simple way to archive what I am trying to do.

a_c_m’s picture

a_c_m commented

Bump to see if there is any new interest...

--
acmconsulting.eu

jrust’s picture

jrust commented

The ability to sort the output of relativity is already built in by using views. Under node relativity display settings (admin/settings/relativity/display) there is the rendering option for children nodes. And since you can use a view as the rendering option you have all the sort power of views at your fingertips.

An example view that I created for my audio tracks has the following: Page View enabled in Table mode, Fields of Title and Audio player, Filters is Published and Node type, Arguments is "Relativity: Parent Node ID" (this is the really important one!), Sort is "Product: List order". Works like a charm.

a_c_m’s picture

a_c_m commented

I think you missed what i was asking for, display once they are linked is fine.

This bounty is to add functionality to selecting related elements.

If you find this module useful and think this functionality might add to it, please pledge some money :)

Drayen

--
acmconsulting.eu

andb’s picture

andb commented

I'm also interested in the autocomplete part, maybe the ordering. Perhaps it would be best to split the feature request / bounty into its component parts in order to move things forward. These seem to be the needed parts:

A. Ordering
1. Weight for children per relativity relationship, as per #132176: Ordered graph structure
2. A tool to modify these weights quickly and easily (this could be done as a list of all children, grouped by node type, with a weight drop down, for example, I don't see the need for AJAX here)

B. Attaching (preferably with the possibility to select multiple entries at once)
1. Autocomplete (I just put up a feature request specifically for this, as other requests were too vague) #245382: Autocomplete field to select child nodes
2. A graphic view which would allow drilling down through fields, filtering to find wanted records, then provide a check box allowing selection of multiple nodes, with a submit button at the bottom to end the operation. (I found no reference to a tool like this, but would be happy to write it as a requested feature)

a_c_m, andredw, do these sound like the correct parts that you are interested in?

lordnacho’s picture

lordnacho commented

Used CCK to add a field, "Weight" to my node type called "item".

Then in relativity.module, in the function theme_relativity_show_children, I changed the query to:
$result = db_query('SELECT a.nid FROM {relativity} a, {content_type_item} b WHERE a.nid = b.nid and parent_nid = %d order by b.field_weight_value', $parent->nid);

This required all nodes to have the weight set, so if you have old data, you can default it to zero or something.

Hope this helps a little.

a_c_m’s picture

a_c_m commented

Interesting, a great idea and simple stop gap solution - i like it !

I'm about to re visit this for a new project so may have more money to throw at the problem or just do it myself.

We really want the drag and drop (users love it) and the auto complete feature is a must, as large (5000+) catalogs will soon get difficult to control/handle.

a_c_m
--
acmconsulting.eu

arne.olafson’s picture

arne.olafson commented

Hacking the module is unnecessary, and didn't work for me. Creating a cck weight field is smart, and you can sort your View based on that. I used a dropdown list.
Hope that helps

a_c_m’s picture

a_c_m commented

http://drupal.org/node/245382

One part down, one to go.

--
acmconsulting.eu