Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by MaXi32

  1. After gone through some testing, I found out that in the latest prestashop 1.7, when you clear cache, the only cache folders that is being used is in /var/cache/* There are 2 folders inside that /var/cache/ called Prod and Dev, If you enable debug mode, the cache folder will go inside /var/cache/dev and if you disable debug, it will go into /var/cache/prod. Also it has been mentioned that prestashop 1.7 doesn't use /cache/* folders: here So, with this information, the solution to delete prestashop cache in prestashop 1.7 manually is to write a script to delete all files inside /var/cache/* and this script can run X time. Search about prestashop cronjob (maybe they have ready module) + how to delete folder in php script.
  2. Believe me. it is possible and I'm not sure if this cache issue has bug or not. and some people are reporting the same thing like this 2GB cache per day: and this person has 11GB cache: this is my old cache folder few months ago which get into the auto backup archived ( 1.6 GB ) if I didn't manually delete it. The latest size is 2.5 GB ++ :
  3. I mean it's worth nothing to delete that folder /cache/* which is not used in prestashop 1.7 but only the /var/cache/*. In my case I have over 2.5 GB cache files .. That's why it's scary to make daily backup to include that 2.5 GB. Thank you so much for helping.
  4. OK I just found the answer about the description of folder /cache/ in Prestashop 1.7. When I go inside that folder /cache/* I saw a text file called deprecated.txt and it says the /cache folder is deprecated. So, it shouldn't be used. Meaning, it's worth nothing to delete:
  5. I just created this script here to detect file changes, so i monitored prestashop folder, within 3 hours right now, when I enable cache together with CCC and when I click clear cache, I can see the only files in folder that are being created and removed are only at this location: 1) /var/cache/ So, this raises my question about the other cache folder that don't have any file activities like: /cache/cachefs/ /img/tmp/ /themes/your_theme/cache/ /cache/smarty/compile/ /cache/smarty/cache/ When do they get generated ? Hopefully someone can describe this for prestashop 1.7.6. what are the folders that can be safely (officially) deleted (which cache or temps folders) ?
  6. Or maybe my brief question for all of the confusing posts above is, what files or folders that can be safely deleted if I want to reduce the size of the prestashop backup.
  7. That is exactly what I don't want you to do. Please do not misunderstand my question. Because all I need is the documentation regarding to simple folder structures that are being deleted like what the other websites are describing like this (this is taken from https://presta.site/blog/en/how-to-clear-prestashop-cache/ : but the above description is not official from prestashop. So, I need the official documentation as end users without having to go through the codes. I understand that source codes are linked to the Symfony cache tool, so I have no time to go through with that, that's the reason I'm requesting a documentation about the folder structure that are being deleted. Maybe prestashop developers know exactly what I mean here. The documentation in the given link doesn't describe in technical about what folders are being deleted.
  8. I can see some other functions like clearSf2Cache in the Tools.php as well, to simplify what your described above to end users without having to go deep into the source code, what are the folder structures that will be deleted? because end users are interested with the documentation. Thank you.
  9. I'm on prestashop, if I click on the clear cache button from the backend, I read from a website here , it said that in prestashop 1.7 I can simply delete /var/cache folder to clear cache but what about the other cache files in /cache/smarty/ ? Then the other website here said, I can delete the following: /cache/cachefs/ /img/tmp/ /themes/your_theme/cache/ /cache/smarty/compile/ /cache/smarty/cache/ But it doesn't say about /var/cache folder. So what is the official description, when I click on clear cache button what files are being deleted in prestashop ? I need this information to create a script to delete the cache folder manually.
  10. I know this is an old thread, but is the clear cache equivalence to removing /var/cache folder? If this is correct then, we can just setup a script to remove /var/cache folder at specific time. No need to make the script as it's not best security practice to send argument to execute php script
  11. If you have mod_security installed in your server, this might be the reason. you need to ask your hosting provider to whitelist rules
  12. A little bit off topic question: How can I check the warning log generated by 1 click upgrade module. Where is the full log file ?
  13. Do you mean ? <-- this is the latest version. and it doesn't compatible with PHP 7.3. Prestashop 1.7.6.* only compatible up to PHP 7.2 where Prestashop 1.7.7 is compatible with PHP 7.3 If you mean the exact version number 1.7.3 then, the version only compatible up to PHP 7.1 as stated in the system requirements. Source: https://devdocs.prestashop.com/1.7/basics/installation/system-requirements/
  14. PHP 7.4 version has been released few months ago and this means that PHP 7.3 is pretty stable. I have my own server and because of Prestashop requirement style, I use multiple PHP installation in my server which I don't really like to do this in term of overall server performance. Because I like everything up to date, in my opinion, PHP 7.2 is outdated and should not be used as today. I like how the wordpress requirements catch up with every latest PHP version. Hopefully that Prestashop do the same thing in the future.
  15. Similar question. The path doesn't exist. I re-add language and delete. This is reproduce-able error. Maybe a bug?
  16. Sometimes you can ignore the ICU check. In my case, I have prestashop and the required ICU is 64.1 but I have ICU 64.2 (the latest). Prestashop doesn't check greater version. I dont think I should downgrade my ICU. I think this should be considered a bug. PHP version came bundled with its own ICU's version. Edited: I think the best way to check system requirement is to use this recommended tool by Prestashop: https://github.com/PrestaShop/php-ps-info/releases This tool is recommended by Prestashop as mentioned in the official documentation: https://devdocs.prestashop.com/1.7/basics/installation/system-requirements/
  17. Sorry for coming to the old post. I don't want to open the new post since this is related and not so important. Is there any side effects on the existing module functioning that can be found so far when resetting the category table to AUTO_INCREMENT=0 ? I can see that some posts recommend to put it as AUTO_INCREMENT=3 (maybe due to prestashop default demo data is set to 3):
  18. Got similar problem with . The link given by @anilkumar36521 is too old and the mail code doesn't exists in the latest Prestashop. Is anyone got solution for ? It has been few days I'm trying to solve this with many solutions given by community. I can confirm there is nothing wrong with my mail server as I can configure the SMTP mail in the other client app like Outlook, Gmail app without any problem.
  19. Not working. Something wrong with the code. The server has perfect configuration that I can use on other client software like outlook roundcube. I'm a server admin.
  20. Tried it. Seems like problem with the cache.
  21. I'm currently using nginx_apache for my webserver and I see that openlitespeed (free) is getting more popular on the net because of its performance. May I know if Prestashop is fully compatible with openlitespeed? Is there any requirements like extra modules in PS that need to be installed when using openlitespeed? Please share your experience.
  22. @Vidar Bjerkeland If you got an HTTP error 500, I would suggest that you enable the debugging mode to find the actual error message. There are 2 ways to enable debugging mode: The first method to enable debugging mode (if you are able to access the back office / admin page) 1) Log into the back office - > Go to Advanced Parameter -> Debug mode 2) Then enable the debug mode -> Yes 3) Save it The second method to enable debugging mode (if you are not able to access the back office / admin page) 1) Go to your root prestashop installation directory and edit this PS config file : /public_html/config/defines.inc.php 2) Using editor with a line number, at the line 29 you will see the following code: /* Debug only */ if (!defined('_PS_MODE_DEV_')) { define('_PS_MODE_DEV_', false); } change the false to true like below: /* Debug only */ if (!defined('_PS_MODE_DEV_')) { define('_PS_MODE_DEV_', true); } 3) Save it. After enabling the DEBUG Then, go back to the page that trigger the blank page or internal error 500. There must be some error messages that will appear and from there you can share the error message for us to help. Another important thing is, if your shop is not ready for live production, then do not enable the cache option at the back end because when u try to make some changes, it might break something like having blank page, cache files that conflicts with another module, etc. I think by default it is enabled. it is not recommend to enable cache setting if the shop is in development status or not ready for live production. Sometimes blank page problem can be problem with the server configuration like file permissions but the common problem in prestashop is due to the the PS cache that needs to be cleared or disabled. Let's say that you are not able to disable the cache option at the backoffice because of the blank page, then you have to manually disable it through mysql database. To disable the cache manually: 1) Go to your SQL database management like phpmyadmin, find the table that says something like PS_CONFIGURATION or *_CONFIGURATION 2) Find a field called PS_SMARTY_CACHE and put the value as 0 and PS_SMARTY_CLEAR_CACHE put the value as everytime 3) Save it and try reload the blank page.
  23. Error 500 can be so many reasons. I think most of them related to your server configuration. You can actually debug it by enabling the debugging mode in Prestashop php config file and you might see some errors that telling you why: define('_PS_MODE_DEV_', true);
  24. If you do care about your customer reputation on your web services, you should consider using SMTP instead of php mail. Read here for more information https://www.jvfconsulting.com/blog/php-mail-function-vs-smtp-guaranteed-delivery/
  25. This has not been fixed for a long time since 2017.. Also happens at version 1.7.6
  • Create New...

Important Information

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