bfarber

Member profiles settings in the ACP:

You didn't see this snippet from our 4.6 changelog from me shhhhh
 

Hey,
we have published the first article of a series about upcoming 4.6 changes.
We took the opportunity for some spring cleaning, so we have removed most of the deprecated methods!
They were all marked as deprecated for a while, so you should already be aware of these methods, but here’s a full list of the methods and the new approaches to make your life easier, so if you haven’t already, now it’s the best time to review your code and make sure that none of these methods is used.
Most of the changes can already be implemented while the 4.5.x lifecycle.
 

Thanks for the support however I can't commit to any specifics as I have no control over the app review process and there are many unknowns in the whole development process. Promising features in a specific timeframe is the quickest way to poorly developed applications 😉

There is no way to force this, no. It's done automatically based on the device that views the site.
https://html.com/attributes/img-srcset/
We specify a 2x density image (what you are referring to as the "HD emoticon") and the user agent/browser will automatically use this if the device has a high density display.

Most likely your core > front > global > mobile* templates are modified and thus are not importing the template that defines the mobile menu properly.

So what you're suggesting is a way for members to create albums of images, from their profile, disconnected from a category within the software. Is that effectively correct?

There is no requirement for Redis to persist data if restarted. Redis is used as a temporary cache. Any data lost does not represent a problem for the community software with a very minor exception not worth worrying about - you have the option to store "topic views" in Redis that are accumulated for a short period of time, and then they are saved to the MySQL database by a task periodically. If data does not persist, you might lose out on some topic views being recorded. This is probably not a concern if you are looking at fine tuning Redis persistance for performance in 99% of cases.

We have fixed here few issues for an upcoming release:) 

You can restart Redis at any time - this should not log users out.

We do not have a planned maintenance release at this time.

Not exactly, however
1) You could register MySQL Triggers directly if you wanted.
2) You could create a hook which hooks in at a low level, e.g. to the active record save() method, or even to the database class directly.
It really depends on what you are after.

If you are using 4.5 and experiencing this issue I'd recommend submitting a ticket.

The JSON+LD structure has been updated for 4.5 to remove the warnings.

What do you mean "topic pages that have been reviewed"? Topics don't support the reviews functionality, or do you mean rated?

Review data used to be valid for Article object types in structured data, but Google has since changed their mind and no longer allows you to include review data for articles. We are looking into this.

Uploads have been redesigned for 4.6 to address this quirk which can happen with longer filenames.

Sure. But that argument could be used for literally hundreds of functions and services that IPS could theoretically build to attract some new audience. Because it works for everything, it doesn’t mean much. 
As Paul already said, there a many many LMS providers already out there, who have worked for years in teams exclusively on this one product—so they are far ahead and will likely always remain ahead for years to come. It makes very little sense that IPS starts from scratch to compete with them through a completely new app, just to maybe get a few new customers in a competitive market, when at the same time, 98% of the current user base don’t have any use for that function. It makes much more sense to stay competitive in the markets they already serve and focus on the apps they already have. (By the way: Chat was already killed. Blogs almost. So as history shows, they are rather narrowing down their app portfolio, not extending it—e.g. just to attract some new people selling trainings.)
I appreciate that some users really really want it (and I would like it too actually as my sites are very education-based), but lets be reasonable about it and not try to convince IPS with rhetorics. Saying it’s really really needed or even “required” doesn’t make it so and IPS doesn’t fall for that anyway. They know their user base in its entirety. 

My community had ~12 at one point and only 3 were used and the rest were at less than 1% 😆. Not saying it's like that for everyone of course. 
On Invision Community, we removed the "sad" and "confused" reactions because they were extremely underutilized. 
Which reminds me, I'd love to see more green +1s 😂 

jQuery is obviously not needed in 2021 - I'd love to do away with it. In reality, we have many thousands of lines of JS and the cost/benefit of rewriting everything for that reason alone isn't really there. Plus, we'd likely end up with a lot of helper methods that are essentially reimplementing some of jQuery's helper methods. We use some of the more advanced jQuery features too, so it wouldn't be as simple as updating .find to .querySelectorAll.
So, the answer is: yes, I agree, but it isn't as simple as saying "let's do that".
Also, in reality, if we were going to take the opportunity to redo our entire frontend codebase, we'd likely move to a reactive framework to build a better frontend, rather than simply rewriting what we have now but without jQuery. This will happen in time - we can't stay with the same code forever - but again it's about finding the right balance.

Uploads have been redesigned for 4.6 to address this quirk which can happen with longer filenames.

I will do a video for you tomorrow. 

Review data used to be valid for Article object types in structured data, but Google has since changed their mind and no longer allows you to include review data for articles. We are looking into this.

AdminCP > System > Settings > Email Settings

 
Make sure the "Log Statistics" setting is off and there won't be any "trackers" in emails. Note that any tracking done with the setting on is anonymized (you can't tell who received what email and so on).

This is probably an incrementing ID, controlled by MySQL.
If so, you can run the following operation on whatever the invoice table is:
ALTER TABLE wherever_invoices_live AUTO_INCREMENT = 999999; Where 999999 is the number you'd like to start from.
Backup everything first. Then back it up again. Just in case.