Closed (cannot reproduce)
Project:
Simple hierarchical select
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Mar 2013 at 16:38 UTC
Updated:
7 May 2013 at 06:57 UTC
If you save a node with some term selected and afterwards delete that term - shs field is not displayed when editing node anymore (with this term).
Comments
Comment #1
playfulwolf commentedhmm, everything works when clearing cache, but still it is a bug.
Comment #2
stborchertJust checkd on a clean install with latest code and it worked fine. The element is displayed (without preselected value) on node/edit after deleting the term I've previously set before saving the node.
Could you give some more details about your configuration?
Comment #3
playfulwolf commentedMy install is semi-clean install, with not much modules. What I did:
1. Created vocabulary with terms, most of them single hierarchy, some had 1 level of children
2. Created node type with required shs field, with the requirement to select the last child.
3. Created node content, selecting 1st level shs term (it was also the last level)
4. Deleted that term in Taxonomy manager.
5. Opened node edit form - cannot see widget at all. Refreshed page - no change.
6. Cleared caches - everything works.
Server is Wampserver Apache + php 5.3 on locanhost win7 machine, not much extra config made
Comment #4
playfulwolf commentedOk, I have repeated the same steps and in "5" step I still could see that already deleted term, but when I selected it and pressed save:
and cannot see the widget.
After edit page refresh with f5 or ctrl+f5 I still can see that deleted term and if I select it - the same error message appears (and no widget).
I am using Entity cache and Javascript callback handler modules, but with them disabled no change.
Comment #5
playfulwolf commentedbtw, I cannot see the widget from the beginning of edit if the term which was deleted was the first in vocabulary
Comment #6
stborchertEntity Cache does some very hard caching, which SHS could not take care of. SHS clears the default caches (especially its own).
There has been an error (fixed right now) with the integration of "js.module" so the elements of SHS won't be displayed at all (results in an javascript error "data is null") so using the next dev release might fix this for you.
Comment #7
playfulwolf commentedI am getting the same bug without Entity Cache also. Will wait for next dev t.y.
Comment #8
stborchertFeel free to reopen if this still happens.