Hi,

Thank you for the module -- if I can get it working in the next couple of days it will be a perfect fit for our site.

When I try to create a menu, I see this error:

warning: mysql_real_escape_string() expects parameter 1 to be string, array given in [local path]\includes\database.mysql.inc on line 321.

And the menu contains no items.

I've tried on a fairly clean install (Administration Menu and the Acquia Network connector are on) of Drupal 6.19.

My taxonomies are:

Vocabulary: Sports
Baseball
Basketball
Football

Vocabulary: Years
2003 and earlier
2004
2005
2006

I've tried with each vocabulary being #1 and #2, and the error remains the same. This was a test install, on the actual install, using the same vocabularies the error message has a slight difference:

warning: mysqli_real_escape_string() expects parameter 2 to be string, array given in [local path]\includes\database.mysqli.inc on line 323.

Any ideas? Anything I can do to help track it down?

Thanks

Comments

sjtout’s picture

sjtout commented
Title: Can't create a menu » Can't create a menu - doesn't work with D6?

I just tested this on a clean install of 6.09 (without the Acquia modules) -- thinking that maybe one of the recent security patches had begun the issue, but got the same result (parameter 1, line 321). In this install, Advanced Taxonomy Menu was the only non-core module. This makes me wonder whether the module works at all for D6?

NewZeal’s picture

NewZeal commented

I have just uploaded the module to a new install and created a menu. I did get a mysql escape string error but the menu still created. So there is a problem, but the module does work on D6 because I have it working on a number of sites. Try upgrading to a more recent version of drupal 6.x.

NewZeal’s picture

NewZeal commented
Status: Active » Fixed

Bug fixed and new release made.

sjtout’s picture

sjtout commented
Version: 6.x-1.1 » 6.x-1.2

I can build a menu now without seeing the error message.

But the real issue was that there don't seem to be any items in the menu. Perhaps this is user error.

Here's what I do:

1) click the Add option for Advanced Taxonomy Menu
2) type a name in in the "Name of menu system:" field, then use the same string in the "Module page: " (e.g.: sportytest2)
3) From the dropdowns for position, select 1 for one vocabulary (e.g., type) and 2 for a second vocabulary (e.g., year) -- both of these vocabs have a few items to test with (3 to 5) (DO NOT click 'Hide empty items')
4) Click Submit-- the menu is built
5) Go to Site Building -> Menus -> List, and click the new menu (e.g., sportytest2).

Expected: There will be some items in the menu.
Actual: The menu is empty -- there are no items.

Am I missing something?

Thanks

sjtout’s picture

sjtout commented

--this is with Drupal 6.19

sjtout’s picture

sjtout commented
Title: Can't create a menu - doesn't work with D6? » The 'Hide Empty Terms' checkbox doesn't seem to work

I think what was happening was that I didn't have any terms with those vocabs applied and Empty terms were being hidden despite the box not being checked. I added some items and the paths to those items showed up in the menus.

This is really exactly what I'm looking for. Would love to have the 'Hide empty' checkbox work, but can live without it and am just really happy that there's a solution for this. Thank you.

NewZeal’s picture

NewZeal commented

Try editing the menu and selecting the hide option. I think there is a problem when first creating the menu.

sjtout’s picture

sjtout commented

After installing the latest dev build, I turned on 'Hide empty terms', rebuilt then menu, then turned off 'Hide empty terms' and rebuilt the menu. So far, I don't believe I've seen the menu show empty terms. For my purposes, I really want it to hide empty terms, so it's working as I'd hoped. Thanks.

Status: Fixed » Closed (fixed)

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

hexabinaer’s picture

hexabinaer
Location Berlin, Germany
commented
Version: 6.x-1.2 » 6.x-1.3

Cofirm: the Hide Empty Terms checkbox doesn't seem to make any difference. For client presentation purposes I would really like to not hide the terms during development stage.

Drupal 6.22
A.T.M. 6.x-1.3
Configuration of the only vocabulary used in this module: multilingual - localize terms, multiple select, required.

Please let me know if you need more information for troubleshooting.