Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by MaXi32

  1. 7 hours ago, Guest said:

    Deleting content (subfolders and files) from ./var/*, ./cache/*, ./img/tmp/* folders reduces it by a maximum of 50 MB (4000 products).

    Other folders must be kept.

    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:



  2. 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:


    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) ?

  3. 15 minutes ago, Guest said:

    I will definitely not write all the documentation, I am not a paid developer of Prestashop.
    Unfortunately, it is not possible to describe all functions in the official documentation

    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.


    16 minutes ago, Guest said:

    Describe everything you need is a few pages.



    The documentation in the given link doesn't describe in technical about what folders are being deleted.

  4. 24 minutes ago, Guest said:

    Find functions in:




    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.

  5. 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:


    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.

  6. On 2/13/2020 at 4:20 PM, KingBirds said:

    Is prestashop 1.7.3 now working with php 7.3?

    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/

  7. 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.

  8. 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. 




    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/

  9. 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): 



  10. 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.

  11. On 5/2/2017 at 2:09 AM, bijou10 said:

    I had same problem I tried all for days,

    just solved like this:



    mail domain server:  smtp .yourdomain.com  (in my case mail.mydomain.com  check you email configuration in your cpanel)

    smtp server:   smtp .yourdomain.com


    I left blank user name  and pasword,

    SSL ( need enable SSL in Preferences General)



    and your store contact must be your domain email

    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.

  12. 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.

  13. @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.

    • Like 1
  14. On 8/14/2019 at 12:53 PM, renegades said:

    Good question. I'd ask the same. Funny there isn't an answer to it. It's not funny anymore.

    Try to install 1.7.6 since yesterday and get 500 error. No (informative) message. Nothing in the server error report, nothing. To be honest, the over-complication just to install that thing, paired with the lack of support here at Prestashopthat, it puts me off. I need a shop, not a never-ending nightmare.

    Waiting for the forum administrator to ban me for speaking out by addressing facts 😅.

    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);

  15. I never used docker but have experienced using vagrant as my main website development for many years but I just stopped there. I know vagrant and docker, the concept still the same. Do not over obsessed with the purpose of this technologies. They are not developed to make your development easy but the point is to make the testing environment better by working with team. Normally if you work with team, you need to use docker or you gonna have miscommunication. So the other people can test your work without asking you "what do I need to run this thing" and you wasted a lot of time for setting up the same environment? if you are like me working alone, I just use private git repo + ftp push. You don't need docker.

    Normally this is what I do without docker or vagrant. Only do this if you don't share your server configuration with other team:

    1) Create a random dev subdomain for testing purposes like dev.mywebsite.com, install prestashop in here with the database dev_prestashop. You can put more tests in the same server like dev2.mywebsite.com, dev3.mywebsite.com. So the dev.mywebsite.com is like a beta version of the live site in www.mywebsite.com

    2) Secure this dev.mywebsite.com with httpd or nginx password and only you and your team can access this

    3) Now create an empty git repository inside this directory and push as a new repo at your git online repo (I choose my own hosted gitlab svn.mywebsite.com)

    4) Now you have the test server with the same configuration as live server and git-able with your team! The reason I don't see the need of Docker.

    So, how do you update changes to live production on www.mywebsite.com? What about the database? Here is how I did it:

    1) in the public_html for my dev.mywebsite.com, I created a new folder that stores prestashop sql files -> public_html/mydb/ . Then, I dump the sql file without zip or gz compression (eg. dev-prestashop.sql) so I can detect changes from my private git.

    2) If let say I want to commit the dev project, I have to set a rule that I always need to copy a new database inside the directory so it will be synced.

    3) Then, for the live production, I can just pull it from the dev repository and make changes there


  • Create New...

Important Information

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