bfarber

The error says "resolving timed out" which I would assume means your server is having DNS lookup problems. You will likely need to contact your host about this issue.

The tar/xml files are not retained. They are install files and are used to install the resources, and then are removed.
It is generally against license agreements to purchase a plugin or application and use it on more than one site. If the author of a resource does allow this, then you may be able to reach out to them and ask them for a copy of the resource once you've purchased it to install on another site. If you are speaking of test sites specifically, we have a special -TESTINSTALL key that you can use on your test site which will give you access to your resources purchased for your live site for a test installation.

The tar/xml files are not retained. They are install files and are used to install the resources, and then are removed.
It is generally against license agreements to purchase a plugin or application and use it on more than one site. If the author of a resource does allow this, then you may be able to reach out to them and ask them for a copy of the resource once you've purchased it to install on another site. If you are speaking of test sites specifically, we have a special -TESTINSTALL key that you can use on your test site which will give you access to your resources purchased for your live site for a test installation.

You're missing an automatically created database column used to track parent associations. I'm not sure how that would have happened unless you uninstalled and reinstalled Pages after starting the conversion. We can help you resolve the issue through the support desk, however.

Go to the forum management area in the AdminCP, click the dropdown arrow next to the forum, and choose to Move/Delete Content.

Thanks for the heads up. I've added a note internally to our PHP8 support task.

Theme templates are stored in the database in core_theme_templates.

Thanks for the heads up. I've added a note internally to our PHP8 support task.

Oh no worries - at least it clears up why I wasn't able to find what you were seeing. Thanks for confirming!

I fixed the DateInterval issue.
I can't reproduce or see the first issue however, and my code lines aren't matching up.
What do you have on line 1120?

I'm finding it to be a lot faster locally with IN_DEV enabled actually.
I had to adjust the regex you supplied (it didn't account for typed parameters like function x( $member=NULL, \IPS\Member\Group $group ) ) but it was pretty helpful nevertheless. Thanks! I found a few more similar issues (method_exists() calls on NULL for instance) but nothing you hadn't reported. Let us know if you spot anything else.

On a busy site, a cache time of 1-2 minutes can represent significant savings on database overhead. That seems reasonable.

I'm not confident this is going to be "simple". You can move the table to a remote database and then create a plugin on \IPS\Member to fetch from that remote database, however the bigger problem you'll face is that many, many areas of the software join the members table on to save queries, which wouldn't be possible with the table stored in a remote database. You would probably need to do a project search and change many, many core areas of the software (searching, fetching content items, fetching comments in content items, etc.) to account for the change.
Honestly, your better solution would be to just host your database entirely in Russia if this is a legal requirement.

This is not possible out of the box

When you set up a custom confidential OAuth client, you can choose which scopes are available. Look at the "Scopes" tab.

 
By default, "profile" and "email" are the two valid scopes that are created, but you can adjust and make others.

@kmk I think this sentence only applies to options in ACP when adding a new phrase. There is no such option directly in the widget.
When you editing block go to "Content" tab, on right side you have "Tags" head. Click on Phrases [+].
 

I've added your suggestions to an internal development suggestions list for consideration in an upcoming release.

We support Microsoft Edge, the browser that Microsoft currently supports.
https://en.wikipedia.org/wiki/Internet_Explorer
Internet Explorer stopped receiving material updates in 2016. It no longer works with Microsoft Teams as of Nov 2020, and will not work with Microsoft 365 as of 2021. In other words, Microsoft doesn't even support this browser for their own major web-based products.
Frankly...we can't move forward with technology if we continue to support the past forever and ever. Specifically in this case, we migrated to using CSS variables which is a major major overhaul of our design system allowing for easier theming, more flexibility, better cohesiveness across the entire site and many more features, but is a feature which Internet Explorer doesn't support (because, again, it hasn't received material updates in 4 years).
We don't support any other browsers released 4+ years ago either for the record.

The Spam Defenense system only stops users highly suspected (or known) of spamming from registering. It does not arbitrarily "guess" if a user may be a spammer based on factors such as random usernames that a human might consider.
In this case, I'd use the ban filters to block the email domain "@ahhtee.com" from registering, which is where these registrations seem to be coming from. If these users actually are submitting spam, I'd also report them as spammers through the software so our system can learn, but please note that a "funny looking name" is not actual spamming and I would caution against making judgement calls too early.

We support Microsoft Edge, the browser that Microsoft currently supports.
https://en.wikipedia.org/wiki/Internet_Explorer
Internet Explorer stopped receiving material updates in 2016. It no longer works with Microsoft Teams as of Nov 2020, and will not work with Microsoft 365 as of 2021. In other words, Microsoft doesn't even support this browser for their own major web-based products.
Frankly...we can't move forward with technology if we continue to support the past forever and ever. Specifically in this case, we migrated to using CSS variables which is a major major overhaul of our design system allowing for easier theming, more flexibility, better cohesiveness across the entire site and many more features, but is a feature which Internet Explorer doesn't support (because, again, it hasn't received material updates in 4 years).
We don't support any other browsers released 4+ years ago either for the record.

The Spam Defenense system only stops users highly suspected (or known) of spamming from registering. It does not arbitrarily "guess" if a user may be a spammer based on factors such as random usernames that a human might consider.
In this case, I'd use the ban filters to block the email domain "@ahhtee.com" from registering, which is where these registrations seem to be coming from. If these users actually are submitting spam, I'd also report them as spammers through the software so our system can learn, but please note that a "funny looking name" is not actual spamming and I would caution against making judgement calls too early.

"We have an internal suggestion" means that the idea has been raised and is something we are considering changing in a future release.

Optimizing a server is a huge task and it's hard to give a lot of general "do this" recommendations. Most suggestions are specific to an environment.
For starters, I'd make sure that (1) you don't have things installed and running that you don't need. The less PHP modules, Apache/nginx modules and so on that are executing, the better off you'll be. And (2) make sure your configurations for Apache/nginx, PHP and MySQL are as optimal as can be. There are thousands of tutorials online that can help you determine what the optimal configuration for your environment and level of traffic should be, and I'd start with reviewing some of those. Basic things like ensuring static files are cached can go a long ways.

This is not possible just yet, but it's been raised internally as a suggestion.

Yes, I don't believe that error is related to the patch.