Jump to content

SmartPlugs

Members
  • Posts

    159
  • Joined

  • Last visited

Contact Methods

Profile Information

  • Location
    Marseille
  • Activity
    Agency

Recent Profile Visitors

151,060 profile views

SmartPlugs's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

20

Reputation

  1. Bonjour, Je viens de faire un test sur une version PS 1.7.8.7 (prise au hasard) et sur laquelle les 2 langues sont installées. Quand je supprime le /fr/ de l'url d'une page de catégorie je suis bien redirigé vers la page correspondante en /fr/ grâce au mécanisme redirection canonique... Quelle version de PrestaShop utilises-tu ? Yann
  2. Hi, Is your error related to a "Validation function not found isUrl4Smpl" message ? Yann
  3. Hi, If you get the "Validation function not found isUrl4Smpl", please read this post. Feel free to contact us using the addons page instead of disable the module Yann
  4. Hi guys, As Prestachamps mentionned, if you get the "Validation function not found isUrl4Smpl" you should check first the disable overrides option switched (adances parameters > performances). Your shop might still be in a debug mode and you should try with this option set to "no". Then (if still not working) : On PS 1.7 you should try to empty cache using the button in advanced parameters > performances. Then : You should check if the override/classes/Validate.php file still exists and if it includes the isUrl4Smpl() function. In any case i would recommand you to contact me using the addons page instyead of posting on the forum. I always reply to addons messages. Thanks, Yann
  5. Bonjour à tous, Je suis l'éditeur du module smplredirectionsmanager et je réponds sur ce post pour les besoins de personnes rencontrant éventuellement ce problème à l'avenir. Le module smplredirectionsmanager déclare cette surcharge de la classe Validate pour étendre les fonctionnalités de PrestaShop, la fonction de validation isUrl() native ne prenant pas en charge certains caractères pourtant bien valides. Si vous rencontrez l'erreur "Validation function not found isUrl4Smpl" c'est que votre site PrestaShop n'arrive pas ou plus à lire cette surcharge. La démarche à suivre dans ce cas est : De vérifier (sur PS 1.7) que les surcharges ne sont tout simplement pas désactivées via le back-office dans l'onglet paramètres avancés > performances. Le champ "Désactiver toutes les surcharges" doit être positionné sur "non". De vérifier que la méthode isUrml4smpl est bien présente dans le fichier /override/classes/Validate.php et non commentée. Lors des migrations il peut arriver que les surcharges soient "oubliées". De vider le cache : via le bouton présent en haut de page dans l'onglet paramètres avancés > performances (sur PS 1.7) ou via la suppression du fichier cache /cache/class_index.php (sur PS 1.6). Ces 3 points suffisent à régler le problème dans la majorité des cas. Pour vérifier le bon fonctionnement du module il suffit d'essayer d'ajouter une redirection manuellement. Je vous invite sinon à me contacter directement via le support du module ce qui sera beaucoup plus efficace que de poster dans le forum. Il est vraiment dommage de se priver des fonctionnalités du module pour un problème de ce type et qui sera de toute manière résolu au pire en me contactant. Merci à vous. Yann
  6. Hi Gringeo, If you have any backup, try to restore (on PS 1.6) the /override/classes/Link.php and /override/classes/Dispatcher.php files and then delete all the content relative to Pretty Url in those two files. If you don't have any backup i would first find all the modules that override those 2 files (in this case they also will have a override/classes/Link.php file, same for the 2nd file). And i would then manually add all the overriden methods founded in the main /override/classes/Link.php file (same for Dispatcher). Or you also can try to uninstall/reinstall all the module you will find (but you probably will loose their datas too). Hope it's clear enought...
  7. Hi Sviz, Before uninsatalling Pretty Urls you MUST make à backup of your /override directory. Otherwise it might broke your site. Have a deeper look in the removeOverloadedFiles() methof of pretty url module : it will delete overriden files even if some modules added other methods in them.
  8. Bonjour Juju, Il est le plus souvent impossible (enfin pour moi) de savoir pourquoi un site perd des places, en général on ne se pose pas la question quand il en gagne. As-tu pensé à regarder l'évolution de tes backlinks ? Google ajuste sinon très régulièrement son algorithme ce qui implique à chaque fois des changements dans les résultats. Enfin tout à pour dire qu'il peut exister de nombreuses raisons qui font que l'on plonge "sans avoir rien fais de spécial."
  9. Hi, Here is the behavior you can expect with images according to PrestaShop htaccess "bootstrap" : Il the file exists il will be served and PrestaShop won't even be fired. You can try a request on init.php file : you will get a 500 error that shows the index.php (bootstrap file) is not fired. If the file does not exist the request will be rewriten in index.php and PrestaShop will be fired (and modules as well) In your case, the /img/p/pl.jpg (or en/jpg) file exists and you wont't have any redirect. If you delete this file your redirect should work but i wonder why you don't just replace the img by the one you want (?). Hope it will help. Yann
  10. Hi, {hook h='displayCart'} will display the result of the hookDisplayCart() method of each module hooked on displayCart. You will be able to find them in design > positions. It should be a module provides by your theme as i don't have any hook called "displayCart" on my PS 1.7.4.2. Yann
  11. Hi, I just read in PS 1.7.4.2 code that there's a redirect to index.php?controller=404 on ProductController when the product does not exist. This is quite different of what is done in PS 1.6 that just returns & 404 code and then display an error whitin the product page (controller) and i did not noticed that before. Anyway, i was expecting that putting a die() in the begining of FrontController::init() override should have avoid to be redirected to the 404 page. If i were you i would do some step by step debug to understand what's going on (and if you want to use an override). Using a module hooked on actionDispatcher will allow you to play before the init() method. Pretty urls already override many controllers so ... It's a bit more longer in terms of code but the idea is to build a module (http://doc.prestashop.com/pages/viewpage.action?pageId=51184607). This module should declare that it is hooked on actionDispatcher on his install method !$this->registerHook('actionDispatcher') And then it should have a hookActionDispatcher() method public function hookActionDispatcher($args) { do what you need to do like a redirect or running your own controller } Yann
  12. Hi, As you use Pretty Urls i really would recommand to create a module hooks on actionDispatche Can you try a die('what you want') in the very begining of the init() override just to check if your class override works ? Yann
  13. Hi, Wich version of PS do you use ? Is the rewrite mod enabled ? Yann
  14. Hi, The PageNotFoundController class extends FrontController class. So the init() method in PageNotFoundController is herited from the FrontController one and i would override this one. The override method would be something like public function init() { parent::init(); Your code here Then Redirect to index } The good point with the Dispatcher way is that you wouldn't have to make a redirect (just change the controller). The good one with the FrontController override is that all objects like cart, customer, cookie etc will be already instanciated. There're probably many ways to achieve your project, i just gave the "first" ideas i would have. Yann
  15. Hi, I would achieve that with a module plugged on "actionDispatcher" hook (see Dispatcher::dispatch()). Otherwise with an override (FrontController::inti() as example). Yann
×
×
  • Create New...