The latest versions of CiviCRM run fine with PHP 7.2. However, a) this has only been true a few months, b) Drupal 7 has only very recently become 7.2-compatible, c) most major Linux distributions don't ship with 7.2 by default. I'd say those three factors account for few sites running it.
Note that as of CiviCRM 5.8.0, known PHP 7.2 import issues have ...
PHP 7 is not supported yet - see CRM-17789
Also: this and this
Update (Aug 2017): The information above was correct when it was written. Things have moved on and PHP 7.0 is supported from 4.7.12 onwards. Earlier versions of 4.7 don't run on PHP 7.0 and nor does any released version of 4.6. There are discussions about adding this to 4.6 - see the same ...
This kind of question is hard to answer for an open source project like CiviCRM :-) There is no 'owner' of the product that can tell you this. Nor is there a group of paid developers that will be able to continue supporting this. Considering that I think it is an impossible question to answer, and the wrong one to ask at this point in time. It would have to ...
When PHP 5.6 reaches it end of life. It means basicly that no further updates are coming from the official php group. But it means you can still keep php 5.6 on your server it does not stop from working.
From api explorer the results are retrieved using rest api where check_permissions is always set to TRUE by default even though its been explicitly set via api params.
If you have check_permissions set to TRUE than api returns only those fields which are defined for the the entity. In your case the fields would be
civicrm_api('Contribution', 'getfields', ['...
It's on your php.ini config file. where it it depends on your OS, in ubuntu/debian it's under /etc/php5 and you have cli and fpm, check that the cli version enables the extension simplexml
FYI, CiviCRM is not yet super tested with php7 (was classified "experimental" two months ago
Not yet officially. If you want to track progress you can subscribe to the ticket at https://lab.civicrm.org/dev/core/issues/1496 and its subtickets.
If you find some issue feel free to report it in a ticket there.
The money_format issue might be something you could look at. If you're testing I'd look closely at how money amounts are formatted on the ...
Does your VPS let you choose the version of PHP? If so, downgrade the version of PHP, upgrade CiviCRM, reset the PHP version.
Alternatively you could copy your installation to another server with older PHP, upgrade CiviCRM there and then transfer back to your VPS.
Since you have attempted an upgrade your system may be in a partially upgraded state. You ...
It sounds like you're running PHP 7.2 or greater with a version of CiviCRM that doesn't support PHP 7.2+. If you edit your question to include your CiviCRM version, that could help folks troubleshoot. However, it sounds like you may need to upgrade your CiviCRM to a version that supports 7.2.
MySQL 8 isn't officially supported yet. This particular problem should be fixed in 5.23 though since it's the word "groups" that mysql 8 doesn't like - see https://lab.civicrm.org/dev/core/issues/1143 and the more general https://lab.civicrm.org/dev/core/issues/392
It's likely that you've added (or removed) the php-crypt library in your PHP upgrade process. This would cause your password to be encrypted in an incompatible method. Re-enter your credentials or match your php-crypt to what it was previously.
You have two options for troubleshooting:
Debug and backtrace info should also be in your CiviCRM logs, stored in the ConfigAndLog directory.
You can enable debug and backtrace by adding these three lines to civicrm.settings.php:
$civicrm_setting['Developer Preferences']['debug_enabled'] = TRUE;