Closed (fixed)
Project:
Hierarchical Select
Version:
5.x-3.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
10 May 2008 at 01:14 UTC
Updated:
2 Jun 2008 at 08:53 UTC
Jump to comment: Most recent file
Comments
Comment #1
wim leersWhich version of IE?
Comment #2
32940stf commentedie6
Comment #3
wim leersWell, I can't produce any error. Please provide the steps to reproduce this.
Comment #4
wim leersComment #5
32940stf commentedI am getting the error when I open the "Edit vocabulary" page. The actual create page for a node works fine. So I imagine it has to do with the preview functionality.
Comment #6
32940stf commentedI just tried the May11 build and the problem still persists.
Comment #7
wim leersSorry, still can't reproduce. I think you need to tell me what your exact settings are… The easiest way to do that, is by looking at the
variabletable and sending me the value of thehierarchical_select_config_taxonomy-1entry.Comment #8
32940stf commentedHere you go:
a:5:{s:9:"config_id";s:10:"taxonomy-1";s:12:"save_lineage";i:0;s:15:"enforce_deepest";i:0;s:12:"level_labels";a:2:{s:6:"status";i:0;s:6:"labels";a:1:{i:0;s:0:"";}}s:7:"dropbox";a:3:{s:6:"status";i:0;s:5:"title";i:0;s:5:"limit";i:0;}}
Comment #9
wim leersNope, still can't reproduce.
Unless you have (or put) this site live, I'm afraid I won't be able to help you.
Comment #10
pingers commentedI have the same issue and may be able to make the site live within the week... if it's not fixed by then :)
Comment #11
wim leersOk.
I'm really curious what the cause of this is, because with these *exact* settings, I can't reproduce it… very odd!
Comment #12
32940stf commentedI am currently travelling on business. When I get home I should be able to get it up to a box as well. It will be a Windows box. What type of access do you need?
Comment #13
wim leersInitially, just access to the Drupal web site. If that doesn't give me enough information, I will need FTP or SSH (preferred) access as well.
Comment #14
NeuZeitgeist commentedI have the same note in IE7. When I try to add a new document having Hierarhical select I have the same note. I do "No" and continue to work, but in any case it is not very convinient.
Thank you for the useful module :)
Comment #15
summit commentedHi Wim,
I have the same issue. See attached picture. It is on IE6 with the latest .dev HS 3.
Settings are just installing HS3 and trying to update a vocabulary with it by using content/taxonomy/add/vocabulary
Hope this helps.
greetings,
Martijn
Comment #16
wim leersNeuZeitgeist & Summit: could you please provide your exact configuration? It'd be interesting if it's the same as 32940stf's. And if it's different, I might be able to reproduce it here.
Comment #17
NeuZeitgeist commentedI have the same note as Summit and 32940stf's. What configuration you want to know? I use Hierarchical Select 5.x-2.2.
Comment #18
wim leersSee #7 for an explanation of what I need.
Comment #19
NeuZeitgeist commentedMay be it is a problem of Jquery update? I changed it today and I have no this note in my IE7.
Comment #20
wim leersYou have to use jQuery Update 1.x, not 2.x. So it *might* be the cause.
Comment #21
summit commentedHi Wim,
In /misc I have got JQuery 1.1.2. What further configuration are you looking for please?
greetings,
Martijn
Comment #22
wim leersSummit: see #7.
Comment #23
summit commentedVariable: hs_config_taxonomy-
greetings,
Martijn
Comment #24
summit commentedIs this what your looking for Wim?
Thanks for going into this!
Greetings,
Martijn
Comment #25
wim leersIt seems something went wrong there: you have "hs_config_taxonomy-" as the config id, but it really should be "hs_config_taxonomy-", i.e. the vocabulary id is missing. Are you sure there's no other such variable?
Can you please go to that vocabulary's configuration form and hit the "Save" button and then test again? And please verify that a proper entry in the variable table exists then (i.e. one like "hs_config_taxonomy-1").
Comment #26
NeuZeitgeist commentedI run update.php as you told, but still I have no hierarchical_select_config_taxonomy in my table varible...
Comment #27
wim leersI'm writing functionality to export configurations right now. Let's wait until that's committed, then retrieving this information becomes super easy.
Comment #28
32940stf commentedWim,
I have set up a dev box which the behaviour is reproducable (it is a bit ugly right now so please forgive the cosmetics). I will sent to you directly the details. If you go into the categories and edit the "Where in the World" vocabulary, you should see the same behavior in IE6.
Comment #29
32940stf commentedBTW, it is the HS build as of May18th.
Comment #30
wim leersThank you very much, 32940stf! You've helped me track down the cause. :)
This problem only occurs if you have the jQuery Interface module installed. So either I have some JS somewhere on that config page that is conflicting, or I'm using it in such a way that I'm triggering a bug.
For a quick solution: just uninstall the jQuery Interface module. You no longer need it for Hierarchical Select – you might need it for other modules, but that's unlikely.
Comment #31
wim leersConfirmed: when I clear out common_config_form.js, it works. So it's somewhere in that file.
Comment #32
wim leersThe problematic code is:
I don't know *why* this is so problematic though. Especially because it only happens in IE, and even then only when jQuery Interface is installed.
Comment #33
32940stf commentedConfirmed, removing the jQuery Interface module resolved the issue.
Thanks again Wim
Comment #34
wim leersI found a work-around…
Changing
var configId = Drupal.settings.HierarchicalSelect.configForm[id];to
var configId = Drupal.settings.HierarchicalSelect.configForm.id;fixes the problem. It's all in the details, right? Sigh!
Comment #35
summit commentedHi Wim,
You mean deleting the sentence:
?
greetings,
Martijn
Comment #36
wim leersI fixed the typo above. Now you can see what it should be changed to.
Comment #37
summit commentedHi,
the above .js change is in common_config_form.js in the /include folder.
greetings,
Martijn
Comment #38
wim leersIndeed, as mentioned in #31. Note that I only posted this to indicate how minor the change was: this *is* fixed in the current tarball ;)
Comment #39
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.