Bug #32445
closed
Problem saving in 4.6.1, not in 4.6.0
0%
Description
During install wizard, this error occurs when trying to install system extensions. The same message appears sometimes when saving a TS template.
Fatal error: require(): Failed opening required '/PATH/web/typo3/sysext/em/classes/settings/class.tx_em_settings.php' (include_path='.:/usr/share/php5:/usr/share/php:/home/sites/general/ZendFramework191minimal/library:/PATH/typo3/contrib/pear/') in /PATH/t3lib/class.t3lib_div.php on line 5140
This does not happen with 4.6.0.
The class is in place in 4.6.1, with sufficient permissions (tried a few permission variations).
PHP is 5.3.5.
Updated by Vincent Mans over 12 years ago
Hm... now it happened in 4.6.0 too... perhaps it's not a bug but something on the server. It was an upgrade from 4.5.7, the original install in this case was a low 4.5.x.
When saving a TS template, the message appears. But the TS template is saved.
Updated by Vincent Mans over 12 years ago
Additional findings:
It occurs irregularly, and for example also when going to the page content module. A few times refreshing the backend page solves the issue.
Other info:
- it happens in Chrome, I didn't reproduce it in other browsers yet since it occurs irregularly
- it's a website on a subdomain (sub.domain.tld)
Updated by Vincent Mans about 11 years ago
- Target version set to 4.7.8
Version 4.7.7 I have the same problem.
In /typo3temp/Cache/Code/cache_phpcode a file is created, and within there is a link stored that has "home/vroot" before "home/sites/[webroot]". This "home/vroot" is only valid within the server.
This is the line (dots added by me):
'tx_em_extensionmanager' => '/home/vroot/home/sites/site.../web/typo3/sysext/em/classes/class.tx_em_extensionmanager.php'
There is no path, not in phpinfo(), with "home/vroot" in front. Is it possible that the EM extension adds a cron command somehow?
Updated by Vincent Mans about 11 years ago
It seems this is solved. One of the admins somehow had copied old RTE settings into the page TSConfig.
These deprecated settings seem to be the reason for our problems.
Updated by Wouter Wolters about 11 years ago
- Status changed from New to Closed
Not a bug, as mentioned by the author.