Stuart Silvester

When the Marketplace closes you'll need to obtain any future updates from the author. Many 3rd party authors are (or already have) setting up their own websites to sell their products. With 4.7.13 you'll be able to manually upgrade resources you installed from the Marketplace.
We will be providing a 'proof of purchase' system in the near future but in the meantime authors may ask you for another proof of purchase if you want to obtain updates directly.

Super duper excited about this!
I may break my rule of not using beta releases just to get into this early.

Your theme seems not to be compatible with the IPS version you’re using.

I would suggest solving the problem that's causing the logs to begin with. A 'large' table won't slow things down but a plugin causing something to get logged a lot could.
The table is automatically pruned, you don't need to manually clear it.
You should probably disable the 'MVN; (or similar name) plugin until it's fixed.

We've got an open bug report for this, it will be addressed in a future release.

We've got an open bug report for this, it will be addressed in a future release.

We've got an open bug report for this, it will be addressed in a future release.

We've got an open bug report for this, it will be addressed in a future release.

Luckily we are the experts in seeing usage trends 😉
Trust me. You have no idea how many problematic things we prevented from being published in the Marketplace over the years.
PSA: you might want to use multi-quote when doing many replies 🙂 

All good 🙂 Always best to ask and be incorrect, than not to ask and get caught out. Will close this for you

Ryan and the team have done a fantastic job with these new tools and I'm really keen to see how they help in the current spam wave we're all experiencing.

Spam has always been an ongoing battle for community owners as spammers find new ways to circumvent existing anti-spam practices.
We have seen an uptick in new ways spammers are breaking through existing defense.
As such, we here at Invision Community continue to look at new ways for community managers to combat against spam. For our September release, we have added several new tools that can prevent spammers from registering in the first place and help combat them even if they register successfully.
Let's take a look at these new tools and settings.
Geolocation based registration filtering
Oftentimes, spam attacks can originate using bots and servers from specific regions. Using our existing Geolocation service, we have now added filters that will allow administrators to hold registrations from specific regions for administrator review, or deny the registration entirely.

Using this, administrators whose communities are under a spam attack from a specific region, can temporarily filter registrations from that region. Multiple regions can be defined at once, and each individual region can either be held for administrator review, or denied completely.
Disposable Email Filtering
We have added an extra option to our spam defense system to filter users registering with throwaway disposable emails, which are often used by spammers to bypass email validation.

During Spam Defense checking, we now also check the domain in use for the registration against a frequently maintained list. If the user passes through the normal spam defense checking, but is found to have a disposable email address, then the administrator can define one of the following actions to be taken.
Allow the registration to proceed Allow the registration, but moderate all posts (which an option to remove moderation after a certain amount) Flag the account for administrator review Register the account but immediately ban it Completely deny the registration For both Geolocation and disposable email filtering, the existing Spam Defense Whitelist is always honored ahead of these filters.
Contact Us Email Verification
A common pain point has been the Contact Us page. While the spam does not go to a user facing location, it does still land in the administrators inbox, or other area defined by the sites Contact Us settings.
To help with this, if a visitor who is not logged in attempts to use the Contact Us page, then in addition to the existing CAPTCHA, the administrator can optionally require the person to verify their email address before the message is ever sent. This applies to all Contact Us behaviors, including any added by third party applications.
Cloud Content Analysis
For our Invision Community Cloud customers, we have also added an additional layer of spam prevention after registration.

After a user registers, or if the account has been dormant, then the first few content submissions will be analyzed using a custom developed algorithm within our platform.
The algorithm takes into factor many different elements of the content, and will rank the post between 1 (not spam) and 5 (definitely spam).
The algorithm can be constantly adjusted and improved based on trends without any intervention from the administrator, and without the need to update to new releases of Invision Community.
The administrator can then decide one of the following actions to take based on the score that was received.
Allow the submission Hold the submission for moderator review Deny the submission completely Of course, specific groups can be made exempt from this and not have their content checked at all, which is useful for sites with subscription based registrations which may not want to have this applied to new subscribers, but do want to have new non-subscribers checked.
Spam can quickly become a headache for most community managers, and these new tools will help further combat it at the source. For our enterprise and Invision Community Cloud customers, being able to check for spam when posting is a new tool which will further filter out more of those annoying topics and posts.
We hope these new features give you additional tools in the fight against spam.
The features and changes presented here are available in the following packages:
Geolocation based registration filtering, Disposable Email Filtering, Contact Us Email Verification: Beginner, Creator, Creator Pro, Team, Business, Enterprise, Invision Community Classic (Self Hosted).
Content Analysis: Beginner, Creator, Creator Pro, Team, Business, Enterprise.

View full blog entry

This won't be a problem in .13. There can be a bit of slowness if there's a delay connecting with a back-end service. We've adjusted the timeout so this won't cause big delays.

They say they've retired the test because it's old - https://www.validbot.com/tests/102/safari-pinned-tab-icon.html
Outside of that, we don't currently support SVG for favicons. Not all browsers (mainly Safari) support this.

mask-icon is a Safari specific thing, It was originally for those MacBook Pro's that had the touch bar so they could show a single color icon. I believe Safari may use it for other things.
https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/pinnedTabs/pinnedTabs.html
https://en.wikipedia.org/wiki/Favicon#How_to_use

This should be fixed completely now.

The date format depends on the locale of the language pack you're using. If the date format is wrong, you're most likely using the wrong locale. (en_US vs en_GB for example).

This isn't using proper backticks. You can remove this line

Thanks for your reply! I know some people get all worked up if costs go up even a tiny bit but we really tried to balance this.
All with the eye toward making Classic, self-hosted viable for the future, we:
Took feedback from a private group of clients for month to refine the new terms Lowered the initial purchase price. Include all the apps with the new terms. Gave people the option to stay on old terms if they want. Give you several months of free time when you switch. I am actually very proud of our ability to keep Classic around in a world where people just do not use self-hosted as much anymore. And, again, I thank our private client feedback group for helping us shape this in a way that is beneficial to most clients.

It will show 'guest' next to posts without their display name.

It only happens if you have DEBUG_TEMPLATES enabled (because it bypasses the deprecation suppression in Whoops), but we'll get this fixed

It only happens if you have DEBUG_TEMPLATES enabled (because it bypasses the deprecation suppression in Whoops), but we'll get this fixed

Images typically have sizes hard oded in the post for lazy load purposes so changing the size of the image would make your previously uploaded thumbnails blurry

Yes and no, loading="lazy" cannot work for background-images for example, which is something we use it for currently. We won't be making any changes for this in v4.

Hi Stuart,
Thanks for the time to explain this, really appreciated!
Best regards
Ricardo