Hi @rmga,
The warning:
[Wed May 13 13:50:30.116224 2020] [php7:warn] [pid 104169] [client x.x.x:37373] PHP Warning: file_exists(): open_basedir restriction in effect. File(plugins/gateways/README/index.php) is not within the allowed path(s): (/home/omp/:/home/omp/plugins/gateway:/usr/share/php5/:/var/lib/php5/:/tmp/:/:/ompdata) in /home/omp/lib/pkp/classes/plugins/PluginRegistry.inc.php on line 243, referer: https://x.x.x/index.php/press1/management/settings/website
…appears because you seem to have a file called README in plugins/gateways; I’m not sure where this came from but you should be able to remove it to resolve the warning. (This will be ignored without causing a warning in a future release.)
As for this warning:
[Wed May 13 13:50:29.450622 2020] [php7:warn] [pid 104170] [client x.x.x:37372] PHP Warning: DOMDocument::loadXML(): Empty string supplied as input in /home/omp/lib/pkp/classes/plugins/PluginGalleryDAO.inc.php on line 57, referer: https://x.x.x/index.php/press1/management/settings/website
…it explains why the Plugin Gallery is empty. Are there any related warnings/errors appearing above that?
There is not enough information to track down the cause of the warning…
[Thu May 14 08:45:55.944929 2020] [php7:warn] [pid 73900] [client1x.x.x.x9622] PHP Warning: htmlspecialchars() expects parameter 1 to be string, array given in /home/ojs/lib/pkp/lib/vendor/smarty/smarty/libs/plugins/modifier.escape.php on line 39
…but I suspect it is cosmetic. To track it down, you’d probably need to temporary edit lib/pkp/lib/vendor/smarty/smarty/libs/plugins/modifier.escape.php at line 39 to dump a stack trace, which would help indicate the cause of the problem.
Regards,
Alec Smecher
Public Knowledge Project Team