Empty AdditionalConfiguration.php breaks install tool
If you add an "empty" AdditionalConfiguration.php with only one line, "
/install.php?install[controller]=layout&install[context]=backend&install[action]=executeSilentConfigurationUpdate&_=1524415847672 add this one line to the JsonResponse. Backend response "Something went wrong. Please use Check for broken extensions to see if a loaded extension breaks this part of the install tool and unload it." in the view.
#6 Updated by Riccardo De Contardi over 1 year ago
I am actually able to reproduce it, with the latest master. My procedure:
1) create the file AdditionalConfiguration.php
2) write in it:
important: write exactly these characters, don't add anything else
- if you are outside the TYPO3 Backend, when you call the Install Tool, you get an empty page
- if you are inside the Backend and click on any of the Install Tool icons, you get the error:
Something went wrong. Please use Check for broken extensions to see if a loaded extension breaks this part of the install tool and unload it.
- There are no php errors
- The error occurs only when the AdditionalConfiguration.php does not contain a space or a new line after those characters so, if you just write
<?php or prepend a space, the error occurs; if you add a space or a line after
<?php, the error does occur.
#7 Updated by Christian Kuhn over 1 year ago
- Status changed from Needs Feedback to Rejected
Confirmed now, but imho not a bug of our application:
The start tag for php is
where [whitespace] is usually a line break.
Having a file without a line break or white space after
is invalid PHP, the code is interpreted as text only.
See the comments on http://php.net/manual/en/language.basic-syntax.phptags.php for more details on this.
You simply have to provide "valid" php code in this file, similar to a parse error or missing access permissions: That would make the Application fail, too.
According to my tests, the install tool works if you add
as file content.