As reported in my support thread here I have found that importing user tools fails when scripture references are in <book> <chapter>.<verse> format, and especially when they are gathered together in lists.
For example, any of the following occurring in a html document to be imported will cause the import to fail silently, and no user tool will be created:
Eph. 1.1-10, 12-14
2 Cor. 1.22; 5.5; Eph 1.14
Steps to reproduce
1. Create an HTML file containing any of the lines above.
2. File -> User Files -> Import User Tool...
3. Import the HTML file as a new user tool
Even if the above were not correctly hyperlinked, I would expect the import to run to completion and the user tool to be created. Ideally, they would all be detected and hyperlinked correctly.
At a minimum, if the import did fail I would expect a notification indicating the nature of the failure and the context (i.e. the line / reference that it failed on).
Import fails, no user tool is created.
In all of the cases shown above, converting the period to a colon allows the import to succeed. However, tracking back through 8 years of research notes and manually making this change is tedious, particularly when (a) there is no indication of what or where the problem is; and ( the same data imported fine into Accordance 10.
2015 MacBook Pro
OS X 10.10.2