Search Forums
Kiwitrees on Twitter

    3.1.1, roadmap, widget, library, prefix, themes, statistics, html, fancy image bar, 3.2.1, add missing death, margin, add, css, 3.0.0 widgets, emigration, sidebar, googlemap, 3.2.2, data errors, random_media, mobile, Google Maps, married, locked out, pdf, datatables, MYSQL, session, Require visitor authentication, updates, birth, internal messaging, Extra menus, default individual, webtrees, FAQ, login failure, children, BAPM, .mo, dropbox. token, ID notes, cousins, tree, descendant, autocomplete, php 7, events of close relatives, IE problem, translation, media_links, cousin tab, menu, Administration, fancy tree view, individual resource, colors theme, Support/Bug Reporting, white screen


    1612 posts

    There are no width parameters controlling the width of any of those columns. They each take as much space as they need, only using more if it’s spare after all the columns are rendered, starting from the left and working across. That does mean that the last (place of death) will often be wrapped.

    Its not practical to set column widths given the infinite variations on content (data) length, screen size, theme design, screen font and zoom settings, etc..

    Similarly forcing a “nowrap” policy on (for example) the place names could get crazy when some people have place levels extending to 6 or even nine parts. Even on my site with a maximum for any place of three levels it results on the table extending wider than the screen unless I go full screen on my 27 inch monitor!

    So the only solution is to physically remove the two “anniversary” columns. Even that will only improve things for some situations, not others, and simply leave a lot of white space for many. Those columns have been there since PGV was invented. It would need a major user consensus to remove them.

    Also, that display is common to other parts of the system, especially the individual list pages. So any change will effect those too – and I wouldn’t want to start creating more display variation than necessary.

    As is often the case, the most common problem with busy displays like that is small screen sizes and / or large fonts / zoom settings.

    My personal kiwitrees site is