13.

By the way, has anyone tested IPS with Open Search instead of Elastic Search? Most likely it should work, and if someone has already checked, please tell us about your experience.

The Details and Summary tags are a modern and correct way to do spoilers. It has many advantages over the IPS implementation of spoilers, including naming, accessibility, semantics and the ability to search hidden text in Chrome-based browsers. MDN docs with demo: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details

What exactly do you mean? Please describe in more detail. I have been using Cloudflare for years and it already works great in my cases.

Unfortunately, there is no such feature, although many clients have been asking for it for many years.

Bump. Reports for user profiles are still missing.

¯\_(ツ)_/¯

Sometimes, as the forum evolves, it becomes necessary to merge categories. It would be great if this feature was available out of the box and worked the same way as when merging topics, i.e. all topics from the merged sections are moved to one selected, and the URL of the old section is redirected to the new one with the HTTP code 301.

What is IndexNow? IndexNow is an easy way for websites owners to instantly inform search engines about latest content changes on their website. In its simplest form, IndexNow is a simple ping so that search engines know that a URL and its content has been added, updated, or deleted, allowing search engines to quickly reflect this change in their search results. Without IndexNow, it can take days to weeks for search engines to discover that the content has changed, as search engines don’t crawl every URL often. With IndexNow, search engines know immediately the "URLs that have changed, helping them prioritize crawl for these URLs and thereby limiting organic crawling to discover new content." IndexNow is offered under the terms of the Attribution-ShareAlike Creative Commons License and has support from Microsoft Bing, Yandex. Documentation FAQ

Have you ever heard about code review before merging? None of those concerns are valid because code review before merging a code from pull requests was invented exactly for this. Obviously, no one is suggesting adding code directly to the repo without the proper review. This is how most of the code in the world is written. Especially the code you already have on your server, from the OS to every little third-party library used in IPS. This is a much easier and faster way for IPS to fix things like this with the help of the community.

This forum section is full of topics about trivial fixes and improvements that are very easy to do. I hope someday IPS will give active clients access to the repository to create pull requests, so that we can fix it ourselves, and we don't have to wait for years for such small things to be fixed (or never fixed).

My vote for OpenSearch.

Yes, make it optional with the ability to upload the custom sound.

It would be better to use the native method everywhere and fallback to the JS-based method only when needed, so the majority of users of modern browsers won't experience problems just because of a minority of technically backward Apple browsers. It's very easy because native lazy loading works perfectly fine when used with JS-based method at the same time.

OpenSearch is the Elasticsearch alternative with open source and Apache 2.0 Licence. https://opensearch.org

When we paste URLs in the editor, some of them are automatically handled as a link, for example: https://www.google.com/ But it does not work if the domain is IDN, e.g.: https://xn--90adahrqfmec.xn--p1ai/ The expected behavior is conversion to link like this: https://гемоглобин.рф But it simply does not work here, even though there is a clear indication of the HTTPS protocol.

@idioteque, explain your problem in more detail.

With my experience of using both WordPress and IPS Community for years, I would choose and recommend WordPress for blogs. And there is no other choice between those two, honestly, IMO. IPS isn't bad for what it was initially created for, i.e., for forums. But not more than that.

Gutenberg

For me, it is not important which editor to use, but how exactly it will be customized by IPS. The main thing I hope for is that IPS won't carry over all the same bugs that they added to the current editor and haven't been fixing for years. Such as the complete inability to delete mentions in mobile Chrome, for example: 1620649541089.mp4 As well as get rid of additional overcomplications, such as replacing existing editor functions. For example, fast and easy URL embedding on clumsy and slow: 👍 👎

.htaccess rule for all xml and json files: <FilesMatch "\.(xml|json)$"> Order Deny,Allow Deny from all </FilesMatch>

It's still not fixed even in 4.6.x 😞 https://invisioncommunity.com/applications/core/data/versions.json https://invisioncommunity.com/applications/core/data/theme.xml

I wonder why image extensions are hardcoded instead of option in ACP? It would be great to have this as an option, so everyone who cares about modern image formats could add them there without any code.

Some time ago, I described how I solved this problem for one of my communities.

Better not just Amazon, but also (at least) FFmpeg.

I also would love to see here an option to display these messages to all users but without mentioning the exact moderator, who performed the action. I.e., groups with permissions will see: %username% changed the title from "ABC" to "123" %username% moved %n% messages to the %topic% While ordinary users will see: Moderator changed the title from "ABC" to "123" Moderator moved %n% messages to the %topic% Where %username% is the username and Moderator is just text.