Jump to content
Elektroniktradede

HTTP 500 Internal Server Error Fehler bei klick auf Module/Module Manager

Recommended Posts

ich habe einen neuen Shop installiert auf elektroniktrade.de alles funktioniert, nur wollte ich anfangen unter denn Modulen diverse einstellungen zu machen. Nun kommt im Backendbereich bei klick auf Module/Module Manager. http 500 Fehler. Ich habe folgendes in den Logdaten, da verstehe ich aber ein wenig Bahnhof :-) Habe auf true gesetzt, so bekomme ich ein Bug Report, siehe unten.

Type error: Argument 3 passed to JXBlogPostProductsRepository::__construct() must be an instance of PrestaShopBundle\Translation\TranslatorComponent, instance of PrestaShopBundle\Translation\DataCollectorTranslator given, called in /var/www/vhosts/hosting130379.af98e.netcup.net/httpdocs/modules/jxblogpostproducts/jxblogpostproducts.php on line 62

Exception:

Symfony\Component\Debug\Exception\FatalThrowableError

in modules/jxblogpostproducts/src/JXBlogPostProductsRepository.php (line 33)

    private $db;

    private $shop;

    private $db_prefix;

    private $translator;

    public function __construct(Db $db, Shop $shop, Translator $translator)

    {

        $this->context = Context::getContext();

        $this->db = $db;

        $this->shop = $shop;

        $this->db_prefix = $db->getPrefix();

 

LevelChannelMessage

DEBUG20:03:33doctrineSELECT name FROM ps_module WHERE active = 1

INFO20:03:33requestMatched route "admin_module_manage".

DEBUG20:03:33securityRead existing security token from the session.

DEBUG20:03:33securityUser was reloaded from a user provider.

WARNING20:03:34translationTranslation not found.

WARNING20:03:34translationTranslation not found.

WARNING20:03:34translationTranslation not found.

DEBUG20:03:34doctrineSELECT p0_.id AS id_0, p0_.id_employee AS id_employee_1, p0_.id_module AS id_module_2, p0_.date_add AS date_add_3, p0_.date_upd AS date_upd_4 FROM ps_module_history p0_ WHERE p0_.id_employee = ?

WARNING20:03:34translationTranslation not found.

WARNING20:03:34translationTranslation not found.

WARNING20:03:34translationTranslation not found.

WARNING20:03:34translationTranslation not found.

CRITICAL20:03:34phpType error: Argument 3 passed to JXBlogPostProductsRepository::__construct() must be an instance of PrestaShopBundle\Translation\TranslatorComponent, instance of PrestaShopBundle\Translation\DataCollectorTranslator given, called in /var/www/vhosts/hosting130379.af98e.netcup.net/httpdocs/modules/jxblogpostproducts/jxblogpostproducts.php on line 62

INFO20:03:34phpUser Deprecated: Implementing "Symfony\Component\HttpKernel\DataCollector\DataCollectorInterface" without the "reset()" method is deprecated since Symfony 3.4 and will be unsupported in 4.0 for class "Csa\Bundle\GuzzleBundle\DataCollector\GuzzleCollector".

CRITICAL20:03:34requestUncaught PHP Exception Symfony\Component\Debug\Exception\FatalThrowableError: "Type error: Argument 3 passed to JXBlogPostProductsRepository::__construct() must be an instance of PrestaShopBundle\Translation\TranslatorComponent, instance of PrestaShopBundle\Translation\DataCollectorTranslator given, called in /var/www/vhosts/hosting130379.af98e.netcup.net/httpdocs/modules/jxblogpostproducts/jxblogpostproducts.php on line 62" at /var/www/vhosts/hosting130379.af98e.netcup.net/httpdocs/modules/jxblogpostproducts/src/JXBlogPostProductsRepository.php line 33

 

FatalThrowableError

Symfony\Component\Debug\Exception\FatalThrowableError: Type error: Argument 3 passed to JXBlogPostProductsRepository::__construct() must be an instance of PrestaShopBundle\Translation\TranslatorComponent, instance of PrestaShopBundle\Translation\DataCollectorTranslator given, called in /var/www/vhosts/hosting130379.af98e.netcup.net/httpdocs/modules/jxblogpostproducts/jxblogpostproducts.php on line 62 at modules/jxblogpostproducts/src/JXBlogPostProductsRepository.php:33 at JXBlogPostProductsRepository->__construct(object(DbPDO), object(Shop), object(DataCollectorTranslator)) (modules/jxblogpostproducts/jxblogpostproducts.php:62) at Jxblogpostproducts->__construct() at ReflectionClass->newInstance() (src/Core/Foundation/IoC/Container.php:131) at PrestaShop\PrestaShop\Core\Foundation\IoC\Container->makeInstanceFromClassName('jxblogpostproducts', array('jxblogpostproducts' => true)) (src/Core/Foundation/IoC/Container.php:164) at PrestaShop\PrestaShop\Core\Foundation\IoC\Container->doMake('jxblogpostproducts', array('jxblogpostproducts' => true)) (src/Core/Foundation/IoC/Container.php:177) at PrestaShop\PrestaShop\Core\Foundation\IoC\Container->make('jxblogpostproducts') (src/Adapter/ServiceLocator.php:65) at PrestaShop\PrestaShop\Adapter\ServiceLocator::get('jxblogpostproducts') (classes/module/Module.php:1141) at ModuleCore::coreLoadModule('jxblogpostproducts') (classes/module/Module.php:1120) at ModuleCore::getInstanceByName('jxblogpostproducts') (src/Core/Addon/Module/ModuleRepository.php:480) at PrestaShop\PrestaShop\Core\Addon\Module\ModuleRepository->getModule('jxblogpostproducts', false) (src/Core/Addon/Module/ModuleRepository.php:570) at PrestaShop\PrestaShop\Core\Addon\Module\ModuleRepository->getModulesOnDisk(false) (src/Core/Addon/Module/ModuleRepository.php:213) at PrestaShop\PrestaShop\Core\Addon\Module\ModuleRepository->getFilteredList(object(AddonListFilter)) (src/PrestaShopBundle/Controller/Admin/Improve/ModuleController.php:116) at PrestaShopBundle\Controller\Admin\Improve\ModuleController->manageAction() (vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php:151) at Symfony\Component\HttpKernel\HttpKernel->handleRaw(object(Request), 1) (vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php:68) at Symfony\Component\HttpKernel\HttpKernel->handle(object(Request), 1, false) (vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php:200) at Symfony\Component\HttpKernel\Kernel->handle(object(Request), 1, false) (adminde/index.php:86)

 

Share this post


Link to post
Share on other sites

Da ist was falsch im Modul jxblogpostproducts - dieses deaktivieren bzw. falls kein Zugriff im Backend möglich den Modulordner per FTP umbennen. Dann den Entwickler bzgl. des Fehlers kontaktieren.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More