Jump to content


Gabriel Torres

  • Content Count

  • Joined

  • Last visited

  • Days Won


Gabriel Torres last won the day on July 21 2014

Gabriel Torres had the most liked content!


About Gabriel Torres

  • Rank
    Community Regular

IPS Marketplace

  • Resources Contributor
    Total file submissions: 2

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Makoto Upgraded from ATP, everything was populated and in the ACP seems to be correctly configured, but the prefixes are not displayed before the topic title at the front-end. Editing the post we can see that the prefix is configured correctly there. Also found a small glitch, see screenshot.
  2. @djpretzel Ryan H. is no longer the maintainer of this app. @Kevin Carwile is the new guy... 😉
  3. @All Astronauts @Xeite It could be another plugin conflicting with this one, I'd suggest disabling all other plugins and leaving only this one and clearing the cache to see what happens.
  4. Existing members. Remember that with the previous version I had to run this manually and took several hours, and for this version you wrote above that the system would do this automatically? That explains it... hehehe I've just launched the task to re-identify these members. Thanks for putting this task in the background now! hehehe
  5. @Makoto 24 hours and the app has automatically identified only one user with disposable email address... 😑
  6. @Kevin Carwile We found a issue with this app and compatibility with the new 4.4.x series, more specifically with the new "post before registering" feature. We have forums that we made prefixes mandatory. However, the topic creation box from the "post before registering" feature doesn't ask for a prefix. This way, new topics by new users created this way end up without a prefix in topics where a prefix is mandatory. Could you take a look into this and also into my previous post above? Thanks!
  7. @Makoto When I click on a username in the Members list, the link redirects to: &app=core&module=members&controller=members&do=edit&id=XXXXX Instead of: &app=core&module=members&controller=members&do=view&id=XXXXXX Which would be more useful for me here! The error I reported is gone. I will wait a couple of days to see if the list was fully populated and let you know! 🙂 Thanks for your outstanding support and adding the features we are requesting! 🙂
  8. @Makoto Trying to enable logging throws an error here. Will PM you. Also, the list of previously detected emails with disposable emails (that task that took hours) is now gone...
  9. @Kevin Carwile Sometimes, the prefix isn't displayed at the parent forum topics list. See screenshots below. https://www.clubedohardware.com.br Example given: https://www.clubedohardware.com.br/forums/forum/25-programação-e-desenvolvimento/ Topic: https://www.clubedohardware.com.br/forums/topic/1362189-visualg-variavel-so-aceita-maiuscula/?do=getNewComment Please advise!
  10. Hi guys! I can confirm that the new patch available as of today solves the issue. Simply click on "Support" inside the ACP to apply it! Many thanks for everybody who joined my topic showing that the problem was not just with me here. Cheers!
  11. 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() ); }
  12. Hello, One of the new features of 4.2.2 is a new hard-coded, one-year limit to blocks in the Pages application. I understand this was done to improve performance, as limiting the amount of data you pull from the database server improves performance. The side effect of this new limitation is that our blocks now don't show all the information we need. For example, we have a block that lists our most popular articles, and with 4.4.2, this block only shows the most popular articles posted in the past 365 days instead of all times. Another example, we have a block that lists our products, and with 4.4.2 this block only shows the products released in the past 365 days instead of all products. My suggestion is to respect the "past year" checkbox that is available when configuring blocks, as now this checkbox is simply ignored. This way I believe you could help users like me who want all data, and users who don't need all data and can limit the scope of the queries to improve performance. I know you probably won't implement that, but I thought it would be interesting to open a topic about this, to see if other website owners have the same needs as us here. Thanks! :) Gabriel.
  13. hehehe I guess this is the #1 request, huh @Makoto ?
  14. Many thanks @opentype and @Adriano Faria! This also explains why several other plugins that we use here were removed from the marketplace, even though they work fine. Cheers.
  15. Does anyone know what happened to this app? @Tom Irons
  • Create New...