Search Forums
Kiwitrees on Twitter

    updates, xmas, locked out, F.A.B., future, Favourites 3.0.0, admin, watermark, 3.2.3, descendant, Export/Import, IE problem, timeout, autocomplete, errors, googlemaps, footer, wish, simpl_research, widget, Fancy imagebar, re-order, kiwitrees 2.0.2, census assistant, Extra menus, cousins, default individual, fancy image bar, logs, xenea, HTML block, gettext, NCHI, FAQ, My Page, github, birth, custom modules, cousin tab, events of close relatives, formatting, relationships, defacto, not married, blocks, descendants, google, redirect, Support/Bug Reporting, googlemap. modified, responsive menus, login failure, configure, access level, fact, last change date, surname, order, 7.1, married


    1610 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