Jump to content

Edit History

Marz12

Marz12


detail

New test:

according to

setting PS_DISABLE_NON_NATIVE_MODULE to 0 in table ps_configuration was the only way to get back non native modules. It is a mystery since

- PS_DISABLE_NON_NATIVE_MODULE had always been set to 1 on older Prestashop versions

- the upgrade was performed with the option "disable non native modules" set to NO.

At first, this generates a new error:

Unable to generate a URL for the named route "admin_addons_login" as such route does not exist.

and the connection to the back office is not possible. According to https://github.com/PrestaShop/PrestaShop/issues/30979 we renamed the module psaddonsconnect into something else such as old_psaddonsconnect (that is to say, uninstall it).

and things seem to be OK: payment module and other non native modules are back.

Marz12

Marz12

New test:

according to

setting PS_DISABLE_NON_NATIVE_MODULE to 0 was the only way to get back non native modules. It is a mystery since

- PS_DISABLE_NON_NATIVE_MODULE had always been set to 1 on older Prestashop versions

- the upgrade was performed with the option "disable non native modules" set to NO.

At first, this generates a new error:

Unable to generate a URL for the named route "admin_addons_login" as such route does not exist.

and the connection to the back office is not possible. According to https://github.com/PrestaShop/PrestaShop/issues/30979 we renamed the module psaddonsconnect into something else such as old_psaddonsconnect (that is to say, uninstall it).

and things seem to be OK: payment module and other non native modules are back.

×
×
  • Create New...