The issue above is not a problem with PHP 8. The problem is that the extra Tickets hasn’t been adapted to work with MODX 3. It didn’t work with PHP 7. PHP 8 probably just shows more warnings/notices.
I’m experiencing issues 2 and 4 as well on multiple sites when upgrades from 2 to MODX 3:
Empty manager tree (menu not opening as well, and renders ‘javascript:;’) and Package manager not loading.
No that doesn’t help sorry. I thought that solution concerned the Package Installer. The Installers are working fine now after updating the extra’s through SiteDash.
But the resource trees on many sites remain blank. Links in the left menu also do not work; they render a ‘Javascript;:’.
[2022-10-18 11:04:04] (ERROR @ /var/www/vhosts/example.com/httpdocs/core/components/sitedashclient/src/System/Status.php : 137) PHP warning: is_file(): open_basedir restriction in effect. File(/proc/meminfo) is not within the allowed path(s): (/var/www/vhosts/example.com/:/tmp/)
[2022-10-18 11:04:04] (ERROR @ /var/www/vhosts/example.com/httpdocs/core/components/sitedashclient/src/System/Status.php : 57) PHP warning: is_file(): open_basedir restriction in effect. File(/proc/stat) is not within the allowed path(s): (/var/www/vhosts/example.com/:/tmp/)
[2022-10-18 11:04:04] (ERROR @ /var/www/vhosts/example.com/httpdocs/core/components/sitedashclient/src/System/Status.php : 73) PHP warning: is_file(): open_basedir restriction in effect. File(/proc/cpuinfo) is not within the allowed path(s): (/var/www/vhosts/example.com/:/tmp/)
[2022-10-18 11:09:03] (ERROR @ /var/www/vhosts/example.com/httpdocs/core/components/sitedashclient/src/System/Status.php : 137) PHP warning: is_file(): open_basedir restriction in effect. File(/proc/meminfo) is not within the allowed path(s): (/var/www/vhosts/example.com/:/tmp/)
[2022-10-18 11:09:03] (ERROR @ /var/www/vhosts/example.com/httpdocs/core/components/sitedashclient/src/System/Status.php : 57) PHP warning: is_file(): open_basedir restriction in effect. File(/proc/stat) is not within the allowed path(s): (/var/www/vhosts/example.com/:/tmp/)
[2022-10-18 11:09:03] (ERROR @ /var/www/vhosts/example.com/httpdocs/core/components/sitedashclient/src/System/Status.php : 73) PHP warning: is_file(): open_basedir restriction in effect. File(/proc/cpuinfo) is not within the allowed path(s): (/var/www/vhosts/example.com/:/tmp/)
I cannot find an extra that is exclusively connected to these sites with a problem.
I disables all packages through the database, but without any effort.
extension_packages is empty in the dabatase (I cannot go into the Settings since the menu’s don’t work).
My guess it’s a Javascript problem: the menu’s are not clickable and there are no sub menu’s. It says ‘Javascript:;’ when you hover your move over them.
Does it work if you go directly to https://yourdomain.com/manager/?a=system/settings&ns=core?
Is it only the manager start page https://yourdomain.com/manager/ that fails?
When you call this connector directly in a new browser tab, what is the response?
manager/?a=system/settings&ns=core renders a blank page (within the Manager).
Don’t know about other pages, because I cannot access them through the menu.
This connector only initializes MODX and then loads some language strings. The fact that this doesn’t work means that an error happens when MODX is initialized. (So it’s not a Javascript problem. Most errors in the browser console are just subsequent errors because the data from this request is missing.)
Do you have access to the PHP error log on your server? Are there any related errors in there? (Note this is not the MODX error log in core/cache/logs.)
How did you disable them? In the database table modx_site_plugins → column “disabled”? Did you clear the cache (folder core/cache/) afterwards?
In MODX 3 code from extras can also be loaded from a bootstrap.php file in core/components/name_of_the_extra/. Maybe try temporarily renaming such files to test if they cause the issue.
I disabled them in the modx_transport_packages table, not modx_site_plugins (yes, cache cleared).
Didn’t work though
This is the PHP error log of site1:
mod_fcgid: stderr: PHP Fatal error: Uncaught Error: Class modConnectorRequest not found in /var/www/vhosts/dezandbloem.nl/httpdocs/core/src/Revolution/modX.php:1514, referer: https://mydomain.com/manager/
mod_fcgid: stderr: PHP Fatal error: Uncaught Error: Class modConnectorRequest not found in /var/www/vhosts/dezandbloem.nl/httpdocs/core/src/Revolution/modX.php:1514, referer: https://mydomain.com/manager/
So this line seems to be the problem:
PHP Fatal error: Uncaught Error: Class modConnectorRequest not found in /var/www/vhosts/yourdomain.com/httpdocs/core/src/Revolution/modX.php:1514
Does the file core/src/Revolution/modConnectorRequest.php exist? Is the content correct?
Is there a system setting modConnectorRequest.class or modRequest.class? If yes, what is the value?
According to your error message, MODX tries to load the class modConnectorRequest. But in MODX 3 the value should be MODX\Revolution\modConnectorRequest (with the namespace MODX\Revolution).
The value gets set in this line:
Either to the value of the system setting modConnectorRequest.class (if it exists) or to MODX\Revolution\modConnectorRequest::class (which is MODX\Revolution\modConnectorRequest).
So if you don’t have a system setting, why is the value wrong?
Does it work if you (temporarily) change the line to a hard-coded value: