Daniel F

I think it’s covered by 

Quote

Mentions & My Content

These notifications will be sent whenever someone mentions you or interacts with content you have posted.

15 hours ago, Hisashi said:

Need clear cache.

Do you mean the client or the admin?
If the admin would need to clear his cache, it sounds like a bug on our side.

Do you have any 3rd party applications or plugins dealing with content moderation? If not, please submit a ticket and we'll take a look.

5 minutes ago, FZ said:

How was this a bug? It worked perfectly for years

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!

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!

OK... short long story if anybody else runs into this...
If you don't have the Pages App:

1. check your core_widget_areas database table

IF you're using IP.Pages:

1. check your core_widget_areas database table
2. check your cms_page_widget_database areas
3. check your blocks ( ACP => Pages => Blocks ) and the cms_blocks database table.

15 minutes ago, CoffeeCake said:

We don't have downloads, but could it be a task that runs on a schedule?

Nah, it's a widget ( IPS\downloads\widgets\_topDownloads ) but I have already helped him to locate it.
It's hopefully resolved now.

Were you able to resolve this? If not, have you submitted a ticket?

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.

We have fixed a bug in 4.6 which resulted in duplicate purchases, but the fix isn't retroactive. 

Quote

- Fixed race-condition potentially causing duplicate purchase records or transactions. 

Check your cms_page_widget_areas and core_widget_areas database tables, which should give you a hint where it's being used.

You can always report the file and ask to delete the pending version.

Are you using multiple languages?

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.

6 hours ago, Afrodude said:

Yes table prefix. This is what causing the issue, and I have already reported it as I mentioned above. Hopefully IPS fixing this issue soon.  

Yes, the SQL Toolbox bug was fixed for an upcoming release  and as Stu said, this isn’t related to Redis at all. 

19 hours ago, The Old Man said:

Here's something to check... One of my sites, actually the first I upgraded to 4.6 seems to lost all of the privacy, terms, guidelines and cookie policies. They are all empty! 🤮

Could you pls submit a ticket so that we can take a look at this 

8 minutes ago, DawPi said:

So it should be ported to an application with own Notification class, right?

yes pls 🙂

40 minutes ago, Arcade King said:

Hopefully this resolves the migration issue from VB5 to IPB4. I did a test migration and nobody could log in with their old passwords from VB5.

No, but I've picked your ticket and we'll get this fixed for you:)

4 minutes ago, flimmer said:

seems to be set based on the total membership base, including those groups that are excluded. Is this correct?

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.

3 hours ago, jackflash said:

We have updated a site today and have noticed that the custom blocks are now missing and there doesn't see an option to creating them again?  I have checked the 'Manage Blocks' tab on the front page of the site and it isn't there.  Has it been moved?

Could you please submit a ticket so that we can take a look at this 

Thanks.

It's always better to submit a ticket so that we're really aware of any issues. 

8 minutes ago, Jonny Pelter said:

Changing followApp to follow_app didn't fix the issue.

Look at my reply again;)

Quote

The fix is to change Request::I()->follow_app to Request::I()->followApp ! 

Yes the endpoint is correct.

The fix is to change Request::I()->follow_app to Request::I()->followApp !