angelneychev

Hi Richard,

Glad the photo URLs worked. Noted on the timeout with 1700 rows, and
splitting the file is the right workaround for now. Processing large
imports in batches is on my list.

On the colours: here is how the tree looks on my own installation, five
generations deep:

https://prnt.sc/Hh20Y31lwkF-

Every cell is tinted, blue for males and pink for females, in all five
columns. So the colouring itself works.

I suspect what you are seeing in your last column is your theme
striping the table rows rather than our colours. In a pedigree the top
of each pair is the sire and the bottom the dam, so alternating row
colours look exactly like male and female colouring. Your other columns
are single cells spanning many rows, which is why nothing shows there.

Two things would tell me for certain:

1. In the page source, does dogped-pro.css appear anywhere?
2. Right-click one of the plain cells, choose Inspect, and tell me
   whether the td carries a class ending in cell–male or cell–female.

A link to the page would be quicker still. If the site is not public
yet, or you would rather not post it here, send it through
https://spotmaniac.com/en/contact and I will look at it directly. Pro
questions are better handled there in any case, as these forums are
meant for the free plugin.

Best regards,
Angel

Hi Richard,
No need to apologise, you did nothing wrong. Your CSV is fine, this was
a bug on my side.
The importer saved the sex exactly as your spreadsheet spelled it, so
“Male” went into the database as “Male”. Everything else in the plugin
compares against lower case, so those dogs matched neither value: blank
in the editor, labelled female on the front end, and no colours in the
pedigree.
While fixing it I found the same problem in the date columns, which is
worse. Dates were stored as written, and the editor only understands
YYYY-MM-DD, so it showed an empty date box. Saving such a dog would
have written that empty value back and lost the date for good.
Both are fixed in Pro 1.2.2, attached. Your 1500 dogs are repaired
automatically when you update, so there is nothing to import again.
Worth knowing: if the sex column does not say male or female, that row
is skipped.
Thanks for taking the time to report it. Two real bugs out of one
import is a good catch, and both were worth fixing.
Best regards,
Angel

Hi Richard,

Thanks for the detailed report, and no, you were not missing anything.
That was a real bug, and your description was precise enough for me to
reproduce it straight away.

What was happening: the plugin waited for a full click on the search
result, but the result list was already being dismissed the moment the
field lost focus. On a slightly slower click, or in some browsers, the
list closed before the click registered, so the selection never
happened. That is exactly why you were left with "- None -" in the
dropdown and your typed text still sitting in the box.

This is fixed in version 1.0.2, which is now live on WordPress.org, so
it should show up as an available update shortly. The result is now
applied the instant the mouse goes down, so the selection always
sticks.

While I was in there I also fixed the part you were most likely
expecting anyway: the Father and Mother dropdowns are no longer empty.
Each one now lists the 50 most recently added dogs of the matching sex,
so with a small database like your two test dogs you can simply pick
the father from the dropdown without typing anything at all. The search
box underneath still reaches every other dog in the catalogue, which
keeps it usable once a breed club database grows past a few dozen dogs.

Two more things worth mentioning, both aimed at keeping a pedigree
sane. A dog is no longer offered as its own parent, in either the
dropdown or the search. And a link that would close a loop is now
refused outright: if the dog you are editing already appears somewhere
in the ancestry of the dog you picked as its parent, the save is
rejected and the reason is shown on screen, so two dogs can never end
up descending from each other.

The same improvements are in the Pro submit form, in case you get
there.

Thanks again for taking the time to write it up so clearly. It turned
what could have been a hard-to-catch timing bug into a quick fix.

Best regards,
Angel