aia

It's quite a bad approach and should never be used in any reputable software. Unwanted styles/tags should always be stripped immediately when text is pasted into the editor, long before the message is sent to the database, not on the template side as it happens in this example. This code is a temporary and ineffective workaround, not a solution.

Both AVIF and HEIC have been supported in GD and ImageMagick for quite some time now.

It is highly unlikely to happen due to the licensing issues surrounding HEIC, and also due to the existence of a comparable or superior free and open-source alternative: AVIF. Therefore, the best way to handle HEIC files is to: Add AVIF support to Invision Community (embedding and quality settings). AVIF is supported by all current browsers and is currently the best format in terms of compression/quality. Convert all uploaded HEIC files to a format selected from the uploader options (AVIF, WEBP, JPEG) in Admin Control Panel, with AVIF as the default choice.

Restricting registration by location is the worst thing you can think of. I say this as someone who travels frequently and is often faced with such ill-conceived restrictions. This causes many more problems for ordinary users than for spammers. There are many other more suitable methods to protect against spam (Cloudflare, for example).

@SeNioR- check the value of this setting in Cloudflare:

The last four don't seem so impossible 😉

How many years ago, could you remind me please?

Imagine if clients could make pull/merge requests with such fixes directly to the IPS repository, without wasting time posting it on the forums, waiting for the manual work of the IPS developers, etc... A lot of little but useful fixes/improvements could be implemented and shipped in hours rather than years (as it now, at best). Oh dreams.

No. Everything needed for this can be done in PWA.

Why and How: https://web.dev/aspect-ratio/#example-preventing-layout-shift MDN Docs: https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio Works everywhere: https://caniuse.com/?search=aspect-ratio

This topic is not about that. This topic is about defaults (of editor's link insertion tool) that are more secure and relevant to current and future times. And not all sites use HSTS, btw. And most of them never will.

Wrong. It is not related to HSTS or the browser at all. IPS's editor forces HTTP protocol if a protocol is not specified. Just try to do exactly what is shown on the screenshot and see the resulting HTML. Result: koreanrandom.com (http://koreanrandom.com)

If you insert a link without protocol, it will appear with HTTP in the editor. In 2022 (even in 2015, to be honest), it would be better to use HTTPS as the default protocol. Those who need HTTP must define it explicitly. Example: Result: example.com JFYI: according to google, almost all websites are using HTTPS: https://transparencyreport.google.com/https/overview So forcing the HTTP protocol where there is no need is harmful.

And search-filter (see datalist / js example).

+1 😢

There are other use cases where this feature can be useful. Not just for resetting "old" passwords. Sometimes it can be useful to reset a user's password if it has been leaked and the user used the same password on your site as he did on the source of the leak.

Then you might have a "Mark All as Read" button ¯\_(ツ)_/¯

Yes, the current behavior of the notification reading status is extremely inconvenient. This problem has plagued users for many years. There are a lot of topics about this in the feedback section, and it has been discussed for years.

Oh man... There are a million other ways to find out your IPS version without that number you're talking about.

It sounds like a bug that should be reported to IPS, because if it is, it has consequences for the GDPR.

It's already there and enabled by default. Works exactly the same as with forum posts.

Cool gif, I'll save it for the moment when IPS will officially support the dark theme for the frontend 😉

From my experience, I would recommend a tree view because a flat list would be unreadable with long names. I implemented it myself a long time ago for one of my websites (though not on IPS), and the tree view was much more practical.

Also, a very annoying thing about this dropdown menu is the lack of a search (filter). When you have a bunch of categories in it, it's almost impossible to use it at all. IMHO, all these dropdowns in IPS should have a search (filter) function.

Translation APIs for multilingual communities.