Using drupal 7.8 & PHP 5.3.6
1. Create a vocabulary [Voc] like this:
term2
--term21
--term22
term1
--term11
--term12
2. Create a new content type, add a field [Term reference], WIDGET[Hierarchical Select], and set [Voc] as the vocabulary.
3. HIERARCHICAL SELECT CONFIGURATION as below:
Save lineage: Save only the deepest term[selected],
Level choice: Force the user to choose a term from a deepest level[selected],
Resizable: Enabled[selected]
4. Add a new content with field [Term reference],
Expected: normal
But:
Warning: explode() expects parameter 2 to be string, array given in menu_node_submit() (line 691 of D:\Program Files\VertrigoServ\www\drupal\modules\menu\menu.module).
Attachments are the related pictures.
Please help to check if you guys can reproduce.
Thank you very much!
Comment | File | Size | Author |
---|---|---|---|
#6 | fix_hs_menu_array_warning-1304002-2.patch | 1.36 KB | firebird |
#5 | fix_hs_menu_array_warning-1304002-1.patch | 1.11 KB | firebird |
config.png | 22.59 KB | 86chenjie | |
terms.png | 7.04 KB | 86chenjie | |
warning-msg.png | 14.32 KB | 86chenjie |
Comments
Comment #1
challenge CreditAttribution: challenge commentedI have this message too.
nothing more to add to your analysis, I'm doing something similar to you and it popped right there, same identical modules and passages.
It seems showing only on the backend, if I'm not wrong.
Comment #2
acbramley CreditAttribution: acbramley commentedI'm getting this with the hs_menu and is actually rendering the module completely useless. I can't save a menu item using hs_menu because I get this error on node save:
This is using content that previously was saved without using hs_menu, but I have tried removing the old menu item first before saving again but it doesn't work any better.
Comment #3
acbramley CreditAttribution: acbramley commentedComment #4
drupalthemernet CreditAttribution: drupalthemernet commentedI fixed this bug by adding an IF statement like this in menu.module file at line 705:
Comment #5
firebird CreditAttribution: firebird commentedHere's a patch that fixes the node saves.
Comment #6
firebird CreditAttribution: firebird commented..and here's a patch that also fixes the re-population of the hs elements broken by the previous one.
Comment #7
acbramley CreditAttribution: acbramley commentedPatch in #6 now makes HS Menu function correctly! (as long as jquery_update module is disabled)
Comment #8
giancarlopiccinini CreditAttribution: giancarlopiccinini commentedIf you found the patch can fix all the file hs_menu.module
I did not understand the lines to change
you can put it here for download this file
I have an urgent need to create Web
if I disable Hierarchical Select Menu
Hierarchical Select No error
thanks
Giancarlo Piccinini Italy
----- translated by http://translate.google.it ------
Comment #10
rv0 CreditAttribution: rv0 commentedI think this is a duplicate issue
patches already here
#1272538: Hierarchical Select Menu should also flatten on submit of node forms
Comment #11
firebird CreditAttribution: firebird commentedYes, it does look like a duplicate issue indeed.
Does your patch correctly re-populate the HS fields the next time the node form is loaded? I had to add another line of code (see patch).
Comment #12
rv0 CreditAttribution: rv0 commented@firebird,
It does on my site.
But that might be fixed by another patch which is in this issue queue.
#1271386: Hierarchical Select Menu should respect menu_options
or another one, which I'm having trouble finding atm ;)
In any case it is not related to this issue about node_submit...
Comment #13
Taxoman CreditAttribution: Taxoman commentedThe two other issues mentioned are reported to be in conflict with each other, and neither of them is deemed to be critical (or having the exact same scope as this one, although perhaps overlapping somewhat).
This issue, however, seems to be a real showstopper, hence its Critical status.
If the latest patch here is ok, and resemble an "easy fix", it should be committed to -dev asap.
Comment #14
rv0 CreditAttribution: rv0 commented@taxoman
both issues have been reported months ago, have been (partially) reviewed by the maintainer of HS, and are RTBC afaik.
the 1st issues' patch fixes this issue.
the 2nd issues' patch fixes another issue, and clashes with the first over 1 line of code, I'm not going to lose even more time with this by rolling combo patches (it's really basic and can be done manually)
a small look at the patch in this issue reveals it is not up to standard (why link to this issue in the comments?)
also the "re-populate the HS fields" part is unrelated to this issue.
cross posting and duplicate patches wont help push this issue forward.
closing this in favor of #1272538: Hierarchical Select Menu should also flatten on submit of node forms
Comment #15
FreeFox CreditAttribution: FreeFox commentedMaybe this is closed but I don't find the error message nor a patch in the "other" post so I suggest we keep this one open.
I tested the patch in #6 and my problem with "Warning: explode() expects parameter 2 to be string, array given in menu_node_submit()" is gone so I would say ... please commit
Sorry for re-open, if not ok, please close again. I'll don't touch it again ;)
Comment #16
rv0 CreditAttribution: rv0 commentedFreeFox, I really don't like playing issue ping pong
There's 2 patches in that post, how can you not find it? ...Comment #17
ArchangelGuidz CreditAttribution: ArchangelGuidz commentedConfirming that applying patches 5 & 6 works! Thanks!
Comment #18
Wim Leers#1272538: Hierarchical Select Menu should also flatten on submit of node forms's patch was committed, so this is fixed.
Comment #19
seehive CreditAttribution: seehive commentedJust to confirm that Patch in # 5 & #6 works fine for me , thanks for great work!!!
Comment #20
green monkey CreditAttribution: green monkey commentedjust a heads up
Wim, I see above this is considered fixed #18
- I'm seeing it on a new install Oct 25, 2012 for the version above - on Save
Will apply patch per #19
[note] my mistake this should have been posted to 7.x-3.0-alpha5
I will load the dev version instead [resolved]
Comment #21
AaronA CreditAttribution: AaronA commentedVerified that patches in #5 & #6 work for me also. Could this be rolled into the next release please?
Comment #22
AaronA CreditAttribution: AaronA commentedComment #23
geek-merlinlooks like this is already in current dev.
Comment #25
smallcoder CreditAttribution: smallcoder commentedJust posting a THANK YOU - this code was a life saver ;)