Loading...
 
Skip to main content

Features / Usability

Forum List Topic List

 
Thread actions
Print this page
  • Print all pages

    • Admin_Forums - adding additional prune_values

    Posted by EmmArrBee

    I like the idea of being able to keep a forum fresh by automatically pruning the older items. The current drop down list offers eight options ranging from 1 to 90 days.

    I'd like to be a little less aggressive and use larger values, say 122, 183 & 366 days (4, 6 & 12 months). In LTS v6.7 I see the array of $prune-values in tiki-admin_forums.php

    1. Can I just add the new values to the end of the existing list in tiki-admin_forums.php?
    2. I note the value is multiplied by 60 * 60 * 24 to convert it to seconds, so is there a maximum value I need to be aware of?
    3. Where is this value stored and are there any back end processes which will perform the deletion that I need to worry about??


    All guidance would be most welcomed,

    Thanks

    Martin

    Reads: 1726
    Posted by Torsten Fabricius

    Not sure, but I think the best would be to do a dump, make a test upgrade to the next LTS (9.2) and try it there.

    After that you could report issues or success in the devlist and maybe you'd like to make it an optional preference to use different custom values (for that in future it is not necessary to hack in the code).

    I cannot tell ya, if it works, but you should try it.

    Additionally you could check the revisions of the related php file and thus find out who coded / added stuff and ask these guys.

    Do you know, how to find out revisions with svn?

    --T

    Posted by EmmArrBee

    Torsten,

    Thanks for taking the time to respond. Given 6.7 is a LTS version for a while longer yet, we were hoping to stick with it for now.

    I have no idea how to get the info you are talking about from svn.

    Experimenting could be a bit of a challenge as well for us as we don't have spare server instances and a full test would entail rolling the clock forwards to check the expiry code works as designed with bigger intervals, I guess.

    So some developer input would be really, really helpful in understanding if this is possible/makes sense.

    Thanks again,

    Martin