Jump to content

Anto Webcraft

Members
  • Posts

    32
  • Joined

  • Last visited

Everything posted by Anto Webcraft

  1. Cannot access to "Installed modules" in Prestashop 1.7.2.4 (local install) : Blank page, Apache2 log says : AH01071: Got error 'PHP message: PHP Fatal error: Uncaught GuzzleHttp\\Exception\\ServerException: Server error response [url] https://api-addons.prestashop.com?format=json&iso_lang=fr&iso_code=FR&version=1.7.2.4&method=listing&action=categories [status code] 500 [reason phrase] Internal Server Module main page provide : Cannot get catalog data, please try again later. Reason: Server error response https://api-addons.prestashop.com?format=json&iso_lang=fr&iso_code=FR&version=1.7.2.4&method=listing&action=categories [status code] 500 [reason phrase] Internal Server Error Request randomly provide 500 error and I can't manage Installed modules.
  2. Bonjour, Si jamais cela vous intéresse, il est possible de faire un export à partir de l'administration : Paramètres avancés > Gestionnaire SQL : Ajouter une nouvelle requête SQL => Exporter. Voici la requête qui exporte notamment les sous-totaux des produits par règles de taxes (à personnaliser en fonction de votre configuration : d.id_tax_rules_group= XX => ID règle de Taxe / AS `XX` => Nom de la colonne) SELECT a.id_order, a.invoice_number AS `Numéro facture`, a.invoice_date AS `Date facture`, b.firstname AS `Prénom`, b.lastname AS `Nom`, a.total_products AS `Total produit HT`, a.total_products_wt AS `Total produit TTC`, SUM(CASE WHEN d.id_tax_rules_group = 1 THEN d.total_price_tax_excl ELSE 0 END) AS `Sous-total produit HT (20%)`, SUM(CASE WHEN d.id_tax_rules_group = 2 THEN d.total_price_tax_excl ELSE 0 END) AS `Sous-total produit HT (7%)`, SUM(CASE WHEN d.id_tax_rules_group = 3 THEN d.total_price_tax_excl ELSE 0 END) AS `Sous-total produit HT (5.5%)`, SUM(CASE WHEN d.id_tax_rules_group = 4 THEN d.total_price_tax_excl ELSE 0 END) AS `Sous-total produit HT (2.1%)`, SUM(CASE WHEN d.id_tax_rules_group = 5 THEN d.total_price_tax_excl ELSE 0 END) AS `Sous-total produit HT (10%)`, a.total_shipping_tax_excl AS `Total frais de port HT`, a.total_shipping_tax_incl AS `Total frais de port TTC`, a.total_discounts_tax_incl AS `Réduction TTC`, a.total_discounts_tax_excl AS `Réduction HT`, a.total_paid_tax_incl AS `Total payé`, a.payment AS `Moyen de paiement`, c.name AS `Boutique` FROM ps_orders a LEFT JOIN ps_customer b ON (a.id_customer = b.id_customer) LEFT JOIN ps_shop c ON (a.id_shop = c.id_shop) LEFT JOIN ps_order_detail d ON (a.id_order=d.id_order) WHERE a.invoice_number != 0 GROUP BY a.`id_order` ORDER BY `a`.`invoice_date` DESC
  3. Bonjour, Non il n'y a pas de moyen simple de modifier la boutique par défaut d'un produit, mais ces modifications devraient fonctionner sur un prestashop 1.6 : https://github.com/GraalNetwork/PrestaShop/commit/cd7c32c2cec258fe82f4d7f68012b6a510bd9fb2
  4. Up with a solution on ps 1.6, to avoid infinite loop recursion on actionProductSave calling Product->save() (for example) : /modules/mymodule/mymodule.php class MyModule extends Module { /** Only enable one execution per Module instance */ public static $executed = false; [...] public function hookactionProductSave($params){ // Test if hook as has already been executed (as there is only one instance per module in ps 1.6) $executed = Self::$executed; if($executed == true) return // Set executed static property Self::$executed = true; $product = $params[0]['product']; [...] $product->save(); } [...] Be aware that this will only allow this hookactionProductSave() to be executed once.
  5. Hello, What is your Paypal module configuration ? And youre Paypal account options (like PayPal Account Optional = On) ?
  6. Half correct ! You can't set the default shop of a product if it is not associated with the concerned shop but "migrated" is not the correct terme as you can associate Product with shops by saving them in Shop Context. And last, yes it's quite a big thing... for the current project (online soon), the goal is to share carts beetween shops with different domains and different order process. I created two shops in the same group with same catalogs, customers and quantities, I forced "All shops" edition for Products and Categories. The above snippet avoid dupplicate content (as the catalog is shared) by allowing redirection based on id_shop_default.
  7. Bonjour, Déterrage de sujet mais une contribution a été faite dans ce sens : - Edition de la boutique par défaut pour les produits et les catégories - Configuration pour forcer la génération des liens avec l'URLs de la shop par défaut des produits et catégories Pull request faite sur Github : https://github.com/P...aShop/pull/4662 Et si vous souhaitez que ça soit pris en compte pour la prochaine version de Prestashop, vous pouvez voter ici : http://forge.prestas...owse/PSCSX-7540 Bonne journée
  8. Hi everyone, A larger contribution has been made on github with pull request : https://github.com/PrestaShop/PrestaShop/pull/4662 You can vote for it on : http://forge.prestashop.com/browse/PSCSX-7540 It includes : - Admin edit default_shop field for Products and Categories - Configuration var to force default shop URL on link generation for them. Cheers Anto
  9. Bonjour, Je serais disponible immédiatement pour ce projet. Je vous contacte par Message privé pour les questions. Cordialement, Antonin
  10. Salut, Le module m'intéresse pour un projet. Qqun à un retour d'expérience ? Version 1.5 ou 1.6 ? Bonne journée Antonin
  11. You can try to set the correct files/folders permissions with the FTP access : => login on FTP server => select all Prestashop files => change permissions (right click on filezilla > File permissions... ) to 775 = Owner : read/write/execute, Group: read/write/execute, Public:read/execute. => Don't forget to set the recursive option for the changes to be applied in sub-folder/directories, it can take à while... => Select /cache directory : delete class_index.php and the content of /cache/smarty/*
  12. Did you verifiy the correct settings in : - /config/settings.inc.php : _DB_SERVER_ / _DB_NAME_ / _DB_USER_ / _DB_PASSWD_ - /config/defines.inc.php => define('_PS_MODE_DEV_', true); - in phpmyadmin : table : xx_shop_url > domain / domain_ssl / physical_uri - in phpmyadmin : table : xx_configuration > PS_SHOP_DOMAIN / PS_SHOP_DOMAIN_SSL Otherwise you can try to disable overrides and non-native prestashop modules in phpmyadmin : table : xx_configuration : PS_DISABLE_OVERRIDES = 1 / PS_DISABLE_NON_NATIVE_MODULE = 1 Don't forget to clear the class cache by deleting /cache/class_index.php file If nothing works next step should be to reach the apache/php error log to now exactly what's happening.
  13. hI, Did you clear all the cache and set correct permissions ? => login on FTP server => select all Prestashop files => change permissions (right click on filezilla > File permissions... ) to 755 = Owner : read/write/execute, Group: read/execute, Public:read/execute. => Don't forget to set the recursive option for the changes to be applied in sub-folder/directories, it can take à while... => Select /cache directory : delete class_index.php and the content of /cache/smarty/* and apply the same rights to /cache folder with 775 = Owner: read/write/execute, Group:read/write/execute, Public:read/execute (don't forget the recursive option) Cheers Antonin
  14. Hi, Have you tried to clear the cache and reset file permissions ? => login on FTP server => select all Prestashop files => change permissions (right click on filezilla > File permissions... ) to 755 = Owner : read/write/execute, Group: read/execute, Public:read/execute. => Don't forget to set the recursive option for the changes to be applied in sub-folder/directories, it can take à while... => Select /cache directory : delete class_index.php and the content of /cache/smarty/* and apply the same rights to /cache folder with 775 = Owner: read/write/execute, Group:read/write/execute, Public:read/execute (don't forget the recursive option)
  15. Hi ! It's a problem of rights on files. Two options : - 1 - You've got a SSH access to the server with linux:console or windows:putty, after that it depends on the system you're website is running on... - 2 - You've got only FTP access : => login on FTP server => select all Prestashop files => change permissions (right click on filezilla > File permissions... ) to 755 = Owner : read/write/execute, Group: read/execute, Public:read/execute. => Don't forget to set the recursive option for the changes to be applied in sub-folder/directories, it can take à while... => Select /cache directory : delete class_index.php and the content of /cache/smarty/* and apply the same rights to /cache folder with 775 = Owner: read/write/execute, Group:read/write/execute, Public:read/execute (don't forget the recursive option) If it doesn't solve the problem, it should a problem of file/directory owner. Hope this helps. Antonin
  16. Happened to me when improving the tinyMCE editor with this instructions : http://mypresta.eu/en/art/prestashop-16/extended-rich-text-editor.html It's relative path problem with multilang adding /fr/ or /en/ ... at the beginning of the URI : - CMS pages link is ../img/cms/xxx.jpg instead of : ./../img/cms/xxx.jpg Tried to fix it within tinyMCE configuration (./js/admin/tinymce.inc.js for 1.6.0.14) with : relative_urls : false, convert_urls: false, No time to fix tinyMCE so I edited directly the root folder .htaccess file and added the folowing line at the end of # Images block : # Image CMS . RewriteRule ^.*/img/cms/(.*)$ %{ENV:REWRITEBASE}img/cms/$1 [L] nb : don't forget that this fix is placed in autogenerated part of htaccess so any changes of rewrite conf will overwrite this fix. (save it in a comment at the beginning Hope this helps someone ! Anto
  17. En version 1.4.8 : "Bad SubDomain SQL query." Est le résultat de /Classes/Cookie.php $subDomains = SubDomain::getSubDomains(); if ($subDomains === false) die(Tools::displayError('Bad SubDomain SQL query.')); Donc dans /Classes/SubDomain.php if (!$result = Db::getInstance(_PS_USE_SQL_SLAVE_)->ExecuteS('SELECT `name` FROM `'._DB_PREFIX_.'subdomain`')) return false; Donc la requête "SELECT `name` FROM `'._DB_PREFIX_.'subdomain`" ne retourne rien... donc soit la table est absente de la BDD soit la table est vide. Dans mon cas c'était un export incomplet de la BDD source, trop long pour être exporté complétement sur un phphMyAdmin OVH. Dans ce cas, j'ai exporté dans un premier temps la structure de la BDD (Exporter > Personnaliser > Options spécifiques au format : structure). Puis dans un deuxième temps les données mais partiellement : (Exporter > Personnaliser > Options spécifiques au format : données), c'est-à-dire sans le contenu des tables connections, connections_source et guest, qui sont les plus grosses, ne servent pas à grand choses et ne sont jamais vidées par Prestashop. Pour moi c'est une erreur de conception. Est-ce que vous savez si celà a été résolu sur la 1.6 ?
  18. Le plaisir est pour moi Juste pour le référencement du post : Prestashop 1.6.0.9 type de processus de commande standard 5 étapes bug multi transporteur avec envoi différé Prestashop 1.6.0.9 standard checkout bug multi carrier with ship when available Solution here : http://www.prestashop.com/forums/topic/373906-carrier-by-product/
  19. You're welcome ! You can add [solved] to your subject title and by the way rename it by something like : "admin email on checkout/new order" Regards Anto
  20. Hi, You've got a simple module already included in Prestashop (just install it) named Alertes email where you can configure an email notification for new orders sent to the email address you want. For the exact copy of the customer order confirmation email you'll have to override the paymentModule Class to add te desired email address line 762 (ps 1.6.0.9) (comma separated email works ). But be carefull with this as it is an essential Prestashop feature. Cheers, Anto
  21. Il est 8h30 ici Ile de La Réunion. Je peux te faire le transfert (je t'envoie un message en mp, car ce n'est pas le bon forum). Je posterai toutes les étapes dans ce sujet. Que veux-tu dire par "garder l'ancien site" ? Garder l'ancienne URL ?
  22. Bonjour, Il faudrait un peu plus de précisions pour te donner la marche à suivre. - Est ce que tu souhaites conserver l'ancien hebergement ou le fermer (plus facile et rapide si conservation de l'ancien) ? - Quel est le type d'hébergement de l'ancien serveur et du nouveau (dédié, mutualisé...) ? - Quelle est la version du nouveau serveur (OS, version, Apache, IIS) ? - As-tu la main sur la gestion des zones DNS des deux noms de domaines ? - Est-ce que les IDs des produits et pages CMS ont été conservés. Pour tester essaye de coller la dernière partie (URI) des anciennes URL sur le nouveau nom de domaine, voir si cela pointe bien vers la bonne fiche produit sur le nouveau serveur : www.<nouveauNomDeDomaine>.xx/<URIDelAncienNomDeDomaine>, si cela ne marche pas, tu peux déjà commencer un fichier excel de correspondance entre les ancienne URI et les nouvelles pour toutes les pages de ton ancien site. - Quels sont tes connaissance en gestion des zones DNS, administration (simple) de serveur (cas d'un serveur dédié) et fichier htaccess ? - Quelles sont les URLs de l'ancien et du nouveau site Cordialement;
  23. You can add : <br/>{$customer->email} in /override/controllers/admin/templates/orders/helpers/view/view.tpl line : 689
  24. I saw you disabled the cache and the source code shows <link rel="stylesheet" href="/themes/default-bootstrap/css/modules/blocktopmenu/css/superfish-modified.css" type="text/css" media="all" /> So you will be able to modify CSS editing this file
×
×
  • Create New...

Important Information

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