Method "Symfony\Component\DependencyInjection\Extension\ExtensionInterface::load()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataHubBundle\DependencyInjection\PimcoreDataHubExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Extension\PrependExtensionInterface::prepend()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataHubBundle\DependencyInjection\PimcoreDataHubExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Extension\ExtensionInterface::load()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataImporterBundle\DependencyInjection\PimcoreDataImporterExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Extension\PrependExtensionInterface::prepend()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataImporterBundle\DependencyInjection\PimcoreDataImporterExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface::process()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataHubBundle\DependencyInjection\Compiler\ImportExportLocatorsPass" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface::process()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataHubBundle\DependencyInjection\Compiler\CustomDocumentTypePass" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface::process()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataImporterBundle\DependencyInjection\CompilerPass\MappingConfigurationFactoryPass" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface::process()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataImporterBundle\DependencyInjection\CompilerPass\ResolverConfigurationFactoryPass" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface::process()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataImporterBundle\DependencyInjection\CompilerPass\LoaderConfigurationFactoryPass" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface::process()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataImporterBundle\DependencyInjection\CompilerPass\InterpreterConfigurationFactoryPass" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface::process()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pimcore\Bundle\DataImporterBundle\DependencyInjection\CompilerPass\CleanupStrategyConfigurationFactoryPass" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "Symfony\Component\HttpKernel\Bundle\Bundle::build()" might add "void" as a native return type declaration in the future. Do the same in child class "Pimcore\Bundle\DataHubBundle\PimcoreDataHubBundle" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Support for MariaDB < 10.4 is deprecated and will be removed in DBAL 4. Consider upgrading to a more recent version of MariaDB. (AbstractMySQLDriver.php:55 called by AbstractDriverMiddleware.php:68, https://github.com/doctrine/dbal/pull/6110, package doctrine/dbal)
"SELECT item_id, CASE WHEN item_lifetime IS NULL OR item_lifetime + item_time > ? THEN item_data ELSE NULL END FROM cache_items WHERE item_id IN (?, ?)"
[
"sql" => "SELECT item_id, CASE WHEN item_lifetime IS NULL OR item_lifetime + item_time > ? THEN item_data ELSE NULL END FROM cache_items WHERE item_id IN (?, ?)"
"params" => [1 => 17438942652 => "\x01tags\x01site_domain_6894dc7ba736d7b8312a680dd4349060"
3 => "site_domain_6894dc7ba736d7b8312a680dd4349060"
]
"types" => [1 => 12 => 23 => 2]
]
debug
Executing statement:
"SELECT item_id, CASE WHEN item_lifetime IS NULL OR item_lifetime + item_time > ? THEN item_data ELSE NULL END FROM cache_items WHERE item_id IN (?, ?)"
"SELECT id FROM documents WHERE `path` = BINARY ? AND `key` = BINARY ?"
(parameters:
[1 => "/"
2 => "robots.txt"
]
, types:
[1 => 22 => 2]
)
doctrine
[
"sql" => "SELECT id FROM documents WHERE `path` = BINARY ? AND `key` = BINARY ?"
"params" => [1 => "/"
2 => "robots.txt"
]
"types" => [1 => 22 => 2]
]
debug
Executing statement:
"SELECT id FROM documents_page WHERE prettyUrl = ?"
(parameters:
[1 => "/robots.txt"
]
, types:
[1 => 2]
)
doctrine
[
"sql" => "SELECT id FROM documents_page WHERE prettyUrl = ?"
"params" => [1 => "/robots.txt"
]
"types" => [1 => 2]
]
debug
Executing statement:
"SELECT id FROM documents WHERE `path` = BINARY ? AND `key` = BINARY ?"
(parameters:
[1 => "/"
2 => ""
]
, types:
[1 => 22 => 2]
)
doctrine
[
"sql" => "SELECT id FROM documents WHERE `path` = BINARY ? AND `key` = BINARY ?"
"params" => [1 => "/"
2 => ""
]
"types" => [1 => 22 => 2]
]
debug
Executing statement:
"SELECT item_id, CASE WHEN item_lifetime IS NULL OR item_lifetime + item_time > ? THEN item_data ELSE NULL END FROM cache_items WHERE item_id IN (?, ?)"
[
"sql" => "SELECT item_id, CASE WHEN item_lifetime IS NULL OR item_lifetime + item_time > ? THEN item_data ELSE NULL END FROM cache_items WHERE item_id IN (?, ?)"
"params" => [1 => 17438942652 => "\x01tags\x01document_1"
3 => "document_1"
]
"types" => [1 => 12 => 23 => 2]
]
debug
Executing statement:
"SELECT item_id, CASE WHEN item_lifetime IS NULL OR item_lifetime + item_time > ? THEN item_data ELSE NULL END FROM cache_items WHERE item_id IN (?)"
(parameters:
[1 => 17438942652 => "document_1\x01tags\x01"
]
, types:
[1 => 12 => 2]
)
doctrine
[
"sql" => "SELECT item_id, CASE WHEN item_lifetime IS NULL OR item_lifetime + item_time > ? THEN item_data ELSE NULL END FROM cache_items WHERE item_id IN (?)"
"params" => [1 => 17438942652 => "document_1\x01tags\x01"
]
"types" => [1 => 12 => 2]
]
debug
Successfully got data for key
"document_1"
from cache
cache
[
"key" => "document_1"
]
debug
Executing statement:
"SELECT item_id, CASE WHEN item_lifetime IS NULL OR item_lifetime + item_time > ? THEN item_data ELSE NULL END FROM cache_items WHERE item_id IN (?, ?)"
User Deprecated: Since symfony/validator 6.4: Method "Symfony\Component\Validator\ValidatorBuilder::setDoctrineAnnotationReader()" is deprecated without replacement.