[#25248] - [4.0] Latest nightly build fails for TYPO3 fatal error
- Closed
- 17 Jun 2019
- Medium
- Build: staging
- # 25248
Steps to reproduce the issue
Install the latest nightly build
Expected result
Just works as previous ones
Actual result
Fatal error
System information (as much as possible)
This code in the bootstrap.php and cms.php causes the error, the TYPO3 package is not included at all
// Suppress phar stream wrapper for non .phar files
$behavior = new \TYPO3\PharStreamWrapper\Behavior;
\TYPO3\PharStreamWrapper\Manager::initialize(
$behavior->withAssertion(new \TYPO3\PharStreamWrapper\Interceptor\PharExtensionInterceptor)
);
if (in_array('phar', stream_get_wrappers()))
{
stream_wrapper_unregister('phar');
stream_wrapper_register('phar', 'TYPO3\\PharStreamWrapper\\PharStreamWrapper');
}
| Labels |
Added:
?
|
||
| Labels |
Added:
J4 Issue
|
||
do a composer update - that fixed it for me
Tested Nightly build. It should not happen with a Nightly build as one does not have to use composer in this case.
Indeed. Just now i have not composer to use.
Informed Maintainers of this issue.
Thanks JM
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-06-17 08:18:13 |
| Closed_By | ⇒ | franz-wohlkoenig |
| Status | Closed | ⇒ | New |
| Closed_Date | 2019-06-17 08:18:13 | ⇒ | |
| Closed_By | franz-wohlkoenig | ⇒ |
@franz-wohlkoenig
Why closing? This is a real issue. Re-opening.
thought its a Composer-issue.
Running composer update fixes the issue. The missing Typo3 library in the nightly build is correctly installed.
This is my bad. In the conflict fixing somehow the typo 3 package ended up in the dev dependencies section (which doesn’t ship in the production & nightly builds). I probably need to regenerate the lock file. But I’m not going to be able to today as I’m seeing family and heading back home in London. If anyone wants to pick it up. Just delete the lock file and run composer install and commit the new one. We’ll probably update some packages on the way but we’re still in active development so it’s no big deal
| Status | New | ⇒ | Discussion |
| Status | Discussion | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-06-17 17:54:25 |
| Closed_By | ⇒ | mbabker | |
| Rel_Number | 0 | ⇒ | 25251 |
| Relation Type | ⇒ | Related to | |
| Labels | |||
| Build | staging | ⇒ | 4.0-dev |
| Status | Fixed in Code Base | ⇒ | Closed |
| Closed_By | mbabker | ⇒ | joomla-cms-bot |
| Rel_Number | 25251 | ⇒ | 0 |
| Relation Type | Related to | ⇒ | |
| Labels | |||
| Build | 4.0-dev | ⇒ | staging |
Set to "closed" on behalf of @mbabker by The JTracker Application at issues.joomla.org/joomla-cms/25248
Nightlies are being rebuilt with #25251 merged right now, updated package will be on the server within 2-3 minutes of this post. Note #25252 is included which bumps PHP minimum requirement to 7.2.
Closing.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/25248.
Did not test Nightly build, but got the same error after the 3.9.3 and 3.9.4 merges into 4.0 in my localhost instance clean install.
I solved it by using composer update and accepting to discard changes as I got this in Terminal