Hi-

I am trying to replace hierarchical select with SHS (7.x-1.6) and am so far very happy!
I just noticed when I looked at in on a windows machine running IE that the text field of my taxonomy field is replaced by it's ID number, and the select option is broken.

It works great on FF, safari, chrome on my mac, and even in FF on the PC but it is not working on a pc running ie. (Windows 7 IE 8.0.7601)

Here are two screenshots from the PC, on in FF the other IE. (rhyming unintentional)

Any advise is appreciated.

Thanks!

CommentFileSizeAuthor
ie8-shs.PNG7.45 KBdharper
ff-shs.PNG10.93 KBdharper
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

stBorchert’s picture

It seems the JavaScript is not loaded. Please test the latest development version. In this version there is a fallback if the JavaScript will not work.

dharper’s picture

stBorchert -

Thanks for the tip. The dev version worked as advertised when the JS was not called. This will be a good workaround until I can figure out the cause of the problem.
After some more investigation and trial and error, I discovered that the IE8 browser did have js enabled, and the SHS drop-down DID work on a simple content type. The SHS will STOP working when it is wrapped in a multi-page section!

I've tried to compress the JS, thinking that may be why the JS is being ignored for SHS by IE, but no luck.

To reproduce: Make one SHS dropdown as the first one in a content type. Them make a multi-page section, then tuck a SHS dropdown INSIDE one of the pages of one of the sections.

Thanks in advance for any thoughts/tips.

PS How muck trouble will I be in if I go live with a dev version of the module?

stBorchert’s picture

Status: Active » Postponed (maintainer needs more info)

How exactly did you create the multipage sections (which module did you use, which configuration, ...)?

How muck trouble will I be in if I go live with a dev version of the module?

As the dev version fixes some issues of the latest stable release it will cause less trouble than version 7.x-1.6 ;)

dharper’s picture

I am using the fieldsets module to create a page division then a page within that.
Then in the "manage fields" section of the content type (project) I move the
'Department' under that page division. And assign shs as its widget.

I'm on a bus to Boston with sketchy wifi. More later if y need it.

Thanks!

Dan

dharper’s picture

stBorchert -

I'm sorry, I mis-spoke. I'm using fieldGROUP module to group fields into fieldsets in the content type. (v-tabs, h-tabs, pages, divs, accordion). I think the problem in IE may be that the HSH js in not getting picked up when the select list in inside a field-group. Kinda like a cloaking device, but in a bad way.

Using the dev version has solved my issue for now, so IE folks will see the hierarchical drop-down, it will just be in One window that looks like:

food
-meat
-fruit
--red fruit
---apples
---cherries
--blue fruit
---blue berries

One last thought (if I'm not pushing my luck) Using HSH in views is killer good! BUT if I could get the 'more' arrows AND the node total in views, I'd give up coding forever! And if it could have an aggregate behavior that too would be bonus.

So the above choice fruit in an exposed views filter would look like "fruit(3) >" AND when I select that as the filter in SHS, I get apples, cherries AND blue berries in my view.

Thanks for a thin, powerful and helpful module!

Dan

4fs’s picture

I am also having this issue, although on all browsers (displaying the id and not the text of the taxonomy term). I am using ubercart and the issue is occurring on product listing pages (custom catalog view) where I have some exposed filters such as filter by e.g. 'brand' etc. I am also using views hacks to limit the number of exposed options to terms on products. I am also using Better Exposed Filters for some addition filtering options on my views. This issue happened when I switched to the dev version and is corrected when I revert back to shs 1.6.

However, if I revert back to 1.6 then my shs taxonomy terms on the node edit page is blanked out. The blanked out term field could be related to the following issue posts as I have the High-performance JavaScript callback handler enabled:

https://drupal.org/node/2015487
and
https://drupal.org/node/2001298

Update: Just wanted to add I am also using field group for my field layout. I am also using taxonomy menu going inside a superfish menu if that helps at all.

4fs’s picture

Status: Postponed (maintainer needs more info) » Active
stBorchert’s picture

Issue summary: View changes
Status: Active » Closed (cannot reproduce)