Search Forums
Kiwitrees on Twitter

    json, not married, 1939 Register, design, statistics, pdf, Advanced search, 3.1.1, sanity, translation, internal messaging, tabs, dead, IE11, kiwitrees 2.0.2, address, clippings cart, configure, margin, future, performance, person, google, default individual, folder, Add a wife, cousins, burial, name, surname, Administration, new feature, Canada, data errors, road map, census, updates, colors theme, tab, reports, 3.3.2, seo, BAPM, installation, github, research tasks, styles, simpl_grey, 7.2, time, add_asso_facts, white screen, Extra menus, title, fatal error, F.A.B., error, login failure, tools, Histo


    1614 posts

    No problem. I thought by deleting the logs, like cache, would reduce my size for loading site.

    Yes, that is correct, and you should do it, But that is not doing it “at your web host end”. In many or maybe even most (I don’t know for sure) cases that is sufficient. But in some cases it will not. Only your web host can help in that case. But try it – delete all your logs and see if it results in a reduction in the size of your database.

    But if you mean by “loading site” the speed at which pages load, then no, the size of the log files will not matter, except when you load the logs page.

    My personal kiwitrees site is