Stuart Silvester

This issue is specific to where no report notifications have been configured. If you create a notification type, you'll see the UI as detailed in the blog post. You can do this as a work around, even if you do not intend to use the notifications.

I don't recall seeing an addon for it, but it wouldn't be difficult for a developer to implement in v4. We removed Gravatar support about 6 years ago, it wasn't used by that many customers and created privacy concerns since it requires sharing PII (email addresses) with a third party.

The default avatars (profile photos) will be like you see on here, a coloured background with a letter on it. We do not support Gravatar.

Changed Status to Not a bug

Hi, I do not believe that this is a software issue. If you exported and re-imported your database to create the test site, it was most likely exported in a non-UTF8 character set. If your server default character set is not UTF8, you will need to specify it when exporting the database (use utf8mb4 for best results - to retain emoji)

We have released a patch to address this issue. Please go to AdminCP > System > Support and apply the patch from the first/top left box. If you do not see an option to install the patch, you already have the latest release.

We have released a patch to address this issue. Please go to AdminCP > System > Support and apply the patch from the first/top left box. If you do not see an option to install the patch, you already have the latest release.

In fact, opening the full content of the email in the error log, two message IDs appear: Next week, We'll be releasing a patch to address this issue.

You're not using S3 for Theme resources (JS/CSS), they're being served from your main site. Earlier when I visited your site I saw a Cloudflare blocked page, so it may be worth seeing if Cloudflare is periodically blocking requests to those files for some reason.

Right, there were changes (as detailed in the change log). In 4.7.18 this feature didn't work for you because it relied on Trending data that wasn't available for your legacy plan. In 4.7.19 we made some changes so plans without the real-time trending features could still utilize the hot/popular topic badge, this also included adding the setting you're screenshotting to control the time period where the topic is marked HOT if it has trended in the last X minutes. Topics that are less than an hour old or have less than 3 posts are completely excluded. I hope that clears up any confusion!

With Cloud plans it works a little differently. It uses Trending data to determine when something is popular. Trending data uses many more variables than just the number of replies such as the number of reactions, number of views etc.

You can work around this by changing the 'Remove guest details after' setting on the 'content reporting' page to a large value instead of 'never'. We'll fix this in an upcoming release.

Check that you have the setting enabled so customers can generate their own renewals for a product. AdminCP > Commerce > Products > Edit Product > Client Area Settings tab > Allow customer to renew?

Hi, No, it isn't compatible so it won't work.

S3 integration currently only works with S3. There were some 3rd party resources for version 4 to add support for S3 compatible platforms