Closed (fixed)
Project:
Simple hierarchical select
Version:
2.0.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Jan 2022 at 16:07 UTC
Updated:
9 Mar 2022 at 04:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
tmaiochi commentedI'll work on this.
Comment #3
tmaiochi commentedSorry, but I can't reproduce this error. Can you give me more details, please?
Comment #4
summit commentedHi,
Sorry, I try to reproduce it myself.
I need functionality like:
https://www.drupal.org/project/shs/issues/2712115 for new terms and
https://www.drupal.org/project/shs/issues/3248983 for term lineage.
And I think some of this code was interfering.
Now I have implemented clean latest .dev and patch from https://www.drupal.org/project/shs/issues/3241169
Now it works without being able to add new terms on node edit and without the term lineage. No WSOD anymoe.
But not this functionality also..
May be a check like I propose easy and may be not, I am not able to judge about that.
greetings and thanks for your quick reply, Martijn
Comment #5
mr.valtersComment #6
mr.valtersComment #7
joel_osc commented+1 for RBTC - patch fixed this error which was triggered when adding a paragraph to a node with an SHS field on it. Thank-you @mr.valters!
Comment #8
stborchertThis has probably been fixed with #3241169: Error saving null/empty value after 2.0.0-rc1 update but I'm extending the checks here.
Comment #9
stborchert