The edit was aimed at fixing saving an empty file. This was indeed a vulnerability in our application. But it wasn't supposed to fix the certificate validation problem. All the same, your problem should be related to the ONLYOFFICE Docs certificate. This can be seen from this log, Drupal cannot connect to ONLYOFFICE Docs Server due to "certificate verify failed":
Hi
k.elizabeth →
,
you must specify the following in your settings.php file:
$settings['reverse_proxy'] = TRUE;
$settings['reverse_proxy_addresses'] = array($_SERVER['REMOTE_ADDR']);
This issue is described here:
https://www.drupal.org/project/metatag/issues/2842049
📌
urls with http instead of https
Needs review
Hi k.elizabeth → , on the ONLYOFFICE document server, are you using a certificate issued by a trusted certificate authority?
apaderno → , thank you for your comments, we will fix this. I do not understand one point. To get the logger variable, I use the parent class method L154. I don't understand what is the downside of using this. I even found a similar usage in Drupal source code L71. Can you point out what is the disadvantage of such use?
Hi vishal.kadam → , in source code Drupal are many places where this construction of calling the currentUser() method is used. We ran linters with the DrupalPractice standard and fixed all the places where there were warnings about calls to \Drupal ( https://www.drupal.org/project/onlyoffice/issues/3291611 📌 \Drupal calls should be avoided in classes, use dependency injection instead Fixed ). DrupalPractice allows the use of the \Drupal::currentUser() construct. Why can't we use it here?