Kiwitrees on Twitter

    access level, image, tools, 1939 Register, 3.0.0. setup, FAQ, php 7, timeout, media_links, logs, emmigration, slideshow, tab, widget, events of close relatives, block, I18N, MAC, ASSO, immigration, spouse, Google Maps, fatal error, shared note, pages, Histo, 5.6, internal messaging, repo, 500, follow, Georgian, custom modules, REFN, language, bug, flags, simpl_grey, defacto, name, living, transifex, 7.1, dropbox. token, release, add_asso_facts, logout, login failure, login, .mo, album, future, custom text, custom, cousins, wish, administration pages, 2.0.2, validation, divorce


    1669 posts

    Yes. I don’t see much value in it, and feel it’s causing more work than benefit. It hasn’t (yet) completely gone, just hidden while I make my mind up.

    If this was a large project with a team of developers it would be useful, but just for me its repetitive.

    I have two things I need to replace though, a store of the language .po files, and a list of changes in each version. I’m sure there are easier ways to achieve both though.

    I’m also moving towards making all downloads available for registered users only. I have some improvements to existing modules in the pipeline, plus a couple of completely new ones and don’t feel inclined to share them outside this small community. It also helps if I know who downloads them, so I can alert users directly if there are problems or changes.

    My personal kiwitrees site is