Marc

If that subscription moves to the premium group C, then they would move to that group during the trial  period also
They will indeed remain in that group
The group change action occurs upon point of having that subscription, whether they are on trial or not. Trial has exactly the same benefits as when they begin to pay
If they do not pay for the subscription after their trial period, they will revert to their previous group once it expires. 
If they were already a member, it would revert to their previous group. As you are essentially registering in order to purchase the item, they would not have been a guest, their last state will have been whatever your first members group is on registration (by default thats 'members')

That could actually indicate your mysql instance is in read only mode

There is no elasticsearch on the cloud based platform, so no values I can give you to enter there. There will be changes to the way in which search works internally on cloud at points in the future, on some levels, but that isnt there at present

In group 32 (heavenly)  you have placed html markup for the group that was very broken. I have now removed that for you, and things should be showing properly again. 

There is no way in which to force them for older items at present unfortunately. You could maybe optimise the actual files on disk, just as a thought on how you can speed up the load there. Of course make sure you back that up completely.

We do not accept that payment method here at the present time.
 

Mail is not send for items generated as the result of rebuilding achievements

You would indeed require a classic license in order to download locally for development. 

You would need to check your rules there. For example
47509 - Has no content count, so doesnt match the content >10 rule 47508 - Reputation level 16, so doesnt match the reputation count > 25 rule 47506 - Post count of 1, so doesnt match the content> 10 rule  

Ah,  these are entry categories you are looking at, rather than blog categories. You would click "Edit blog" then you will see entry categories as a tab, where you can manage these.

It looks like you may have items on your site that are not compatible with PHP 8. Please try recovery mode, as described here
https://invisioncommunity.com/4guides/welcome/getting-support-r292/

You would need development in order to create your own SSO for this. You can find our developer guides in the following location
If it does have OAuth 2.0 you may be able to use the built in login method for this, if its just allowing people to log in using logins created on that platform. If that is the case, take a look here
SVG is not a type that is allowed by default for logos. If you wish to use a SVG file you would need to manually add that to your theme
 

Actually they are on the bottom of the purchase page before you purchase it. The software requires secure versions of PHP (currently PHP 8), with GD, mbstring, and all default PHP extentions, along with mySQL.

Have generated a new invoice for you on the links directory only 🙂 

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.
 

That would be the  correct thing to do. So your file would be 
<?php \define( 'CP_DIRECTORY', 'nameOfAdminDirectory' );  

Take a look at the whitelist section in this guide, and ensure you whitelist yourself if you are testing registrations
 

These are items from "Our picks" so you can manage these by selecting your name, and selecting "Manage promoted content"

This issue has been resolved in our recently released 4.7.9 version. Please upgrade if you are seeing this issue, and let us know if you see any further issues.

This issue has been resolved in our recently released 4.7.9 version. Please upgrade if you are seeing this issue, and let us know if you see any further issues.

This issue has been resolved in our recently released 4.7.9 version. Please upgrade if you are seeing this issue, and let us know if you see any further issues.

This issue has been resolved in our recently released 4.7.9 version. Please upgrade if you are seeing this issue, and let us know if you see any further issues.

This issue has been resolved in our recently released 4.7.9 version. Please upgrade if you are seeing this issue, and let us know if you see any further issues.

This issue has been resolved in our recently released 4.7.9 version. Please upgrade if you are seeing this issue, and let us know if you see any further issues.

This issue has been resolved in our recently released 4.7.9 version. Please upgrade if you are seeing this issue, and let us know if you see any further issues.