Default theme. It switches between Light and Dark automatically to match the operating system theme.
Provides greatest readability, but requires a well-lit environment.
Reduces eye fatigue. Ideal for low light environments.
Page Width
Fixed page width. Improves readability.
Dynamic page width. As wide as the browser window.
Log Messages
Level (7)
Channel (6)
Time
Message
deprecation
Method "Symfony\Component\DependencyInjection\Extension\Extension::getAlias()" might add "string" as a native return type declaration in the future. Do the same in child class "Exercise\HTMLPurifierBundle\DependencyInjection\ExerciseHTMLPurifierExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Extension\Extension::getAlias()" might add "string" as a native return type declaration in the future. Do the same in child class "Eccube\DependencyInjection\EccubeExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Extension\ConfigurationExtensionInterface::getConfiguration()" might add "?ConfigurationInterface" as a native return type declaration in the future. Do the same in implementation "Eccube\DependencyInjection\EccubeExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\ComposerInstallCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\ComposerRemoveCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\ComposerRequireAlreadyInstalledPluginsCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\ComposerRequireCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\ComposerUpdateCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\DeleteCartsCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\GenerateDummyDataCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\GenerateProxyCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\InstallerCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
The "Doctrine\Bundle\DoctrineBundle\Command\DoctrineCommand" class is considered internal. It may change without further notice. You should not use it from "Eccube\Command\LoadDataFixturesEccubeCommand".
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\LoadDataFixturesEccubeCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\PluginDisableCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\PluginEnableCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\PluginGenerateCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\PluginInstallCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\PluginSchemaUpdateCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\PluginUninstallCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Eccube\Command\PluginUpdateCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
The "Eccube\Command\UpdateSchemaDoctrineCommand" class extends "Doctrine\Bundle\DoctrineBundle\Command\Proxy\UpdateSchemaDoctrineCommand" that is deprecated use Doctrine\ORM\Tools\Console\Command\SchemaTool\UpdateCommand instead.
Method "Symfony\Component\HttpKernel\DataCollector\DataCollectorInterface::getName()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\DataCollector\EccubeDataCollector" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\DataFixtures\Executor\AbstractExecutor::execute()" might add "void" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\Common\CsvDataFixtures\Executor\DbalExecutor" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\DBAL\Types\Type::convertToDatabaseValue()" might add "mixed" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\DBAL\Types\Type::convertToPHPValue()" might add "mixed" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\DBAL\Types\Type::requiresSQLCommentHint()" might add "bool" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\DBAL\Types\Type::convertToDatabaseValue()" might add "mixed" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeTzType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\DBAL\Types\Type::convertToPHPValue()" might add "mixed" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeTzType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\DBAL\Types\Type::requiresSQLCommentHint()" might add "bool" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeTzType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Doctrine\EventSubscriber\InitSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Doctrine\EventSubscriber\TaxRuleEventSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\ORM\Query\Filter\SQLFilter::addFilterConstraint()" might add "string" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\Filter\NoStockHiddenFilter" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\ORM\Query\Filter\SQLFilter::addFilterConstraint()" might add "string" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\Filter\OrderStatusFilter" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Persistence\Mapping\Driver\MappingDriver::getAllClassNames()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Doctrine\ORM\Mapping\Driver\AnnotationDriver" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Persistence\Mapping\Driver\MappingDriver::getAllClassNames()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Doctrine\ORM\Mapping\Driver\NopAnnotationDriver" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Persistence\Mapping\Driver\MappingDriver::getAllClassNames()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Doctrine\ORM\Mapping\Driver\ReloadSafeAnnotationDriver" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\ORM\Query\AST\Functions\FunctionNode::parse()" might add "void" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\ORM\Query\Extract" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\ORM\Query\AST\Functions\FunctionNode::getSql()" might add "string" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\ORM\Query\Extract" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\ORM\Query\AST\Functions\FunctionNode::parse()" might add "void" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\ORM\Query\Normalize" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\ORM\Query\AST\Functions\FunctionNode::getSql()" might add "string" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\ORM\Query\Normalize" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\EventListener\IpAddrListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\EventListener\LogListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\EventListener\MaintenanceListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\EventListener\MobileTemplatePathListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\EventListener\RateLimiterListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\EventListener\RestrictFileUploadListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\EventListener\TwigInitializeListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\DataTransformerInterface::transform()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\DataTransformer\EntityToIdTransformer" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\DataTransformerInterface::reverseTransform()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\DataTransformer\EntityToIdTransformer" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\EventListener\ConvertKanaListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\AddCartType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\AddressType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\AuthenticationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\AuthorityRoleType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\BlockType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\CalendarType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\CategoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\ChangePasswordType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\ClassCategoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\ClassNameType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\CsvImportType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\CustomerType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\DeliveryFeeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\DeliveryTimeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\DeliveryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\LayoutType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\LogType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\LoginType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\MailType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\MainEditType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\MasterdataDataType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\MasterdataEditType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\MasterdataType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\MemberType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\NewsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\OrderItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\OrderMailType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\OrderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\PageType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\PaymentRegisterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\PluginLocalInstallType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\PluginManagementType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\ProductClassType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\ProductTag" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\ProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\SearchCustomerType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\SearchLoginHistoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\SearchOrderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\SearchPluginApiType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\SearchProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\SecurityType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\ShippingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\ShopMasterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\TagType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\TaxRuleType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\TemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Admin\TwoFactorAuthType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Front\ContactType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Front\CustomerAddressType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Front\CustomerLoginType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Front\EntryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Front\ForgotType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Front\NonMemberType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Front\PasswordResetType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Front\ShoppingShippingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Front\ShoppingShippingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Install\Step1Type" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Install\Step3Type" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Install\Step4Type" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Install\Step5Type" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\KanaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\KanaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\CategoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\CategoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\CsvType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\CsvType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\CustomerStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\CustomerStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\DeliveryDurationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\DeliveryDurationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\DeviceTypeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\DeviceTypeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\JobType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\JobType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\LoginHistoryStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\LoginHistoryStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\MailTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\MailTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\OrderStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\OrderStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\PageMaxType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\PageMaxType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\PaymentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\PaymentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\PrefType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\PrefType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\ProductListMaxType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\ProductListMaxType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\ProductListOrderByType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\ProductListOrderByType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\ProductStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\ProductStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\RoundingTypeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\RoundingTypeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\SaleTypeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\SaleTypeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\SexType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Master\SexType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\MasterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\MasterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\NameType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\PhoneNumberType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\PhoneNumberType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\PostalType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\PostalType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\PriceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\PriceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\RepeatedEmailType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\RepeatedEmailType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\RepeatedPasswordType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\RepeatedPasswordType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\SearchProductBlockType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\SearchProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\ShippingMultipleItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\ShippingMultipleType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Shopping\OrderItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Shopping\OrderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\Shopping\ShippingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\ShoppingMultipleType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Eccube\Form\Type\ToggleSwitchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Encoder\PasswordEncoderInterface" class is deprecated, use "Symfony\Component\PasswordHasher\PasswordHasherInterface" instead.
The "Eccube\Security\Core\Encoder\PasswordEncoder" class implements "Symfony\Component\Security\Core\Encoder\PasswordEncoderInterface" that is deprecated since Symfony 5.3, use {@link PasswordHasherInterface} instead.
Class "Eccube\Security\Core\User\CustomerProvider" should implement method "Symfony\Component\Security\Core\User\UserProviderInterface::loadUserByIdentifier(string $identifier): UserInterface": loads the user for the given user identifier (e.g. username or email). This method must throw UserNotFoundException if the user is not found.
Class "Eccube\Security\Core\User\MemberProvider" should implement method "Symfony\Component\Security\Core\User\UserProviderInterface::loadUserByIdentifier(string $identifier): UserInterface": loads the user for the given user identifier (e.g. username or email). This method must throw UserNotFoundException if the user is not found.
Method "Symfony\Component\Security\Http\Authentication\AuthenticationFailureHandlerInterface::onAuthenticationFailure()" might add "Response" as a native return type declaration in the future. Do the same in implementation "Eccube\Security\Http\Authentication\EccubeAuthenticationFailureHandler" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Security\Http\Authentication\AuthenticationSuccessHandlerInterface::onAuthenticationSuccess()" might add "Response" as a native return type declaration in the future. Do the same in implementation "Eccube\Security\Http\Authentication\EccubeAuthenticationSuccessHandler" now to avoid errors or add an explicit @return annotation to suppress this message.
Since symfony/security-http 5.1: The "Symfony\Component\Security\Http\Logout\DefaultLogoutSuccessHandler" class is deprecated, use "Symfony\Component\Security\Http\EventListener\DefaultLogoutListener" instead.
Since symfony/security-http 5.1: The "Symfony\Component\Security\Http\Logout\LogoutSuccessHandlerInterface" interface is deprecated, create a listener for the "Symfony\Component\Security\Http\Event\LogoutEvent" event instead.
The "Eccube\Security\Http\Authentication\EccubeLogoutSuccessHandler" class extends "Symfony\Component\Security\Http\Logout\DefaultLogoutSuccessHandler" that is deprecated since Symfony 5.1.
Method "Symfony\Component\Security\Http\Logout\LogoutSuccessHandlerInterface::onLogoutSuccess()" might add "Response" as a native return type declaration in the future. Do the same in implementation "Eccube\Security\Http\Authentication\EccubeLogoutSuccessHandler" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Security\Core\Authorization\Voter\VoterInterface::vote()" might add "int" as a native return type declaration in the future. Do the same in implementation "Eccube\Security\Voter\AuthorityVoter" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Countable::count()" might add "int" as a native return type declaration in the future. Do the same in implementation "Eccube\Service\CsvImportService" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "SeekableIterator::seek()" might add "void" as a native return type declaration in the future. Do the same in implementation "Eccube\Service\CsvImportService" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "TCPDF::_getxobjectdict()" might add "string" as a native return type declaration in the future. Do the same in child class "setasign\Fpdi\Tcpdf\Fpdi" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Service\OrderStateMachine" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Service\SystemService" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\HttpFoundation\Session\Storage\Handler\StrictSessionHandler::open()" might add "bool" as a native return type declaration in the future. Do the same in child class "Eccube\Session\Storage\Handler\SameSiteNoneCompatSessionHandler" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\HttpFoundation\Session\Storage\Handler\AbstractSessionHandler::doRead()" might add "string" as a native return type declaration in the future. Do the same in child class "Eccube\Session\Storage\Handler\SameSiteNoneCompatSessionHandler" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\HttpFoundation\Session\Storage\Handler\StrictSessionHandler::updateTimestamp()" might add "bool" as a native return type declaration in the future. Do the same in child class "Eccube\Session\Storage\Handler\SameSiteNoneCompatSessionHandler" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\HttpFoundation\Session\Storage\Handler\AbstractSessionHandler::doWrite()" might add "bool" as a native return type declaration in the future. Do the same in child class "Eccube\Session\Storage\Handler\SameSiteNoneCompatSessionHandler" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\HttpFoundation\Session\Storage\Handler\StrictSessionHandler::destroy()" might add "bool" as a native return type declaration in the future. Do the same in child class "Eccube\Session\Storage\Handler\SameSiteNoneCompatSessionHandler" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\HttpFoundation\Session\Storage\Handler\AbstractSessionHandler::doDestroy()" might add "bool" as a native return type declaration in the future. Do the same in child class "Eccube\Session\Storage\Handler\SameSiteNoneCompatSessionHandler" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\HttpFoundation\Session\Storage\Handler\StrictSessionHandler::close()" might add "bool" as a native return type declaration in the future. Do the same in child class "Eccube\Session\Storage\Handler\SameSiteNoneCompatSessionHandler" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Extension\ExtensionInterface::getFunctions()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Twig\Extension\CartServiceExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Extension\ExtensionInterface::getFunctions()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Twig\Extension\EccubeBlockExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Extension\ExtensionInterface::getFilters()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Twig\Extension\IntlExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Extension\ExtensionInterface::getFunctions()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Twig\Extension\RepositoryExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Extension\ExtensionInterface::getFunctions()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Twig\Extension\TwigIncludeExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Template::getTemplateName()" might add "string" as a native return type declaration in the future. Do the same in child class "Eccube\Twig\Template" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Template::getDebugInfo()" might add "array" as a native return type declaration in the future. Do the same in child class "Eccube\Twig\Template" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Template::getSourceContext()" might add "Source" as a native return type declaration in the future. Do the same in child class "Eccube\Twig\Template" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Util\CacheUtil" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\AmazonPayV2_42\AmazonPayEvent" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::verify()" might add "PaymentResult" as a native return type declaration in the future. Do the same in implementation "Plugin\AmazonPayV2_42\Service\Method\AmazonPay" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::apply()" might add "PaymentDispatcher" as a native return type declaration in the future. Do the same in implementation "Plugin\AmazonPayV2_42\Service\Method\AmazonPay" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::checkout()" might add "PaymentResult" as a native return type declaration in the future. Do the same in implementation "Plugin\AmazonPayV2_42\Service\Method\AmazonPay" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setFormType()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\AmazonPayV2_42\Service\Method\AmazonPay" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setOrder()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\AmazonPayV2_42\Service\Method\AmazonPay" now to avoid errors or add an explicit @return annotation to suppress this message.
The "Plugin\AmazonPayV2_42\phpseclib\Net\SFTP::login()" method will require a new "mixed $..." argument in the next major version of its parent class "Plugin\AmazonPayV2_42\phpseclib\Net\SSH2", not defining it is deprecated.
Method "Symfony\Component\Console\Command\Command::execute()" might add "int" as a native return type declaration in the future. Do the same in child class "Plugin\Api42\Command\DumpSchemaCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\Api42\Doctrine\EventSubscriber\EntityListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\Api42\Form\Type\Admin\ClientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\Api42\Form\Type\Admin\OAuth2AuthorizationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "GraphQL\Error\ClientAware::isClientSafe()" might add "bool" as a native return type declaration in the future. Do the same in implementation "Plugin\Api42\GraphQL\Error\InvalidArgumentException" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "GraphQL\Error\ClientAware::getCategory()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\Api42\GraphQL\Error\InvalidArgumentException" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "GraphQL\Validator\Rules\ValidationRule::getVisitor()" might add "array" as a native return type declaration in the future. Do the same in child class "Plugin\Api42\GraphQL\ScopeValidationRule" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\Api42\Service\WebHookService" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\AttachWysiwygEditor42\EventListener\AweEditorListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\MailMagazine42\Event\MailMagazineHistoryFilePaginationSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Plugin\MailMagazine42\Form\Type\MailMagazineTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\MypageReceipt2Ft\MypageReceipt2FtEvent" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\Noshidelivery\Form\Type\Admin\NoshideliveryCheckType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\Noshidelivery\Form\Type\Admin\NoshideliveryKindType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\Noshidelivery\Form\Type\Admin\NoshideliveryTieType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\Noshidelivery\Form\Type\Master\NoshideliveryCheckType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Plugin\Noshidelivery\Form\Type\Master\NoshideliveryCheckType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\Noshidelivery\Form\Type\Master\NoshideliveryKindType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Plugin\Noshidelivery\Form\Type\Master\NoshideliveryKindType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\Noshidelivery\Form\Type\Master\NoshideliveryTieType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Plugin\Noshidelivery\Form\Type\Master\NoshideliveryTieType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\Noshidelivery\NoshideliveryEvent" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Doctrine\Query\QueryCustomizer::getQueryKey()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\OrderStatusEx\Doctrine\Query\AdminOrderSearchCustomizer" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\OrderStatusEx\EventSubscriber\OrderStatusEventSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\OrderStatusEx\EventSubscriber\PointExDxEventSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\OrderStatusEx\EventSubscriber\SearchEventSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Plugin\OrderStatusEx\Form\Type\CustomEntityType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Extension\ExtensionInterface::getFunctions()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\OrderStatusEx\Twig\OrderStatusExTwigExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\PointExDx\EventSubscriber\EntryEventSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Extension\ExtensionInterface::getFunctions()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\PointExDx\Twig\PointExDxTwigExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\PostCarrier42\EventListener\ConversionTagListener" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\PostCarrier42\Form\Type\PostCarrierCsvImportType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\PostCarrier42\Form\Type\PostCarrierGroupType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\PostCarrier42\Form\Type\PostCarrierMailmagaBlockType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Repository\CustomerRepository::getQueryBuilderBySearchData()" might add "QueryBuilder" as a native return type declaration in the future. Do the same in child class "Plugin\PostCarrier42\Repository\PostCarrierCustomerRepository" now to avoid errors or add an explicit @return annotation to suppress this message.
The "Plugin\PostCarrier42\Util\SqlPeekingLogger" class implements "Doctrine\DBAL\Logging\SQLLogger" that is deprecated Use {@see \Doctrine\DBAL\Logging\Middleware} or implement {@see \Doctrine\DBAL\Driver\Middleware} instead.
Method "Doctrine\DBAL\Logging\SQLLogger::startQuery()" might add "void" as a native return type declaration in the future. Do the same in implementation "Plugin\PostCarrier42\Util\SqlPeekingLogger" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\DBAL\Logging\SQLLogger::stopQuery()" might add "void" as a native return type declaration in the future. Do the same in implementation "Plugin\PostCarrier42\Util\SqlPeekingLogger" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Common\EccubeNav::getNav()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\ProductReview42\ProductReviewNav" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\RelatedProduct42\RelatedProductEvent" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\ReportPdf2Ft\ReportPdf2FtEvent" now to avoid errors or add an explicit @return annotation to suppress this message.
The "Plugin\ReportPdf2Ft\Service\ReportPdf2FtService" class extends "setasign\Fpdi\TcpdfFpdi" that is deprecated Class was moved to \setasign\Fpdi\Tcpdf\Fpdi.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\Securitychecker42\Form\Type\Securitychecker42ConfigType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\SendAllMails42\Form\Type\Admin\OrderMailType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\FormTypeInterface::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Form\Type\Admin\SearchPaymentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setFormType()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Service\Method\Credit" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setOrder()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Service\Method\Credit" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setFormType()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Service\Method\Cvs" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setOrder()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Service\Method\Cvs" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setFormType()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Service\Method\Deferred" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setOrder()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Service\Method\Deferred" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setFormType()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Service\Method\DeferredSms" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setOrder()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Service\Method\DeferredSms" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setFormType()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Service\Method\Paypay" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Eccube\Service\Payment\PaymentMethodInterface::setOrder()" might add "PaymentMethod" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Service\Method\Paypay" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Extension\ExtensionInterface::getFunctions()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\Twig\Extension\YamatoExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Plugin\YamatoPayment42\YamatoPaymentEvent" now to avoid errors or add an explicit @return annotation to suppress this message.
Since symfony/framework-bundle 5.1: Not setting the "framework.router.utf8" configuration option is deprecated, it will default to "true" in version 6.0.
Since symfony/framework-bundle 5.3: Not setting the "framework.session.storage_factory_id" configuration option is deprecated, it will default to "session.storage.factory.native" and will replace the "framework.session.storage_id" configuration option in version 6.0.
Since symfony/security-bundle 5.1: The "success_handler" at path "security.firewalls.admin.logout" is deprecated, register a listener on the "Symfony\Component\Security\Http\Event\LogoutEvent" event instead.
Class "Eccube\Entity\Member" should implement method "Symfony\Component\Security\Core\User\UserInterface::getUserIdentifier(): string": returns the identifier for this user (e.g. its username or email address).
Method "Symfony\Component\Security\Core\User\UserInterface::getRoles()" might add "array" as a native return type declaration in the future. Do the same in implementation "Eccube\Entity\Member" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Security\Core\User\UserInterface::getUsername()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Entity\Member" now to avoid errors or add an explicit @return annotation to suppress this message.
Since symfony/security-bundle 5.3: Configuring an encoder for a user class that does not implement "Symfony\Component\Security\Core\User\PasswordAuthenticatedUserInterface" is deprecated, class "Eccube\Entity\Member" should implement it.
Since symfony/security-bundle 5.3: Configuring an encoder for a user class that does not implement "Symfony\Component\Security\Core\User\PasswordAuthenticatedUserInterface" is deprecated, class "Eccube\Entity\Customer" should implement it.
Since symfony/security-bundle 5.3: Configuring a password hasher for a user class that does not implement "Symfony\Component\Security\Core\User\PasswordAuthenticatedUserInterface" is deprecated, class "Eccube\Entity\Member" should implement it.
Since symfony/security-bundle 5.3: Configuring a password hasher for a user class that does not implement "Symfony\Component\Security\Core\User\PasswordAuthenticatedUserInterface" is deprecated, class "Eccube\Entity\Customer" should implement it.
Enabling the "sensio_framework_extra.router.annotations" configuration is deprecated since version 5.2. Set it to false and use the "Symfony\Component\Routing\Annotation\Route" annotation from Symfony itself.
Method "Symfony\Component\Config\Definition\ConfigurationInterface::getConfigTreeBuilder()" might add "TreeBuilder" as a native return type declaration in the future. Do the same in implementation "Exercise\HTMLPurifierBundle\DependencyInjection\Configuration" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "ArrayAccess::offsetSet()" might add "void" as a native return type declaration in the future. Do the same in implementation "Eccube\Common\EccubeConfig" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "ArrayAccess::offsetUnset()" might add "void" as a native return type declaration in the future. Do the same in implementation "Eccube\Common\EccubeConfig" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Psr\Log\LoggerInterface::log()" might add "void" as a native return type declaration in the future. Do the same in implementation "Eccube\Log\Logger" now to avoid errors or add an explicit @return annotation to suppress this message.
The "Nyholm\Psr7\Factory\HttplugFactory" class implements "Http\Message\MessageFactory" that is deprecated since version 1.1, use Psr\Http\Message\RequestFactoryInterface and Psr\Http\Message\ResponseFactoryInterface instead.
The "Nyholm\Psr7\Factory\HttplugFactory" class implements "Http\Message\StreamFactory" that is deprecated since version 1.1, use Psr\Http\Message\StreamFactoryInterface instead.
The "Nyholm\Psr7\Factory\HttplugFactory" class implements "Http\Message\UriFactory" that is deprecated since version 1.1, use Psr\Http\Message\UriFactoryInterface instead.
Since symfony/asset 5.3: The "Symfony\Component\Asset\VersionStrategy\RemoteJsonManifestVersionStrategy" class is deprecated, use "Symfony\Component\Asset\VersionStrategy\JsonManifestVersionStrategy" instead.
Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactory" class is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactory" instead.
Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" class is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead.
Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Encoder\UserPasswordEncoder" class is deprecated, use "Symfony\Component\PasswordHasher\Hasher\UserPasswordHasher" instead.
Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Encoder\UserPasswordEncoderInterface" interface is deprecated, use "Symfony\Component\PasswordHasher\Hasher\UserPasswordHasherInterface" instead.
Since symfony/security-http 5.4: The "Symfony\Component\Security\Http\EntryPoint\BasicAuthenticationEntryPoint" class is deprecated, use the new security system with "Symfony\Component\Security\Http\Authenticator\HttpBasicAuthenticator" instead.
Since symfony/security-http 5.4: The "Symfony\Component\Security\Http\EntryPoint\RetryAuthenticationEntryPoint" class is deprecated, use "Symfony\Component\Security\Http\Firewall\ChannelListener" directly (and optionally configure the HTTP(s) ports there).
Since symfony/security-http 5.4: The "Symfony\Component\Security\Http\EntryPoint\FormAuthenticationEntryPoint" class is deprecated, use the new security system with "Symfony\Component\Security\Http\Authenticator\FormLoginAuthenticator" instead.
Since symfony/security-http 5.3: The "Symfony\Component\Security\Http\Firewall\RememberMeListener" class is deprecated, use the new authenticator system instead.
Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Authentication\Provider\RememberMeAuthenticationProvider" class is deprecated, use the new authenticator system instead.
Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Authentication\Provider\AuthenticationProviderInterface" interface is deprecated, use the new authenticator system instead.
Since symfony/security-http 5.4: The "Symfony\Component\Security\Http\RememberMe\PersistentTokenBasedRememberMeServices" class is deprecated, use "Symfony\Component\Security\Http\RememberMe\PersistentRememberMeHandler" instead.
Since symfony/security-http 5.4: The "Symfony\Component\Security\Http\RememberMe\AbstractRememberMeServices" class is deprecated, use "Symfony\Component\Security\Http\RememberMe\AbstractRememberMeHandler" instead.
Since symfony/security-http 5.4: The "Symfony\Component\Security\Http\RememberMe\RememberMeServicesInterface" interface is deprecated, use "Symfony\Component\Security\Http\RememberMe\RememberMeHandlerInterface" instead.
Since symfony/security-http 5.4: The "Symfony\Component\Security\Http\RememberMe\TokenBasedRememberMeServices" class is deprecated, use "Symfony\Component\Security\Http\RememberMe\SignatureRememberMeHandler" instead.
Since symfony/security-guard 5.3: The "Symfony\Component\Security\Guard\GuardAuthenticatorHandler" class is deprecated, use the new authenticator system instead.
Since symfony/security-guard 5.3: The "Symfony\Component\Security\Guard\Provider\GuardAuthenticationProvider" class is deprecated, use the new authenticator system instead.
Since symfony/security-guard 5.3: The "Symfony\Component\Security\Guard\Firewall\GuardAuthenticationListener" class is deprecated, use the new authenticator system instead.
The "Sensio\Bundle\FrameworkExtraBundle\Routing\AnnotatedRouteControllerLoader" class is deprecated since version 5.2. Use "Symfony\Bundle\FrameworkBundle\Routing\AnnotatedRouteControllerLoader" instead.
Since symfony/maker-bundle 1.29: The "Symfony\Bundle\MakerBundle\Maker\MakeFunctionalTest" class is deprecated, use "Symfony\Bundle\MakerBundle\Maker\MakeTest" instead.
Since symfony/maker-bundle 1.29: The "Symfony\Bundle\MakerBundle\Maker\MakeUnitTest" class is deprecated, use "Symfony\Bundle\MakerBundle\Maker\MakeTest" instead.
Method "Symfony\Component\HttpKernel\CacheWarmer\WarmableInterface::warmUp()" might add "array" as a native return type declaration in the future. Do the same in implementation "Exercise\HTMLPurifierBundle\CacheWarmer\SerializerCacheWarmer" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\HttpKernel\CacheWarmer\CacheWarmerInterface::isOptional()" might add "bool" as a native return type declaration in the future. Do the same in implementation "Exercise\HTMLPurifierBundle\CacheWarmer\SerializerCacheWarmer" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Extension\ExtensionInterface::getFilters()" might add "array" as a native return type declaration in the future. Do the same in implementation "Exercise\HTMLPurifierBundle\Twig\HTMLPurifierExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Command\DeleteCartsCommand" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Command\GenerateProxyCommand" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Command\InstallerCommand" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Command\LoadDataFixturesEccubeCommand" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Command\PluginGenerateCommand" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\AbstractController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\AbstractShoppingController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\AbstractCsvImportController" service.
Since symfony/security-bundle 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" service is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. It is being referenced by the "Eccube\Controller\Admin\AdminController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\AdminController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Content\BlockController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Content\CacheController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Content\CssController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Content\FileController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Content\JsController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Content\LayoutController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Content\MaintenanceController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Content\NewsController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Content\PageController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Customer\CustomerController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Customer\CustomerDeliveryEditController" service.
Since symfony/security-bundle 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" service is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. It is being referenced by the "Eccube\Controller\Admin\Customer\CustomerEditController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Customer\CustomerEditController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Order\CsvImportController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Order\EditController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Order\MailController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Order\OrderController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Order\ShippingController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Product\CategoryController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Product\ClassCategoryController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Product\ClassNameController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Product\CsvImportController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Product\ProductClassController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Product\ProductController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Product\TagController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\Shop\CalendarController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\Shop\CsvController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\Shop\DeliveryController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\Shop\MailController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\Shop\OrderStatusController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\Shop\PaymentController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\Shop\ShopController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\Shop\TaxRuleController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\Shop\TradeLawController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\System\AuthorityController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\System\LogController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\System\LoginHistoryController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\System\MasterdataController" service.
Since symfony/security-bundle 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" service is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\System\MemberController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\System\MemberController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\System\SecurityController" service.
Since symfony/security-bundle 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" service is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\System\TwoFactorAuthController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Setting\System\TwoFactorAuthController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Store\OwnerStoreController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Store\PluginController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Admin\Store\TemplateController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Block\CalendarController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Block\CartController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Block\SearchProductController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\CartController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\ContactController" service.
Since symfony/security-bundle 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" service is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. It is being referenced by the "Eccube\Controller\EntryController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\EntryController" service.
Since symfony/security-bundle 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" service is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. It is being referenced by the "Eccube\Controller\ForgotController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\ForgotController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\HelpController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Install\InstallController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\InstallPluginController" service.
Since symfony/security-bundle 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" service is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. It is being referenced by the "Eccube\Controller\Mypage\ChangeController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Mypage\ChangeController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Mypage\DeliveryController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Mypage\MypageController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\Mypage\WithdrawController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\NonMemberShoppingController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\ProductController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\ShippingMultipleController" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Controller\ShoppingController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\ShoppingController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\SitemapController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\TopController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\TradeLawController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Controller\UserDataController" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\DataCollector\EccubeDataCollector" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Doctrine\EventSubscriber\TaxRuleEventSubscriber" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Form\Type\Admin\LoginType" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Form\Type\PriceType" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Form\Type\ShippingMultipleItemType" service.
Since symfony/security-bundle 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" service is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. It is being referenced by the "Eccube\Repository\CustomerRepository" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Repository\PageRepository" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Service\CartService" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Service\EntityProxyService" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Service\MailService" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Service\OrderHelper" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Service\OrderHelper" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Service\PluginService" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Service\SystemService" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Service\TwoFactorAuthService" service.
Since symfony/security-bundle 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" service is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. It is being referenced by the "Eccube\Service\TwoFactorAuthService" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Util\CacheUtil" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Common\EccubeConfig" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Eccube\Service\Composer\ComposerServiceInterface" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\AmazonPayV2_42\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\AmazonPayV2_42\Controller\Admin\PaymentStatusController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\AmazonPayV2_42\Controller\AmazonRedirectController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\AmazonPayV2_42\Controller\AmazonShoppingController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Api42\Controller\Admin\GraphiQLController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Api42\Controller\Admin\OAuthController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Api42\Controller\Admin\WebHookController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Api42\Controller\ApiController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\AttachWysiwygEditor42\Controller\Admin\AweConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\AttachWysiwygEditor42\Controller\Admin\AweMediaController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\CategorySort42\Controller\CategorySortController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Coupon42\Controller\Admin\CouponController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Coupon42\Controller\Admin\CouponSearchModelController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Coupon42\Controller\CouponShoppingController" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Plugin\Coupon42\Form\Type\CouponType" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Plugin\Coupon42\Service\CouponService" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\DataMigration42\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\MailMagazine42\Controller\MailMagazineController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\MailMagazine42\Controller\MailMagazineHistoryController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\MailMagazine42\Controller\MailMagazineTemplateController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\MypageReceipt2Ft\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\MypageReceipt2Ft\Controller\MypageReceipt2FtController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Noshidelivery\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Noshidelivery\Controller\Admin\NoshideliveryCheckController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Noshidelivery\Controller\Admin\NoshideliveryKindController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Noshidelivery\Controller\Admin\NoshideliveryTieController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\OrderStatusEx\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\OrderStatusEx\Controller\Admin\Seggin\Shop\OrderStatusExController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PointExDx\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PointExDx\Controller\Admin\Setting\Shop\PointExDxController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\DiscardController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\HistoryController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\MailCustomerController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\MailmagaBlockController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\MonthlyReportContoller" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\PostCarrierController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\ReceiveController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\ScheduleController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\StepMailController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\PostCarrier42\Controller\TemplateController" service.
Since symfony/security-bundle 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" service is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. It is being referenced by the "Plugin\PostCarrier42\Repository\PostCarrierCustomerRepository" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\ProductContact42\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\ProductReview42\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\ProductReview42\Controller\Admin\ProductReviewController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\ProductReview42\Controller\ProductReviewController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Recommend42\Controller\RecommendController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Recommend42\Controller\RecommendSearchModelController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\RelatedProduct42\Controller\Admin\RelatedProductController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\ReportPdf2Ft\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\ReportPdf2Ft\Controller\ReportPdf2FtController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\SalesReport42\Controller\SalesReportController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\Securitychecker42\Controller\ConfigController" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Plugin\Securitychecker42\Service\Securitychecker42Service" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\SendAllMails42\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\SiteKit42\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\SiteKit42\Controller\Admin\DashboardController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\YamatoB2Csv42\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\YamatoB2Csv42\Controller\Admin\YamatoB2Controller" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\YamatoPayment42\Controller\Admin\ConfigController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\YamatoPayment42\Controller\Admin\PaymentStatusController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\YamatoPayment42\Controller\CreditController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\YamatoPayment42\Controller\PaymentController" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\YamatoPayment42\Controller\PaymentRecvController" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Plugin\YamatoPayment42\Service\Method\DeferredSms" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\YamatoPayment42\Service\Method\DeferredSms" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Plugin\YamatoPayment42\Service\YamatoConfigService" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "Plugin\YamatoPayment42\Service\YamatoStatusService" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Plugin\YamatoPayment42\Util\SecurityUtil" service.
Since symfony/dependency-injection 5.1: The "Symfony\Component\DependencyInjection\ContainerInterface" autowiring alias is deprecated. Define it explicitly in your app if you want to keep using it. It is being referenced by the "eccube.collector.core" service.
Since symfony/framework-bundle 5.3: The "Symfony\Component\HttpFoundation\Session\SessionInterface" and "SessionInterface" aliases are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Log\Processor\SessionProcessor" service.
Since symfony/framework-bundle 5.3: The "session" service and "SessionInterface" alias are deprecated, use "$requestStack->getSession()" instead. It is being referenced by the "Eccube\Tests\Fixture\Generator" service.
Since symfony/framework-bundle 5.3: The "session.storage.factory.service" service is deprecated, use "session.storage.factory.native", "session.storage.factory.php_bridge" or "session.storage.factory.mock_file" instead.
Method "Monolog\Formatter\FormatterInterface::format()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "EasyCorp\EasyLog\EasyLogFormatter" now to avoid errors or add an explicit @return annotation to suppress this message.
"SELECT t0.id AS id_1, t0.company_name AS company_name_2, t0.company_kana AS company_kana_3, t0.postal_code AS postal_code_4, t0.addr01 AS addr01_5, t0.addr02 AS addr02_6, t0.phone_number AS phone_number_7, t0.business_hour AS business_hour_8, t0.email01 AS email01_9, t0.email02 AS email02_10, t0.email03 AS email03_11, t0.email04 AS email04_12, t0.shop_name AS shop_name_13, t0.shop_kana AS shop_kana_14, t0.shop_name_eng AS shop_name_eng_15, t0.update_date AS update_date_16, t0.good_traded AS good_traded_17, t0.message AS message_18, t0.delivery_free_amount AS delivery_free_amount_19, t0.delivery_free_quantity AS delivery_free_quantity_20, t0.option_mypage_order_status_display AS option_mypage_order_status_display_21, t0.option_nostock_hidden AS option_nostock_hidden_22, t0.option_favorite_product AS option_favorite_product_23, t0.option_product_delivery_fee AS option_product_delivery_fee_24, t0.invoice_registration_number AS invoice_registration_number_25, t0.option_product_tax_rule AS option_product_tax_rule_26, t0.option_customer_activate AS option_customer_activate_27, t0.option_remember_me AS option_remember_me_28, t0.option_mail_notifier AS option_mail_notifier_29, t0.authentication_key AS authentication_key_30, t0.php_path AS php_path_31, t0.option_point AS option_point_32, t0.basic_point_rate AS basic_point_rate_33, t0.point_conversion_rate AS point_conversion_rate_34, t0.country_id AS country_id_35, t0.pref_id AS pref_id_36, t0.discriminator_type FROM dtb_base_info t0 WHERE t0.id = ? AND t0.discriminator_type IN ('baseinfo')"
(parameters:
[1 => 1]
, types:
[1 => 1]
)
doctrine
[
"sql" => "SELECT t0.id AS id_1, t0.company_name AS company_name_2, t0.company_kana AS company_kana_3, t0.postal_code AS postal_code_4, t0.addr01 AS addr01_5, t0.addr02 AS addr02_6, t0.phone_number AS phone_number_7, t0.business_hour AS business_hour_8, t0.email01 AS email01_9, t0.email02 AS email02_10, t0.email03 AS email03_11, t0.email04 AS email04_12, t0.shop_name AS shop_name_13, t0.shop_kana AS shop_kana_14, t0.shop_name_eng AS shop_name_eng_15, t0.update_date AS update_date_16, t0.good_traded AS good_traded_17, t0.message AS message_18, t0.delivery_free_amount AS delivery_free_amount_19, t0.delivery_free_quantity AS delivery_free_quantity_20, t0.option_mypage_order_status_display AS option_mypage_order_status_display_21, t0.option_nostock_hidden AS option_nostock_hidden_22, t0.option_favorite_product AS option_favorite_product_23, t0.option_product_delivery_fee AS option_product_delivery_fee_24, t0.invoice_registration_number AS invoice_registration_number_25, t0.option_product_tax_rule AS option_product_tax_rule_26, t0.option_customer_activate AS option_customer_activate_27, t0.option_remember_me AS option_remember_me_28, t0.option_mail_notifier AS option_mail_notifier_29, t0.authentication_key AS authentication_key_30, t0.php_path AS php_path_31, t0.option_point AS option_point_32, t0.basic_point_rate AS basic_point_rate_33, t0.point_conversion_rate AS point_conversion_rate_34, t0.country_id AS country_id_35, t0.pref_id AS pref_id_36, t0.discriminator_type FROM dtb_base_info t0 WHERE t0.id = ? AND t0.discriminator_type IN ('baseinfo')"
"params" => [1 => 1]
"types" => [1 => 1]
]
debug
Executing query:
"SELECT t0.id AS id_1, t0.point AS point_2, t0.first_order_point AS first_order_point_3, t0.start_time AS start_time_4 FROM plg_entry_point t0"
doctrine
[
"sql" => "SELECT t0.id AS id_1, t0.point AS point_2, t0.first_order_point AS first_order_point_3, t0.start_time AS start_time_4 FROM plg_entry_point t0"
]
deprecation
User Deprecated: Method "Symfony\Component\HttpKernel\KernelInterface::getCacheDir()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Kernel" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "Symfony\Component\HttpKernel\KernelInterface::getLogDir()" might add "string" as a native return type declaration in the future. Do the same in implementation "Eccube\Kernel" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "Symfony\Component\HttpKernel\KernelInterface::registerBundles()" might add "iterable" as a native return type declaration in the future. Do the same in implementation "Eccube\Kernel" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "ArrayAccess::offsetExists()" might add "bool" as a native return type declaration in the future. Do the same in implementation "Eccube\Entity\AbstractEntity" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "ArrayAccess::offsetSet()" might add "void" as a native return type declaration in the future. Do the same in implementation "Eccube\Entity\AbstractEntity" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "ArrayAccess::offsetGet()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "Eccube\Entity\AbstractEntity" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "ArrayAccess::offsetUnset()" might add "void" as a native return type declaration in the future. Do the same in implementation "Eccube\Entity\AbstractEntity" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "Symfony\Component\HttpKernel\Bundle\Bundle::getContainerExtension()" might add "?ExtensionInterface" as a native return type declaration in the future. Do the same in child class "Eccube\EccubeBundle" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "Doctrine\DBAL\Types\Type::convertToDatabaseValue()" might add "mixed" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeType" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "Doctrine\DBAL\Types\Type::convertToPHPValue()" might add "mixed" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeType" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "Doctrine\DBAL\Types\Type::requiresSQLCommentHint()" might add "bool" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeType" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "Doctrine\DBAL\Types\Type::convertToDatabaseValue()" might add "mixed" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeTzType" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "Doctrine\DBAL\Types\Type::convertToPHPValue()" might add "mixed" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeTzType" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Method "Doctrine\DBAL\Types\Type::requiresSQLCommentHint()" might add "bool" as a native return type declaration in the future. Do the same in child class "Eccube\Doctrine\DBAL\Types\UTCDateTimeTzType" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: Since symfony/framework-bundle 5.3: The "session.storage.factory.service" service is deprecated, use "session.storage.factory.native", "session.storage.factory.php_bridge" or "session.storage.factory.mock_file" instead.
User Deprecated: Since symfony/framework-bundle 5.3: The "session.storage.metadata_bag" service is deprecated, create your own "session.storage.factory" instead.
User Deprecated: Method "Monolog\Formatter\FormatterInterface::format()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "EasyCorp\EasyLog\EasyLogFormatter" now to avoid errors or add an explicit @return annotation to suppress this message.
User Deprecated: The "Eccube\Entity\Cart::setTotal()" method will require a new "$total|int" argument in the next major version of its interface "Eccube\Entity\ItemHolderInterface", not defining it is deprecated.