Closed (cannot reproduce)
Project:
Hierarchical Select
Version:
7.x-3.0-alpha3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Aug 2011 at 15:01 UTC
Updated:
2 Sep 2013 at 13:05 UTC
Since updating to alpha3, this module no longer works. It also breaks taxonomy by malfunctioning.
1. It will not create addtional select boxes after selecting a parent term.
2. On the form to add a new term in taxonomy, it shows no results in the 'relations' section but - New terms added say they have been added, show in the db, but dissapear from view. The only way to access them afterwards is through the DB. This is corrected by uninstalling Hierarchical Select.
3. Uninstalling and resinstalling the module, and ensuring that the tables for the module have been created from scratch does not correct the issue.
The module is currently unusable as is right now.
Comments
Comment #1
wim leers1. This works fine here. Please export your HS config and post it here, that may help me to reproduce the problem you're seeing.
2. This is covered by this issue: #1255880: array_flip() error when adding a Taxonomy term and has just been fixed.
3. This is the same bug as 1.
Comment #2
Routh commentedOk, I have updated to the dev module. This has fixed the taxonomy page issue, however I am still having the same issue with the genre field I have added to books. It will not create the second box when a top level item is created. I thought it might be a JS conflict, however the second box is now created perfectly on the form when adding a new taxonomy term, so I guess it can't be a JS conflict.
Here is my exported config:
Comment #3
wim leersTo be 100% sure it's not a JS thing, just disable JS. HS should still work just fine (it gracefully degrades!).
Comment #4
Routh commentedOk, I've done some playing/testing - here are my findings:
1. With JS disabled, the second box does indeed appear by using the 'update' button. However the add button does not work, and it becomes impossible to add genres at all.
2. With JS enabled, I used Chrome to edit the properties of the update button and removed the display: none; property. By doing so, I was able to use the update button on the top level items. This spawns the second box! It also allows me to add genres normally... so it seems that there is something gone awry, although I cannot say what at this time.
Obviously refreshing the page hides the update button again, so this is no permanent fix, however it seems that the JS script is not starting the 'onclick' trigger for the top level item box correctly to me, since forcing the function with the update button does work.
Thoughts?
Comment #5
wim leersCan you reproduce this on a vanilla D7 installation? In other words: what are the modules you've installed? (Some module may be conflicting with HS. You can easily generate a list of installed modules with drush:
drush pm-list > list.txtwill do that for you.)Comment #6
wim leersClosing due to lack of response.