Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/11/2019 in all areas

  1. When you start generating your images with the unique WebP Generator module, you can obtain significant improvements to the speed of your site. Images in WebP format are also recommended during a PageSpeed Insights and Google Lighthouse audit so they will help you obtain better results there and in consequence have a positive effect on the rankings of your pages. WebP is a a modern image format developed by Google, that ensures superior lossless and lossy compression for images on the web. It uses algorithms which greatly reduce the file size while keeping the quality of the original image. Images size is reduced by 25-30% while maintaining the high quality of the original file Generating images in the new format is more effective than the standard image generation in PrestaShop. The page load time on your site will become faster and this process can also free up space on the server. With our module you can generate Product Images, Category Images, Supplier Images, Store Images, Manufacturer Images. The module is now available on the Addons Marketplace for PrestaShop 1.6 and 1.7: https://addons.prestashop.com/en/visual-products/42715-webp-image-generator.html Besides the technical part, we have also made a few usability improvements compared to the standard image generator in PrestaShop: We have implemented a progress bar where you can see generation process in percentages for each types of images separately. Next to each image type the total number images is also displayed. At the same time, we know the frustration the old image generator caused with its series of repeated time-outs so we made sure that all the images are generated without any errors and without requiring a user to monitor the process, reload the page after a time-out and re-initiate the process. Both Google and your customers will love your images which are generated by this module. Our module will help you to obtain better rankings in Google Image Searches. This is additional to the general improvements in rankings thanks to having a fast site. Below you can see, on the left, the recommendation offered by Google Lighthouse to use WebP for images and on the right a graph showing the reduction in file size obtainable with WebP images. With the recent PageSpeed Insights Update which changed the game completely when it comers to performance metrics, we believe it is vital to add this module as quickly as possible and start generating your images in a format suitable for the year 2019! Stop generating your images with the standard image generator! It is just wasted time while you can try the new technology developed by Google and the results will amaze you. More information as well as server requirements are found on the module's page on PrestaShop Addons: https://addons.prestashop.com/en/visual-products/42715-webp-image-generator.html If you have any questions or are looking for any specific information, write your reply below and we are more than happy to answer. We welcome all feedback from the community and appreciate any suggestions which will help us improve and update the module. As it is being developed continuously, new feature suggestions are very welcome.
    1 point
  2. No estoy seguro, pero ¿eso no se cambia desde "internacional/localizacion", en la pestaña "idiomas", seleccionando el idioma que queiras modificar y cambiando el campo "codigo iso"?
    1 point
  3. Tienes un problema en el módulo Paypal. Renombra la carpeta /modules/paypal para que puedas entrar en el backoffice.
    1 point
  4. Hello everyone, I want to share my case with you, I know there are many people who are pulling their hair trying to solve this problem. When I install the prestashop on my private server, I start having Error 500 and it does not show some images in the frontend or in the back office. when I change the permission to the folders to 777 by FTP FileZilla everything works fine. I reinstall the store 5 times getting the same error. let's start with the 500 Error, as many post say it can be for many problems, in my case permission to write on folders, how to know what is wrong, well you need to find the Apache log in my case was in apache2->logs->error.log. You will be able download the file if your FTP user have permission to see the Apache installation folder, if you don´t contact you service provider. once you have the error.log, open it with wordpad and go to the last line, you will see something like this: [Thu Jan 10 14:29:58.021200 2019] [proxy_fcgi:error] [pid 30320:tid 140432560768768] [client xxxxxx:50400] AH01071: Got error 'PHP message: PHP Fatal error: Uncaught UnexpectedValueException: The stream or file "xxxxxx/apache2/htdocs/xxxx/var/logs/prod.log" could not be opened: failed to open stream: Permission denied in xxxxxx/apache2/htdocs/xxxxxx/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:107\nStack trace:\n#0 xxxxxx/apache2/htdocs/xxxxxx/vendor/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(39): Monolog\\Handler\\StreamHandler->write(Array)\n#1 xxxxxx/apache2/htdocs/xxxxxx/vendor/monolog/monolog/src/Monolog/Handler/AbstractHandler.php(59): Monolog\\Handler\\AbstractProcessingHandler->handle(Array)\n#2 xxxxxx/apache2/htdocs/xxxxxx/vendor/monolog/monolog/src/Monolog/Handler/FingersCrossedHandler.php(99): Monolog\\Handler\\AbstractHandler->handleBatch(Array)\n#3 xxxxxx/apache2/htdocs/xxxxxx/vendor/monolog/monolog/src/Monolog/Handler/FingersCrossedHandler.php(120): Monolog\\Handler\\FingersCrossedHandler->activate()\n#4 xxxxxx/apache2/htdocs/xxxxxx/...\n', referer: http://xxxxxx/adminxxxxxx/index.php?controller=AdminLogin&token=xxxxxx&redirect=AdminThemes to see if it is a permission problem with the folder just to try change it to 777 (remember all folders most have 755 and file 644), refresh the page where you are getting the 500 and you should be able to see it, if you don't please repeat the last step and check the new error. in my case I granted write public permission to logs/prod.log both folder and file and then the store (PrestaShop) wrote on the log prod.log the error which was: [2019-01-10 12:24:20] request.CRITICAL: Uncaught PHP Exception Symfony\Component\Filesystem\Exception\IOException: "Failed to create "xxxxxxxx/apache2/htdocs/xxxxxxxx/config/themes/xxxxxxxx": mkdir(): Permission denied." at xxxxxxxx/apache2/htdocs/xxxxxxxx/vendor/symfony/symfony/src/Symfony/Component/Filesystem/Filesystem.php line 104 {"exception":"[object] (Symfony\\Component\\Filesystem\\Exception\\IOException(code: 0): Failed to create \"xxxxxxxx/apache2/htdocs/xxxxxxxx/config/themes/xxxxxxxx\": mkdir(): Permission denied. at /xxxxxxxx/apache2/htdocs/xxxxxxxx/vendor/symfony/symfony/src/Symfony/Component/Filesystem/Filesystem.php:104)"} [] the store can not create a directory on the custom theme, so I allow 777 permission to the custom theme folder and vuala!!! it works! After 2 days of searching, here is the solution. until now we know that is a permission issue on the prestashop folder. a folder have permission (write and read) for groups, owner and public (777 for write on all) and also has an owner and group owner. if the owner of the folder it is not the same as the user running the apache service on the server you will get 500 error, access denied, not authorize, etc... when we granted 777 to the folder it works because for the system the user running the apache service is consider a public access as it does not own the folder. how to solve it: first we need to know who it the user running the apache service by SSH console in the server, log in as a root an run apachectl -S this will give you all virtual host that you server is listen to and at the end you will find this: User: name="xxxxxx" id=xx Group: name="xxxxxx" id=xx once we have the user we assign the ownership to the PrestaShop folder by using this: chown -R user:group psfolder to check if the changes are made run ls -ld psfolder and you will see something like this: drwxr-xr-x 2 user group 4096 Dec 26 21:20 psfolder the word user and group change it for the user and group name running the apache and the psfolder for the presta shop folder done, if you run your store, everything should work, if it does follow these next step, if it doesn't go back to the troubleshooting and keep checking the logs for the next error change the permission of the PrestaShop folders, subfolders and files by: find folder -type d -exec chmod 755 {} \; find folder -type f -exec chmod 644 {} \; this should be all for the 500 and access denied then if you server is using Page Speed you will see this error on the error.log of the apache and some image won't load on the front end and back office [Thu Jan 10 14:30:13.696250 2019] [authz_core:error] [pid 30320:tid 140432344282880] [client xxxxx:50405] AH01630: client denied by server configuration: uri /img/70x119xpreston-login,402x.png.pagespeed.ic.7FV9FO9pvj.webp, referer: http://xxxxx/adminxxxxx/index.php?controller=AdminLogin&token=xxxxx as you can see is trying to load .webp image that does not exist on the folder but it is generating as the page is load. the problem is in the .htaccess on the psfolder->img that does not contemplate this Google image file, to solve the problem edit the .htaccess and change the line <Files ~ "(?i)^.*\.(jpg|jpeg|gif|png|bmp|tiff|svg|pdf|mov|mpeg|mp4|avi|mpg|wma|flv|webm|ico)$"> for <Files ~ "(?i)^.*\.(jpg|jpeg|gif|png|bmp|tiff|svg|pdf|mov|mpeg|mp4|avi|mpg|wma|flv|webm|ico|webp)$"> Now is all set, I hope this helps many people that have this issue. ENJOY!! Update!! Page Speed and prestashop is having some problem, some time image shows some time does not, so I disable Page Speed and configure Varnish with this file: https://github.com/nexylan/varnish-prestashop All good now, actually it works faster!!
    1 point
  5. Dag Janssen, Het zou kunnen dat het 1 van deze 2 oorzaken zijn: 1. De regel 'inclusief belasting' komt vaker voor, en moet dus ook vaker aangepast worden. 2. Je shop is gecached (geavanceerde instellingen->prestaties knop rechtsboven 'cache legen') Hoor graag of dit je oplossing was!
    1 point
  6. This is template \themes\classic\templates\customer\authentication.tpl. You could remove link. But you also should block "/login?create_account=1".
    1 point
  7. The LiteSpeed Cache plugin does require a LiteSpeed Web Server license with the LSCache module. There are several different licenses available, though, including one free option. Here is more info: https://www.litespeedtech.com/products/litespeed-web-server/lsws-pricing Or, ask your web host about LiteSpeed. Many of them offer it as an option.
    1 point
  8. Quizás es mejor, en vez de lo que hemos intentado hasta ahora, es esto: Elimina lo que hemos puesto antes y añade esto header .nav .header_user_info,.shopping_cart_area,header .nav .search_block_top { z-index: 2; position: relative; } .block_top_menu{ z-index: 1; } Esto hace que la capa de menu este por debajo de los iconos, por lo que no estorba
    1 point
  9. I think so... the description reads: "A 2-CPU trial license with LSCache module is available for free for 15 days. "
    1 point
  10. Essa mensagem está sendo exibida porque nenhuma dessas opções é a combinação padrão do produto. Para isso você deve definir essa combinação padrão em todos os produtos que apresentarem essa mensagem. Outra forma mais simples de "contornar" é alterando a tradução dessa informação. Você pode colocar algo como: "Selecione uma outra combinação. A combinação escolhida está indisponível no momento."
    1 point
  11. 1) Configuring CSS for the child theme in theme.yml Applying indents to the assets tree solved my problem Change assets: use_parent_assets: true css: all: - id: custom-lib-style path: assets/css/custom-lib.css For this assets: use_parent_assets: true css: all: - id: custom-lib-style path: assets/css/custom-lib.css js: all: - id: owl-carousel-lib path: /assets/js/owl.carousel.js priority: 100 position: bottom Clean the cache. (PrestaShop version: 1.7.2.4)
    1 point
  12. I found the issue. In the default theme, there is a blocksearch module. This module uses the old JQuery autocomplete plugin loaded via: $this->context->controller->addJqueryPlugin('autocomplete'); Which expects JS in this form: $("#my_cities").autocomplete(["ooo1", "ooo2", "ooo3"]); Of course, when I then try to load the newer JQueryUI autocomplete, they conflict. I replaced the above line with: $this->context->controller->addJqueryUi('ui.autocomplete'); Which expects JS in this form: $("#my_cities").autocomplete({source: ["ooo1", "ooo2", "ooo3"]}); to test an it all worked! Of course, that breaks the blocksearch module, as I would have to port its code to use the new autocomplete. So for now, I will just stick to the old plugin and JS format.
    1 point
  13. prestashop product pages requires this param to properly identify the product's attributes change. without the id of attribute in the url it is not possible to identify the selected combination, so in effect the combination selector will not work properly. this is how the prestashop is developed and how it works, its not an issue The only one way to remove the id of product / id of attribute or both of them is a module that removes id numbers from urls. But before you will decide to order this kind of addon you have to be sure that module supports prestashop 1.7 well, like mine pretty clean urls.
    1 point
  14. Aquí: https://mypresta.eu/basic-tutorials/cms-fancybox-gallery-prestashop-16-17.html tienes una guía de Vekia para la 1.6 de Prestashop y creo que es lo que quieres. Añado que Vekia tambien tiene una guía para la 1.5. Otra opción: https://www.prestashop.com/forums/topic/310597-free-module-sliders-everywhere-responsive-gallery-image-sliders-or-banners-now-3d/ (aunque creo que no es lo que quieres)
    1 point
  15. Thank you for this usefull information. It solved my problem.
    1 point
  16. I have Prestashop 1.5.5.0 and none of these solutions have worked for me. In my case it's not possible to upgrade to 1.5.6 because the theme is not compatible. After trying tens of .htaccess combinations, file changes in classes/tools.php and any other different solutions provided or the ones I figured out, normally ending in redirection loops in the browser or other errors, this is the one that has worked for me in ******PRESTASHOP 1.5.5.0 **********/, so I leave it here in case it might help someone: 1. Enable SSL in Settings > General. With this we will be able to go through ssl for cart, order, authentication, account, payment, etc. pages. But of course not for the rest of pages (index, categories, products, etc.) 2. Edit /classes/controller/FrontController.php by changing public $ssl = false; to public $ssl = true; With that you will be able to go through https for most of your shop, however category and product pages will NOT go through https. 3. The next obvious step is to go to /controllers/front/CategoryController.php and /controllers/front/ProductController.php and force the ssl on them by adding public $ssl = true; in their class variables. We have to do it, however at this point neither category nor product pages will work at all, resulting in redirection loop. To finally solve this: 4. Go to your back office > Preferences > SEO and URLs, and check "No" for Redirect automatically for main link (canonical URL). Save. Now category and product pages will work too. 5. (Optional) You can also check "Yes" for Friendly URLs. They will work smoothly. After two days struggling with this, this is the solution that has let me force SSL / HTTPS for all my shop's pages.
    1 point
  17. You can change product add date (product update date also) in the database open ps_product * ps_product_shop tables you've got there: change values of these fileds. Optionally you can use my commercial module product date change it allows to change the date_add and date_Upd of product in a handy way, directly from shop back office.
    1 point
  18. Hola a todos, encantado de estar aquí. Soy nuevo y esto intentando crear una tienda online. Pero mis conocimientos en prestashop son cortitos y sudo cada vez que abro mi trastienda :S Saludos y abrazos!
    1 point
×
×
  • Create New...

Important Information

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