Jump to content

Daniel F

Invision Community Team
  • Posts

    6,565
  • Joined

  • Days Won

    37

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Daniel F

  1. It didn't because of the cache. Let's say the first visitor after the widget cache was truncated has all topics shown as unread.Since he's the first visitor his output will be cached and returned to literally any visitor having the same theme, language and groups and even if these members have no unread topics, the widget would show them as unread!
  2. It's not that we don't care, it's just not reasonable to have such feature in a widget. It's true that it was present in the past, but only because it was a bug.It's not possible to implement such a feature with our widgets and the widget cache!
  3. OK... short long story if anybody else runs into this... If you don't have the Pages App: check your core_widget_areas database table IF you're using IP.Pages: check your core_widget_areas database table check your cms_page_widget_database areas check your blocks ( ACP => Pages => Blocks ) and the cms_blocks database table.
  4. Nah, it's a widget ( IPS\downloads\widgets\_topDownloads ) but I have already helped him to locate it. It's hopefully resolved now.
  5. Were you able to resolve this? If not, have you submitted a ticket?
  6. That's a tricky one. The frequency is stored as a string ( e.g. P0Y0M0DT1H0M0S ) so it's not going to work by the default MySQL sort. I have filled a bug report for this.
  7. We have fixed a bug in 4.6 which resulted in duplicate purchases, but the fix isn't retroactive.
  8. Check your cms_page_widget_areas and core_widget_areas database tables, which should give you a hint where it's being used.
  9. You can always report the file and ask to delete the pending version.
  10. It seems that there's a bug in the way how we build the club menu because I'm indeed able to access the page without being a member in a closed club, it's only not appearing in the menu. I have logged this to our bug tracker.
  11. Yes, the SQL Toolbox bug was fixed for an upcoming release and as Stu said, this isn’t related to Redis at all.
  12. Could you pls submit a ticket so that we can take a look at this
  13. No, but I've picked your ticket and we'll get this fixed for you:)
  14. Correct, it's based on the total members count. I agree, that's a fair point, which I have forwarded to our internal suggestion list.
  15. Could you please submit a ticket so that we can take a look at this
  16. Thanks. It's always better to submit a ticket so that we're really aware of any issues.
  17. Yes the endpoint is correct. The fix is to change Request::I()->follow_app to Request::I()->followApp !
  18. You can disable this in your ACP on the System => Streams page.
  19. Thanks, I have filled a bug report for this. (At a quick glance it seems that there's a typo in the used request variables - followApp vs follow_app )
  20. What do you mean with the second column? If you mean the sidebar, following code should accomplish this: \IPS\Output::i()->sidebar['contextual'] .= \IPS\Theme::i()->getTemplate( 'app1', 'module' )->sidebartemplate( $yourVariables );
  21. There's a core_member_status_updates database table in 4.x BTW, are you sure that you're upgrading from 3.4??? The step in your error indicates you're on IPB 3.2
×
×
  • Create New...