TYPO3 v10.1.0 won't install - typo3

I just wanted to install TYPO3 10.1.0, but the installation doesn't work.
At first, it throws an Server-500-error, without any php-errors.
After setting'displayErrors' => true I could see a detailed error message showing
Symfony\Component\DependencyInjection\Exception\InvalidArgumentException
The file "/var/www/html/typo3/public/typo3/sysext/core/Configuration//Services.yaml" does not contain valid YAML: Unexpected characters near "
I opend that file, and removed all comments inside it, and reloaded the install.php, which resolved that error, but another error was thrown, this time in my php-output:
NOTICE: PHP message: PHP Fatal error: Class TYPO3\CMS\Core\Mail\FileSpool contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Symfony\Component\Mailer\Transport\TransportInterface::__toString) in /var/www/html/typo3/public/typo3/sysext/core/Classes/Mail/FileSpool.php on line 38
After I added the __toString():string function in FileSpool.php, I get another error
NOTICE: PHP message: PHP Fatal error: Declaration of TYPO3\CMS\Core\Mail\Mailer::send(Symfony\Component\Mime\RawMessage $message, ?Symfony\Component\Mailer\SmtpEnvelope $envelope = NULL): void must be compatible with Symfony\Component\Mailer\MailerInterface::send(Symfony\Component\Mime\RawMessage $message, ?Symfony\Component\Mailer\Envelope $envelope = NULL): void in /var/www/html/typo3/public/typo3/sysext/core/Classes/Mail/Mailer.php on line 38
So, basically, the core/classes/Mail prevent me from installing TYPO3 10.1.0

This is a known problem caused by changes in Symfony version 4.4 components and is solved in current master or version 10.2.0 (release scheduled for tomorrow, December 3rd) see corresponding patch.
You currently have four options to circumvent this issue:
wait for the new release of tomorrow
use current master instead of 10.1
apply the patch to your installation
add the following lines to your composer.json
"conflict": {
"symfony/config": "~4.4.0",
"symfony/console": "~4.4.0",
"symfony/dependency-injection": "~4.4.0",
"symfony/expression-language": "~4.4.0",
"symfony/finder": "~4.4.0",
"symfony/mailer": "~4.4.0",
"symfony/mime": "~4.4.0",
"symfony/property-access": "~4.4.0",
"symfony/property-info": "~4.4.0",
"symfony/routing": "~4.4.0",
"symfony/yaml": "~4.4.0"
}

Related

How to add Babel support for nullishCoalescingOperator to vue project?

In my Vue-CLI project, when I tried using the ?? operator, I got this error:
Syntax Error: SyntaxError: /Users/stevebennett/odev/freelancing/v-map/src/components/Map.vue: >Support for the experimental syntax 'nullishCoalescingOperator' isn't currently enabled (30:29):
...
Add #babel/plugin-proposal-nullish-coalescing-operator (https://git.io/vb4Se) to the 'plugins' section of your Babel config to enable transformation.
I installed #babel/plugin-syntax-nullish-coalescing-operator (its name seems to have changed), added it to my babel.config.js:
module.exports = {
presets: ['#vue/app'],
plugins: ['#babel/plugin-syntax-nullish-coalescing-operator'],
};
Now the error message seems to have gone backwards, no reference to the operator name at all:
Module parse failed: Unexpected token (39:35)
You may need an appropriate loader to handle this file type.
| case 8:
| points = _context.sent;
console.log(sheetID ?? 37);
What am I doing wrong?
For me, the #babel/plugin-syntax-nullish-coalescing-operator plugin would not work, which is the one you are using.
I had to use the #babel/plugin-proposal-nullish-coalescing-operator plugin which is the one that the error message suggests you use.
Additionally, I noticed this on the page for the #babel/plugin-syntax-nullish-coalescing-operator plugin:
I can't say for sure if this will fix your problem, but it certainly fixed mine

TYPO3 - ext:form not working when using it in gridelements - v8

I have gridelements (the dev branch for 8.x.x) with 8LTS (+ fsc) and ext:form brought to work. Both seem to work for themselves. However, if I place a form element in a gridelement container ... I get the following error message when I want to send the form:
Oops, an error occurred!
The given string was not appended with a valid HMAC.
Anyone an idea what causes this? The other CE elements seem to work in the grid.
the Grid Configuration for all * CE is allowed in the defined container:
Name: Column #1
Column number: 10
Allowed CE: *
Allowed Grids: *
And in Log:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1320830018: The given string was
not appended with a valid HMAC. | TYPO3\CMS\Extbase\Security\Exception\InvalidHashException
thrown in file /is/htdocs/www/typo3_src-8.7.4/typo3/sysext/extbase/Classes/Security/Cryptography/HashService.php
in line 94.
Requested URL: .../contact/?tx_form_formframework%5Baction%5D=perform&tx_form_formframework%5Bcontroller%5D=FormFrontend&cHash=c81ac6ed1b41sdfgsdg71fsdfb44584e7
Debug shows:
TYPO3\CMS\Extbase\Security\Exception\InvalidHashException thrown in file
/is/htdocs/.../www/typo3_src-8.7.4/typo3/sysext/extbase/Classes/Security/Cryptography/HashService.php in line 94.
19 TYPO3\CMS\Extbase\Security\Cryptography\HashService::validateAndStripHmac("a:1:}ac4293effb593e4b063cbfcc6fc2c1e2c0c650a1")
/is/htdocs/.../www/typo3_src-8.7.4/typo3/sysext/extbase/Classes/Mvc/Controller/MvcPropertyMappingConfigurationService.php:
00124: }
00125:
00126: $serializedTrustedProperties = $this->hashService->validateAndStripHmac($trustedPropertiesToken);
00127: $trustedProperties = unserialize($serializedTrustedProperties);
00128: foreach ($trustedProperties as $propertyName => $propertyConfiguration) {
...

typo3 backend does not parse: syntax error, unexpected 'class' (T_CLASS)

I just installed Yet Another Gallery 4.0.7 on Typo3 6.2.19. When I try to open backend module I only get this error:
Parse error: syntax error, unexpected 'class' (T_CLASS), expecting identifier (T_STRING) or variable (T_VARIABLE) or '{' or '$' in /var/www/clients/client6/web32/web/typo3conf/ext/pt_extlist/Classes/Domain/Configuration/Filters/FilterConfig.php on line 351
Screenshot:
The error is coming from the extension "List Generator". The code uses the Class::class syntax which is probably not supported by your version of PHP. Check if you are running PHP 5.5 or higher.
You should try to call class like: 'Vendor\YourController\Task\Yourclass', instead of \Vender\YourController\Task\YourClass::class

using SoapClient,ArrayObject, ArrayIterator causes error in zend framework

I'm working on some helpful method in my entity.
private function setApi($api_address,$api_username,$api_password){
$this->api_address = $api_address;
$this->api_username = $api_username;
$this->api_password = $api_password;
$this->api_client = new SoapClient($api_address); // error
}
Warning: require(App/Entity/SoapClient.php): failed to open stream: No such file or directory in /zendboilerplate/library/Doctrine/Common/ClassLoader.php on line 148 Fatal error: require(): Failed opening required 'App/Entity/SoapClient.php' (include_path='/zendboilerplate/application/../library:/zendboilerplate/application/../library/Bisna/Application/Resource:/zendboilerplate/library:.:/usr/share/php:/usr/share/pear') in /zendboilerplate/library/Doctrine/Common/ClassLoader.php on line 148
It seems that zend looks for a class declaration (and it doesn't use included classes in php).
Identical error for each "new Class" declaration.
Using a my own class included in library everything is ok.
(Also tried with #new SoapClient() but no result).
I'm guessing this is namespace related. Try changing the line that is erroring to:
$this->api_client = new \SoapClient($api_address);
that should force it to use the PHP SoapClient instead of the namespace that is presumably declared at the start of the file you're having trouble with.

wurfl2 integration in TYPO3

everytime i try to install the wurfl2 extension in TYPO3 i get the following error message:
Fatal error: require_once() [function.require]: Failed opening required '' (include_path='.:/usr/local/php/lib/php:/usr/local/php/lib/php/PEAR') in /html/typo3conf/temp_CACHED_ps9b8e_ext_localconf.php on line 501
is anyone familiar with this error and knows how to fix it?
I get the same error message with TYPO3 4.4.4. I had to remove the extension folder and to delete all ./typo3conf/temp* files to get Typo3 running again afterwards.
(You might not see the error message if you don't have something like $TYPO3_CONF_VARS['SYS']['displayErrors'] = '1' in your localconf.php. You can set this with the installtool.
As already mentioned by the other answer first you have to get your system running again: set $TYPO3_CONF_VARS['SYS']['displayErrors'] = '1' in your localconf.php in order to see all error messages. Afterwards remove the extension folder.
I think the error is caused by a missing config file. The extension constant wurflConfig has to be set with the absolute path to the file /YOUR/PATH/TO/WEB_DIR/typo3conf/ext/wurfl2/res1/li/wurfl_config.php and might have to adjust the settings there.