Charles

The staging site is live as it is attached to your production one so it would go when it got purged. However, you are right, we should have suspended and archived the staging one when the parent live one did. Your old production site data is just archived off until it reaches the auto-purge.
But, either way, I put in a thing and it will all purge today.

Just to provide more information, assuming you are referring to the email address k******er@yahoo.com:
On Saturday, January 13, 2024 1:08:27 PM Yahoo sent us a spam complaint for an email sent to that address. Unfortunately they don't really tell us why/how/who put in the spam complaint.
When we receive a spam complaint, the email is automatically added to our suppression list and we never email that address again.
I went ahead and manually removed your email from our suppression list so it should email again.
Since January, we are now on a new email provider. If we get a spam complaint again, it will tell us a tiny but more information about the complaint but only a bit more. If it does spam complaint again, I can at least share that data with you and you could contact Yahoo.
If you want to go in your AdminCP, email settings, and then do a test email to that address I can check the logs and see what happens.

Yes, that's an option.

Hi! I replied to your email you sent on June 9 on June 11. Please check your junk folder. I will reply again now.

Today would be the last day of access.

For any issues with your cloud services, it is best to email in 🙂
I will send this issue in for you now.

Yes, just email accounts@invisionpower.com and they can take care of that for you.

That is correct, private messages are designed to be totally viewable to anyone who is in them. You can of course limit the number of people in a PM to just 2 to prevent others inviting. 

femvoxcommunity@gmail.com was blocked in our system because when you originally tested it did not exist. I have removed the block.

The old PHP7 cluster is sort of being held together with duct tape 😀
Please try to upgrade as soon as possible.

This is fixed now.

Thank you for reporting your problem and for the detailed information.
We were able to see the behavior you are seeing in our logs and are deploying a fix. It only impacted a few of our network endpoints which is why it was intermittent and kind of hard to track down.

You have support here on the community. If you have any issues feel free to post here and we will reply 🙂 

If you Google the error message, the suggestion is to do:
ALTER TABLE core_themes ROW_FORMAT=DYNAMIC;  

I believe Clubs were purposely excluded from Post Before Register because of the very unique permission sets that can be configured around Clubs.

That looks like you have the visual language editor enabled. Go to language translation settings and disable visual language editing.
Those also look like third party addons there so cannot comment on those.  

I'm afraid we do not have any in-software throttling as we usually assume the email service provider would handle that on their side.

I believe everything should be back to stable now. We found a bug in AWS Aurora that ended up requiring engineers to hot-patch our clusters.