I really like this module. I hope there will be a D7 version. :)
Thank you. ~~~

Comments

fernao’s picture

fernao commented

Hi there!

It's great that you like the module!

Yes, I'm planning to make a drupal-7 version, and your message is another stimulus to start the port.

I'll start working on that and as soon as possible.

cheers!

BettyJJ’s picture

BettyJJ commented

Thank you. Keep up the good work! :)

fernao’s picture

fernao commented

Hey!

I've started researching for the main changes needed for drupal 7. And one of then introduces a great deal: the change of the taxonomy module. Now it's associated with cck, and for each content, a new field needs to be created for each content.

Here goes a short explanation of the problems:

Drupal 6:

Tables:
term_data
term_node
vocabulary
node

Drupal 7:
taxonomy_term_data
taxonomy_term_vocabulary
node
field_revision_field_taxonomy_name

(where 'taxonomy_name' is a name choosen by the site admin)

I'm not sure of the better way to implement it, because in the module I need to know the table's name. I guess that I'll have to make a lot of new code on the administration and configuration of the module.

I think I'll have to create a configuration for each content type, that the user will enable and configure individually. But I'm not sure of that. What do you think?
Do you think it's a good thing that different content types has differente relevance configurations (associating different taxonomies etc) ?

BettyJJ’s picture

BettyJJ commented

I'm not quite sure I understand you. :)
It sounds like a good thing that different content types has differente relevance configurations, but if that requires too much trouble, maybe it's better to make a simple version that can work first? But again, that's my very amateur opinion. :)

fernao’s picture

fernao commented

Nice!

Well, I'll have to write lots of new code. Then, I'll make some tests... =D

thanks for your help!

fernao’s picture

fernao commented

Hi there!

Well, I've been working on the migration this week and realized that I'll have to rewrite most of the code. So, I've created a small plan for the drupal-7 version, including some new features, the complete refactoring of the relevance algorithm and some other stuff for improving it's configuration by the administrators of websites:

New features:
- embed a node api (#576712), for example to make it possible to embed it inside of a node
- complete rebuild of the relevancy algorithm, including adjusts for dealing with lots of terms in a same vocabulary
- take related terms into account (#591204)
- configuration per content type
- try to make a more "visual" configuration of the relevance elements
- debug mode to make it possible to configure the relevance together with a view of the preview results
- create an extra field for setting relevance for a specific node
- exclude list - put some nodes in a "don't show list" (maybe merge it with the previous item)

I hope I can release some code soon, even if it's not complete and fully operational.

If anyone has any other suggestion, please tell me!

now let's code!
:)
Fernão