David..

Those would be correct. Ensure you run all those in order of course, as it inserts the data to another table, and then drops it. And of course, as mentioned above, back up

@Matt When the tables where all updated from mediumint(8) to bigint(20) for member ids in a past version, the upgrade skipped this step and only new installation used bigint(20) from that point on.
If I recall correctly it was temporarily skipped because it could have caused issues altering big tables (mainly for big sites) in a minor (?) version. It was supposed to be added to the next major version, but it looks like it was never done until now.
That's also when the code I pointed out in the other topic was most likely added:
 

Greetings! I'm really can't see how current design is overloaded with block, buttons etc
 
For example 'Follow' button is just existing here and can take less space in somewhere else


 
And settings just feels like need to be done like blocks not just raw content

 
Actually there is a lot of moment where design seems like really overloaded and should be put into context menu or something like that, and PLEASE rework out staff page! Thank you very much

Since you mentioned the above, I am unsure why those options are not selected. I have not changed any settings there, and they should be made mandatory if it causes issues.
Regardless:
Selecting "Ask the user to provide a display name" still skips the display name requirement when signing up/in via OAuth.
Selecting "Google account name" automatically uses the Google account's name when registering via OAuth so that at least solves the incomplete account problem.
 
The same issue seems to happen with Twitter sign in too.
 
If we make the user enter a display name when creating a new account in the OAuth login, then the display name is never asked for and just gets redirected back to the OAuth site/app.

Happy Hump Day! Sort of… 
I have a bit of news to share with you: this will be my last Hump Day as I am stepping down from Invision Community. 😢 
I am transitioning to a new role at Amazon. I’ll be creating content and engagement solutions for AWS. 
I’d like to take a moment to thank this community for welcoming me with open arms. When I first started my journey as an Invision Community team member, I focused on community advocacy and connecting clients with the team. We quickly realized my, um... exuberance was better suited in marketing and sales. 
Creating content around Invision Community opened my eyes even further to how brilliantly crafted this platform is and the team behind it.
I've also genuinely enjoyed communicating with industry professionals every day who showed interest in adding a community component to their business.
So many incredible Achievements (😏) happened along the way; I’m grateful I was a part of Invision Community’s success as we blazed through the 20-year anniversary. 🎉 
Now, you won’t be rid of me entirely. My own community, BreatheHeavy, will still remain on the Invision Community platform. I look forward to staying connected with all of you here!
Thank you for engaging and interacting with me these last few years. 
Please feel free to PM me here if you have any feedback, questions or well wishes. 😃 
I want to give a special thanks to @Charles for being my mentor and seeing potential in me (even when I didn't). 
And before I go, here’s a list of updates and changes made to the platform in the last seven days:
 

Thank you, 🙏 
-Jordan
 

Hello . I have a suggestion. Can popular Wallet service wise be added to as A Payment Gateway in Commerce app ? From which the member can pay directly into the Wise business account. If it does, it will be a pretty good addition. Because it is a good service that is fast becoming popular.

Sliding into your DMs..

It’s fine, I thought the same too.
I think it was doable before but now it seems to no longer be the case.

@All Astronauts Can we also add the features from this plugin? 
 
And of course the old online indicator plugins too.
https://invisioncommunity.com/files/file/7853-online-indicator/

Changing the future publish date on an already posted topic does not work. It basically just messes up the topic. Worse part is you cannot change it back apparently either without going through a database backup.
I don’t see why setting a future publish date when editing an already posted topic is enabled.

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

Hello,
The subscription system is a strong point of IPB and subscribers are often the pillar of a community.
Unfortunately, unlike products, it is not possible to display them in the registration form, unlike products, it is only possible to "force" the purchase during the registration.
Is it possible to propose an optional subscription in the registration form? 
Sincerely,
Kims

As you may have noticed, we've been doing a lot of work to prepare Invision Community to use PHP8 as the minimum version.
If you are an Invision Community Cloud client, then you do not need to worry about any of this, and can happily click out of this topic.
For those who host Invision Community on their own servers, then please read on.
PHP7 is now end of life and from November, PHP will no longer offer security updates. PHP8 is a major update which brings many changes including how errors are either logged and means that what was a harmless notice or log entry is now a fatal error which Invision Community cannot capture.
We have introduced the application and plugin scanner to ensure that your site is not "bricked" (unrecoverable from a fatal error) when you upgrade to PHP8 although you currently have the option to re-enable any disabled applications or plugins.
From the November 2022 release, we will require PHP8.0 as the minimum version. If you are currently using PHP7 then you must contact your host and plan your PHP8 upgrade to ensure compatibility with Invision Community from November onwards.

We are rolling out dismissible AdminCP banners to those who are currently on PHP7.
If you are unsure what version of PHP your server is running, simply log into your Admin CP then navigate to System > Get Support and check out the PHP version block.


The November release of Invision Community will also mean that you are no longer able to re-enable plugins the application scanner disables. We continue to work on this tool to refine its error checking and logging verbosity.
If you have any questions, please let me know below.
 

Page speed aside, there was really no need to remove the core CSS from the templates. I agree that most users do not need it so they would of course simply ignore it; but the ones that do need it had the option to view, understand, learn and modify if they wanted to.
CSS is basically harmless and any issue that may come up we could just restore the file to the original version so this shouldn't strain IPS support.
Basically: us self-hosters are already getting hammered with the cloud only features. There's no need to remove features too now.

Please be advised I have asked a dev to come and confirm that auto-renewal is not possible via Google/Apple pay. Someone will be with you as soon as they can.

Page speed aside, there was really no need to remove the core CSS from the templates. I agree that most users do not need it so they would of course simply ignore it; but the ones that do need it had the option to view, understand, learn and modify if they wanted to.
CSS is basically harmless and any issue that may come up we could just restore the file to the original version so this shouldn't strain IPS support.
Basically: us self-hosters are already getting hammered with the cloud only features. There's no need to remove features too now.

Here is my problem with what was done... You also removed the "Classifieds" css from the css tab which is not a core css to my knowledge and I need to add css to that file and now I can't!

Hey
Is a mass cleanup possible through your app? I need to remove all pm from all members.

Hi Steve!
Don't worry, coincidentally Approval Queue UI updates are currently in the works and hopefully will be included in one of the next 4.7 releases! Among other enhancements, exposing the reason content is held for approval is on the list so stay tuned.
Thanks!

I’m sure they do; but that’s when IPS can simply have an automated reply at the ready or even a tutorial link to resolve. So really it shouldn’t strain support at all and increase overall user satisfaction even though it is a trivial issue.
Designer mode is recommended to use on a test install. While that may work, it is an extra step which realistically feels like only expert theme designers use.
4.7.0 did introduce an easier way of adding CSS which is great for newbies, but again, I don’t see why there was a need to remove the intermediate option.
It was a very convenient way of playing around with (a copy of) your theme.

Page speed aside, there was really no need to remove the core CSS from the templates. I agree that most users do not need it so they would of course simply ignore it; but the ones that do need it had the option to view, understand, learn and modify if they wanted to.
CSS is basically harmless and any issue that may come up we could just restore the file to the original version so this shouldn't strain IPS support.
Basically: us self-hosters are already getting hammered with the cloud only features. There's no need to remove features too now.

I’m sure they do; but that’s when IPS can simply have an automated reply at the ready or even a tutorial link to resolve. So really it shouldn’t strain support at all and increase overall user satisfaction even though it is a trivial issue.
Designer mode is recommended to use on a test install. While that may work, it is an extra step which realistically feels like only expert theme designers use.
4.7.0 did introduce an easier way of adding CSS which is great for newbies, but again, I don’t see why there was a need to remove the intermediate option.
It was a very convenient way of playing around with (a copy of) your theme.

Page speed aside, there was really no need to remove the core CSS from the templates. I agree that most users do not need it so they would of course simply ignore it; but the ones that do need it had the option to view, understand, learn and modify if they wanted to.
CSS is basically harmless and any issue that may come up we could just restore the file to the original version so this shouldn't strain IPS support.
Basically: us self-hosters are already getting hammered with the cloud only features. There's no need to remove features too now.

!! Instead of adding extra features IPS need first have to clean up the CSS and JS code, which in many places is 60-70% not used at all and is unnecessarily loaded anyway to slowing down our forums.
*
Adding an option to join solutions? I realised that some of the members adding “almost” solutions to the topic and the another member adds the rest of it or at least extra information. I don’t want to be this person who on the end making an answer with two combined posts and taking away thehappiness and point(most solved etc) from them. 
As well, It will be nice to add an option to sendreactions in the bulk(admin only?) in certain topics(maybe can be optionally enabled in certain sub-forums) example…In https://xbox-vibes.com/topic/2284-question-of-the-weekpytanie-tygodnia-36/#comment-5982 , competitions/games all the answers are liked by me and sometimes I’d like just to pop in and award all the members who’s taking a part. 

Page speed aside, there was really no need to remove the core CSS from the templates. I agree that most users do not need it so they would of course simply ignore it; but the ones that do need it had the option to view, understand, learn and modify if they wanted to.
CSS is basically harmless and any issue that may come up we could just restore the file to the original version so this shouldn't strain IPS support.
Basically: us self-hosters are already getting hammered with the cloud only features. There's no need to remove features too now.