1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

XF 1.4 Don't prune admin.php?logs/spam-trigger ?

Discussion in 'XenForo Questions and Support' started by Marcus, Feb 18, 2015.

  1. Marcus

    Marcus Well-Known Member

    How could I stop admin.php?logs/spam-trigger to prune content over 30 days? Thanks.
     
  2. Chris D

    Chris D XenForo Developer Staff Member

    It's not a custom option, it's defined as 30 days in the code.

    XenForo_Model_SpamPrevention line 774:
    PHP:
    $cutOff XenForo_Application::$time 30 86400;
     
    Marcus likes this.
  3. Marcus

    Marcus Well-Known Member

    Perfect, thanks so much for showing me where this behavior is taken place and what has to be changed.
     
  4. Xon

    Xon Well-Known Member

    Hmm. This is annoyingly short.

    I'll be uploading an addon to provide some configurables for this by the end of the week.
     
    Isil`Zha likes this.
  5. Mike

    Mike XenForo Developer Staff Member

    The purpose of the log is to allow you to check whether your spam rules are hitting what you want and not hitting what you don't. I'm not sure I see the point of older information.
     
  6. Xon

    Xon Well-Known Member

    The user registration record can be easily extended by 3rd party addons, and often contains useful information such as suggesting the users signed up with a VPN or proxy service. We don't want to have to review 10-30 successful registrations a day, so will often only notice after they run into issues with the forum rules which can be weeks to months after the initial registration.

    At the same time, we don't really care about rejected user registrations nearly as much as being able to check successful registrations after the fact.
     
  7. Marcus

    Marcus Well-Known Member

    Actually the log is great for also looking how much "went into the moderation queue". You could build up statistics of directly published content and content that needed moderation before it was published. Content that was created but never published at all because of spam moderation (either disapproved by manual action or it was directly rejected as it is with the conversations).

    You can also find out which users permanently trigger the spam filter that you would never find out either in public areas like forums or user profile messages or private areas like conversations where a user can trigger indefinitely spam keywords which he then changes to get his message through.
     
    Xon likes this.

Share This Page