magicsunday / webtrees-descendants-chart

SVG based descendants chart module for webtrees genealogy application.
GNU General Public License v3.0
26 stars 8 forks source link

ruined output (for left and right orientation) #60

Open arbor95 opened 2 months ago

arbor95 commented 2 months ago

Describe the bug can not see anything or simply lines

To Reproduce Steps to reproduce the behavior:

  1. Go to Heinrich Frese
  2. Click on 'left', click on 'view'
  3. See output

Expected behavior see images and data, moving around

Screenshots not necesssary Desktop (please complete the following information):

Additional context None

magicsunday commented 2 months ago

Seems to Happen at https://freris.de/tree/frese/individual/XI8/Johann-Frese

If you select him with 2 generations the display gets corrupted. Can you extract his gedcom part and append it here, so I can test it?

arbor95 commented 2 months ago

Sorry for the delay. clippings.ged.txt I suppose this candidate (a second wife, without real data) Bernard.ged.txt

console debug output: VM457:1 Uncaught TypeError: n[1] is not iterable at SVGTextElement. (:1:64736) at Te.data (:1:25441) at $i.addNameElements (:1:65260) at :1:64636 at Te.call (:1:26941) at $i.appendName (:1:64335) at Ri.drawNode (:1:74205) at :1:72529 at Te.call (:1:26941) at Ri.nodeEnter (:1:72515)

Further test give a hint: The second wife of Bernard is N.N., handled as special case. When renaming the surname (perhaps to DoNotKnow) the bug is gone.

magicsunday commented 2 months ago

The problem no longer seems to exist in the current development branch (https://github.com/magicsunday/webtrees-descendants-chart/tree/2.1). Is there a way for you to test this? Unfortunately, I won't be able to create a new release today or tomorrow.

arbor95 commented 2 months ago

seems as if its gone there. Only thing is, the presented name is now N. instead of N.N. Nachkommentafel von Heinrich Frese

arbor95 commented 2 months ago

std webtrees shows N.N.

image

magicsunday commented 2 months ago

Should be fixed in latest version in branch 2.1