Search Forums
Kiwitrees on Twitter

    multiple marriages, special character, tab, permissions, seo, ckeditor, links, errors, html, dates, styles, follow, googlemaps, 3.1.1, age, flags, pdf, 2.0, batch update, emigration, php 7, style, cousin tab, REFN, googlemap, timeout, tree, clipboard, edit interface, event, session, pop-ups, type, privacy, image, white screen, translation, prefix, json, shared note, themes, new feature, folder, kiwitrees theme, tags, index, My Page, Extra menus, FAQ, close, blocks, last change date, click, 3.3.1, ASSO, feedback, getClientIp, login, error, gettext


    110 posts


    Wasn’t trying to do anything special; just a simple search and replace. By trial and error have come up with procedure work arounds.

    The natural thing to do is enter the “search” phrase which triggers the program to search. After waiting for that and entering the “replace” phrase, you wait again for it to search. The work around is to do it backwards and enter the “replace” phrase first; the program then does a quick fresh. Then enter the “search” phrase.

    Because of the current behavior, the following work around for repetitive search and replace actions is also necessary. Clear the previous “search” phrase which triggers a quick refresh. Replace the earlier “replace” phrase with the new one; another quick refresh. Lastly, enter the new “search” phrase.

    If there is not much use of this program feature, a change certainly is not necessary. However, to avoid one of the two search times the user cannot use the intuitive approach


    Apache 2.4.27  PHP 7.19 MariaDB 10.2.8