Jump to content

BobSperanza

Friends
  • Posts

    29
  • Joined

  • Last visited

Reputation Activity

  1. Like
    BobSperanza got a reaction from AlexJ in New one-year, hard-coded limit to blocks in 4.4.2   
    Thank you for this! I hope this is not having any side effects.
     
    Honestly, this is really the worst feature they could have added. We all have threads opened more than one year ago and still active today, or do they think we all have forums with threads active just for a few days ? 🧐 Hopefully this will be fixed in the next release.
     
  2. Like
    BobSperanza got a reaction from Gabriel Torres in New one-year, hard-coded limit to blocks in 4.4.2   
    Thank you for this! I hope this is not having any side effects.
     
    Honestly, this is really the worst feature they could have added. We all have threads opened more than one year ago and still active today, or do they think we all have forums with threads active just for a few days ? 🧐 Hopefully this will be fixed in the next release.
     
  3. Like
    BobSperanza reacted to Gabriel Torres in New one-year, hard-coded limit to blocks in 4.4.2   
    Here it is how I fixed this:
    \system\Content\Widget.php
    /* Limit to days */ if ( isset( $this->configuration['widget_feed_restrict_days'] ) and $this->configuration['widget_feed_restrict_days'] > 0 and $this->configuration['widget_feed_restrict_days'] <= 365 ) { $where[] = array( $class::$databaseTable . '.' . $class::$databasePrefix . $class::$databaseColumnMap['date'] . '>?', \IPS\DateTime::create()->sub( new \DateInterval( 'P' . $this->configuration['widget_feed_restrict_days'] . 'D' ) )->getTimestamp() ); } else { $where[] = array( $class::$databaseTable . '.' . $class::$databasePrefix . $class::$databaseColumnMap['date'] . '>?', \IPS\DateTime::create()->sub( new \DateInterval( 'P1Y' ) )->getTimestamp() ); } Simply remove the "else" statement:
    /* Limit to days */ if ( isset( $this->configuration['widget_feed_restrict_days'] ) and $this->configuration['widget_feed_restrict_days'] > 0 and $this->configuration['widget_feed_restrict_days'] <= 365 ) { $where[] = array( $class::$databaseTable . '.' . $class::$databasePrefix . $class::$databaseColumnMap['date'] . '>?', \IPS\DateTime::create()->sub( new \DateInterval( 'P' . $this->configuration['widget_feed_restrict_days'] . 'D' ) )->getTimestamp() ); }  
  4. Like
    BobSperanza reacted to SoloInter in New one-year, hard-coded limit to blocks in 4.4.2   
    I wrote to the support yesterday, we exchanged more than 20 messages where he asks me to disable the cache, to put the language by default, the default theme, to do different manipulation to ultimately say "pay attention at the limit of one year ".
    What a waste of time and energy for that. Change an item like this without warning, not be able to identify the problem because even at IPS it is not obviously obvious.
    Result, since this update, the number of messages is in free fall, the topics are no longer commented, it's really a change that smells faeces. I'm so angry.
×
×
  • Create New...