Search Forums
Kiwitrees on Twitter

    Canada, MYSQL, time, hover, design, request, batch update, future, googlemap. modified, logout, session, errors, fancy image bar, language, latest version, gettext, special character, links, pop-ups, xmas, roadmap, REFN, Google Maps, Extra menus, advent, custom modules, 7.2, ckeditor, surname, abbreviate, CREM, spam, webtrees, notes, help, contacts, shared note, set link, logs, prefix, tools, click, husband, translation, 1939 Register, prison, close, 500, release, php 5.6, Require visitor authentication, age, message, formatting, lists, duplicates, 3.2.2, fact, 3.1.1, version


    554 posts

    On that note, I disagree with adding the DOB, moving the user name, and messing with the date in the resource_todo module. Also, the print function might be nice to give a clean printed listing but is it really necessary. The members in the families I track also have many names in common but adding a DOB would just add an unnecessary distraction and not a clarification. If there is any question about who the individual is, simply click on the name and look.

    The DOB-DOD is already in the other report so consistency – and again, to make sure it’s the correct person. If I’m looking at report on my iPad, it’s not easy to go back/forth making sure I’m picking the right person. DOB-DO(where known) helps. Actually, even on desktop, it’s preferred over “guess which one”

    Why move the user name; the only purpose that I can see is served by the current ability to sort the columns. The date listing has already been addressed.

    Again, it’s in the recent_changes test as it’s not the important field. Having the person and details are. In fact “by” is used instead of “username”, shorter.

    "A-D connections 3.3.1"
    PHP 7.0 Fast CGI

    "The Royals 3.3.1"
    PHP 7.0 Fast CGI
    mySQL server: 5.1.56
    MacOS: 10.11.6  (El Capitan)
    Browsers (mac): Safari  Version 11.0;  Firefox 56.0
    [updated: 07 Oct 2017]