I didn't see an open issue or a D7CX pledge... @maintainers, are you planning a D7 version? Anybody else? Or are you recommending a different technique for D7?

Comments

indytechcook’s picture

Yes, the maintainer (singular) or me, is going to start D7 as soon as I fix the last major update bug in D6. I had originally wanted to introduce a a V3 of D6 as a total rewrite with my totally lack of time has screwed up my plans.

This is a good place to discuss the best way to port to D7 with the current functionality.

I need to update myself with the new features (taxonomy fields). I wasn't sure if using fields was the best idea. I wan to get away from using variables for all of the settings. I'm open to new ideas.

indytechcook’s picture

HEAD has been updated to latest from D6 branch to start the D7 port.

indytechcook’s picture

Version: master » 7.x-1.x-dev

The first version of a working D7 taxonomy menu. None of the options are implemented and there are a few bugs but it does create the menu.

http://drupal.org/node/794334

Vidus’s picture

Keep up the good work on the module. It's excellent. Hoping to integrate a Drupal 7 build of it into the course websites my department at my university will use once 7 launches.

Main issue for us:
Keeping the live changes to menu as terms are added, and the custom path for the main menu button (we usually use a view to list all the terms at that path, to keep things working well if someone doesn't have suckerfish going in their browser)

indytechcook’s picture

Just to give an update. The current D7 version kind of works, or least it used to "kind of" work when I first created it. Once the API become frozen on D7, I will get back to it.

zenlan’s picture

Last week I managed to build a taxonomy menu using this module (D7 beta1 and beta2) but this week the module is flagged as 'unsupported' in admin/reports/updates :

Taxonomy Menu 7.x-1.x-dev (2010-Jul-11)
Project not supported: This project is no longer supported, and is no longer available for download. Disabling everything included by this project is strongly recommended!

Can anyone confirm the status of this project for Drupal 7?

Just want to know if I need to look for other solutions or simply bide my time. Thanks in advance! :)

dstol’s picture

Not supported is kind of scary sounding but #5 sums it up about right.

googletorp’s picture

Status: Active » Needs review
StatusFileSize
new19.62 KB

I've worked on making taxonomy_menu usable.

refactoring might be needed at some point, my goal was only to remove bugs and get the functionality working. This should work with Drupal 7 beta 2.

googletorp’s picture

StatusFileSize
new22.17 KB

Updated patch to fix the batch update.

dstol’s picture

googletorp+++++

I was planning on spending some time with the D7 version very soon.

+++ taxonomy_menu.database.inc
@@ -78,17 +78,28 @@ function _taxonomy_menu_delete_all($vid) {
+  $result = db_query("SELECT field_name FROM {field_config} WHERE type = 'taxonomy_term_reference';");

Why undo DBTNG?

Powered by Dreditor.

dstol’s picture

Status: Needs review » Needs work
googletorp’s picture

#11 The problem with what you were doing, is that the taxonomy_term_node table doesn't exist anymore. So there isn't really a centralized place where Drupal stores info about taxonomy terms. They are now stored as fields, which not only could be on nodes, but could be on anything really. I'm new to the field API, so there might be a smarter way to do this, but at least this actually works.

But for D7 a lot of stuff might need to be rewritten, since taxonomy terms can be on anything entity now, not just nodes.

dstol’s picture

Yeah, I'm aware of this. Like I always say, patches are welcome.

googletorp’s picture

Status: Needs work » Needs review
StatusFileSize
new20.99 KB

Updated patch for the resent changes and added a small fix as well.

pcambra’s picture

suscribe

dstol’s picture

Status: Needs review » Needs work
+++ taxonomy_menu.database.inc
@@ -77,17 +77,28 @@ function _taxonomy_menu_delete_all($vid) {
+  $result = db_query("SELECT field_name FROM {field_config} WHERE type = 'taxonomy_term_reference';");
+  foreach ($result as $field) {
+    $field_name = $field->field_name;
+    if (isset($node->$field_name)) {
+      $tid_field = $node->$field_name;
+      // Loop through all the languages.
+      foreach ($tid_field as $tid_field_languages) {
+        // Loop through all the tids
+        foreach ($tid_field_languages as $tid) {
+          $tids[] = $tid['tid'];
+        }
+      }

I can't believe 4 nested control statements is the best way to go about this. BUT it works on the other hand.

Powered by Dreditor.

googletorp’s picture

#16 I agree. I have rushed through taxonomy_menu to make it work, but nothing else. You could probably do the above someting like this. The problem is that we don't really know how taxonomy tids are stored anymore. On the other hand, when we do figure out how to do this more nicely, it should be able to work, with not only nodes, but any entity. The work on making taxonomy_menu work for entities rather than nodes is a whole other story though, and that's where most of the work needs to be put to make this module not only work in Drupal 7, but to be really useful for Drupal 7.

dstol’s picture

I'm considering committing #14 just so we can have it working. I'm feeling some pressure from the impending D7 release.

dstol’s picture

Commited #14. Thanks googletorp.

http://drupal.org/cvs?commit=468858

rfay’s picture

Status: Needs work » Fixed

Shouldn't this go to fixed?

Congratulations!

dstol’s picture

Yeah I guess. Woo!

But by no means is tax menu 7.x as feature complete as 6.x is.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.