Jump to content

esmDanhost

Members
  • Content count

    2
  • Joined

  • Last visited

About esmDanhost

  • Rank
    PrestaShop Newbie

Recent Profile Visitors

39 profile views
  1. We have experienced this error with non-superadmin employees in version 1.7. A fix seems to be to add access for the following authorization roles to the employee profile in question, in the 'access' table: - 'ROLE_MOD_TAB_ADMINMODULES_CREATE' - 'ROLE_MOD_TAB_ADMINMODULES_READ' - 'ROLE_MOD_TAB_ADMINMODULES_UPDATE' - 'ROLE_MOD_TAB_ADMINMODULES_DELETE' In practice this meant adding four rows to the 'access' table in the database, with data like this: - id_profile = 2, id_authorization_role = 165 - id_profile = 2, id_authorization_role = 166 - id_profile = 2, id_authorization_role = 167 - id_profile = 2, id_authorization_role = 168 This can also be expressed with the following SQL query, where 'Shop owner' is the name of the profile in question: SELECT `id_authorization_role` INTO @create_role FROM `authorization_role` WHERE `slug`='ROLE_MOD_TAB_ADMINMODULES_CREATE'; SELECT `id_authorization_role` INTO @read_role FROM `authorization_role` WHERE `slug`='ROLE_MOD_TAB_ADMINMODULES_READ'; SELECT `id_authorization_role` INTO @update_role FROM `authorization_role` WHERE `slug`='ROLE_MOD_TAB_ADMINMODULES_UPDATE'; SELECT `id_authorization_role` INTO @delete_role FROM `authorization_role` WHERE `slug`='ROLE_MOD_TAB_ADMINMODULES_DELETE'; SELECT `id_profile` INTO @profile_id FROM `profile_lang` WHERE `name` = 'Shop owner' LIMIT 1; INSERT IGNORE INTO `access`(`id_profile`,`id_authorization_role`) VALUES(@profile_id,@create_role); INSERT IGNORE INTO `access`(`id_profile`,`id_authorization_role`) VALUES(@profile_id,@read_role); INSERT IGNORE INTO `access`(`id_profile`,`id_authorization_role`) VALUES(@profile_id,@update_role); INSERT IGNORE INTO `access`(`id_profile`,`id_authorization_role`) VALUES(@profile_id,@delete_role);
  2. Prestashop 1.7 Backoffice 404 Error

    We had the same problem on our hosting, which seemed to arise because of a misconfiguration of Apache when using php-fpm. Implementing the proposed fix in: https://www.prestashop.com/forums/topic/519123-config-prestashop-17-and-nginx/ in our Apache config, seems to have fixed the 404 error. Because we use PHP-fpm som ajustment had to be made to our Apache config. We had the following LocationMatch in our config: <LocationMatch ^(.*\.php)$> ProxyPass fcgi{colon}{slash}{slash}127.0.0.1:9000/data/prestashop$1 enablereuse=on </LocationMatch> This breaks symfony urls, but was simply fixed by inserting the following instead: <LocationMatch ^(.*\.php)> ProxyPass fcgi{colon}{slash}{slash}127.0.0.1:9000/data/prestashop$1 enablereuse=on </LocationMatch> Note that the forum spamfilter removes parts of the config when posted in its entirety. Please replace ' {colon} ' with ' : ' and ' {slash} ' with ' / '. Then apache will proxy the Symfony requests, with characters after .php, on to php-fpm.
  3. [config] PrestaShop 1.7 and nginx

    The same problem can occur when using apache and php-fpm, we had the following LocationMatch in our apache configuration: <LocationMatch ^(.*\.php)$> ProxyPass fcgi{colon}{slash}{slash}127.0.0.1:9000/data/prestashop$1 enablereuse=on </LocationMatch> Which also breaks the Symfony urls, the fix is simple though, change it to: <LocationMatch ^(.*\.php)> ProxyPass fcgi{colon}{slash}{slash}127.0.0.1:9000/data/prestashop$1 enablereuse=on </LocationMatch> Note that the forum spamfilter removes parts of the config when posted in its entirety. Please replace ' {colon} ' with ' : ' and ' {slash} ' with ' / '. Then apache will proxy the Symfony requests, with characters after .php, on to php-fpm.
×