role edit, block, UID, theme, internal messaging, chart, kiwitrees 2.0.2, googlemaps, transifex, resources, cousins, errors, 5.6, wish, lists, language, widget, dead, survey, descendants, login, bug reporting, clipboard, event, design, clippings cart, feedback, 2.0, dropbox. token, family, backup, descendant, gender change, repo, fatal error, ID facts, data errors, research tasks, custom modules, missing data, login failure, colors, .mo, release, styles, 3.1.1, upload, person, hover, research, IE11, tab, zend, menu, FAQ, watermark, GEDCOM errors, new feature, css, spam

Kiwitrees on Twitter

    1717 posts

    The short answer is no, it’s the way this tool was designed. So whilst it “might” be possible to change it, that’s not something high on my priorities so far. It was specifically done this way to make the function actually practical on large trees, on servers with more limited resources.

    But I’m puzzled by (or misunderstanding) the statement “It is really a pain to have to wait for 2 searches for each change.

    You only need to do this for the first record. Then with “Update”, or “update all” you can apply the same search and replace to all other matching records. If it’s not working like that w should investigate.

    My personal kiwitrees site is