opentype

I have that option for years through a third-party solution. Get ready to be insulted. 😉 People who leave a community in anger (e.g. after moderator actions) will love the opportunity vent their anger one last time, blaming and insulting you. I can’t remember a single time a text-based option to give reasons to delete an account was actually useful. If anything, I would suggest a checkbox list with admin-defined options. 

Yeah, that should be a stock option. Not just Gallery, but pretty much any content type could be available as custom field in a Pages database. 

Kind of. You can create a new page with Pages and then add the Activity Stream widget on it. It doesn’t allow you to chose an existing stream, but there are some settings to create a custom stream. 
You can also link a custom stream as “home” link from the menu, but that wouldn’t automatically picked up from other places like the logo. I am actually using that on one of my sites and I customized the logo template to link to “discover/6/”

Users would need to use the Forgot Password function to set a password and would need to know the email address they used with the linked login method. So you could or should explain that somewhere and inform your users before making the switch. 

Users would need to use the Forgot Password function to set a password and would need to know the email address they used with the linked login method. So you could or should explain that somewhere and inform your users before making the switch. 

Been doing that for quite a while across all my communities. 

Yeah, that should be a stock option. Not just Gallery, but pretty much any content type could be available as custom field in a Pages database. 

Yeah, that should be a stock option. Not just Gallery, but pretty much any content type could be available as custom field in a Pages database. 

I have a custom, not public released app, which allows one to cross-reference all the content suite wide.
Like show images from a gallery album in the topic or pages database record sidebar or header, link to records or downloads files from a topic (which will show the featured image in the sidebar)
 
It's coded way too limited for my own needs, I may release it for v5 because it's going to require a complete rewrite then.

I think the topic itself doesn’t “know” anything about the Pages connection. That connection is stored in the table of the cms database. So you have to use a manual query to check if the current topic ID is present across any of your cms databases. Might not be a good idea. 

It can be tricky. Many areas expect standard values or you will get cut-off letters (e.g. in the bread-crumb navigation). There is also more than one value because there is the the space between lines and the space between paragraph and dozens of CSS classes that apply in different areas.  
A start would be to override this default value and pick a higher number:
.ipsType_normal.ipsType_richText { line-height: 1.6; } This should have an instant effect on forum posts, articles and so on. 

It depends on the type of quotation mark. 
Those "
are removed. Proper typographic quotation marks 
like those “ ”
are not removed. They are just treated like any other character. 

You could put a WYSIWYG block with instruction on the registration page. 

figured it out - it's not under permissions it's under the content tab of the group under edit. 
screenshot for those that may find this later on.

Yeah, the plugin replaces the topic view header in any case. I need to update that part. 

You need to set the member group permissions on database level. You only turned on comments. You haven’t set who can comment. 

Of course, but so what? Forcing everything into a basic English character set is a thing of the last century and not something we want to add as feature for modern software. Links work perfectly fine with diacritics, either directly or (when in doubt) URL-encoded. The examples shown in the Woltlab screenshot above are rather terrible. They not even convert the characters in a meaningful way, they actually erase the distinct meaning of these characters. A rather bad idea, both for human readers and the processing of search engines and so on. An Ł is not an L just because there are visual similarities. 
What’s wrong with a link like https://cs.wikipedia.org/wiki/České_knížectví ? If it works for a site like Wikipedia, it works for our forums too. 

Of course, but so what? Forcing everything into a basic English character set is a thing of the last century and not something we want to add as feature for modern software. Links work perfectly fine with diacritics, either directly or (when in doubt) URL-encoded. The examples shown in the Woltlab screenshot above are rather terrible. They not even convert the characters in a meaningful way, they actually erase the distinct meaning of these characters. A rather bad idea, both for human readers and the processing of search engines and so on. An Ł is not an L just because there are visual similarities. 
What’s wrong with a link like https://cs.wikipedia.org/wiki/České_knížectví ? If it works for a site like Wikipedia, it works for our forums too. 

The fact that those are all admin/api files is a little suspicious. First thing I would check is what the difference actually is. So instead of overwriting the files, download the existing files and compare them to the IPS version with a file comparison app or online service. Is there an actual difference in the code?

The fact that those are all admin/api files is a little suspicious. First thing I would check is what the difference actually is. So instead of overwriting the files, download the existing files and compare them to the IPS version with a file comparison app or online service. Is there an actual difference in the code?

Because downloading it all is still going to block something else from loading. So by moving all the CSS to be pre-loaded, it's actually going to block things that should and would have downloaded first. Browsers are actually quite good at prioritising these days, so you can do more harm than good by messing with the order and preloading potentially large files that don't actually need to be pre-loaded.
In an ideal world the key CSS (eg the CSS needed to render the visible part of the page) would be pre-loaded or hard coded into the html. Just not all of it. 

Normally, you would delete the topics themselves and then the orphaned attachments would be cleaned up later through background tasks. 
If you just remove the files, then sure, the links to those files will remain. 

Hi Adriano,
can you check compatibility with 4.7.11? It seemed to have stopped working after the IPS cookie changes. 
It’s not possible to go beyond the rules page and actually start a topic. 

Seems to work. 
I still see the cookie bar briefly appearing on every page load as reported here. 

We've just pushed out a patch that should address these issues with appearing to be logged out on first visit.
Please apply it from AdminCP > System > Get Support  - In the 'Invision Community' box, you'll see an optional patch (if applicable to your community).