Closed (fixed)
Project:
Hierarchical Select
Version:
6.x-3.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Apr 2009 at 06:53 UTC
Updated:
4 May 2009 at 06:50 UTC
Since there doesn't seem to be a post about this yet (and pretty hard to NOT to replicate) perhaps this is due to interference with some other module, but..
if i submit a node form and a field (not a HS tax field) doesn't validate; then the HS vocab that was working now states long error message about JS being disabled and the HS selector no longer works.
No JS errors have occurred and other JS functions still work. I do get a new Update button that lets me limp by.
Comments
Comment #1
liquidcms commentedi can see that 4 HS JS scripts do not get loaded (or get unloaded??) when the form fails to validate.
I can also see that one other JS file - og_access.js also does not load.
all the other JS files that load when when i initially go to node edit form (and HS is still working) are still present when form fails to validate.
Comment #2
wim leersThis happens with the latest dev snapshot?
Comment #3
wim leersThis is a duplicate of http://drupal.org/node/435136? Why?
Comment #4
liquidcms commentednope.. not a duplicate.
the other issue is that the latest dev version doesn't work at all.
this issue is that the dev version i had from a few months back; which does work; fails when the form doesn't validate.
Comment #5
liquidcms commentedtested on clean install of Dr6.10 and still fails.
still using old dev version - but will try new dev version (i.e. look at: http://drupal.org/node/435136) next
Comment #6
liquidcms commentedas posted on the other (different) ticket, the latest dev is still busted even on clean Dr6.10 install.. but it DOES work with menu admin, just not on taxonomy selector on node form; so i tried failing the menu form submit and sure enough it works ok there - so seems like both these tickets may be related only to cck (i.e. Hierarchical Select Taxonomy module)
Comment #7
liquidcms commentedonce this issue: http://drupal.org/node/435136#comment-1495962 with latest dev is sorted out; the issue reported here goes away.