/ Register

Join the community today
Become a Member

Prestashop CMM beta with Prestashop, good idea ?

Discussion in 'Ecommerce / Shopping cart usage' started by harryneopotter, Jun 10, 2017.

Previous Thread Next Thread
Loading...
  1. Jun 10, 2017 #1
    harryneopotter

    harryneopotter Member

    70
    3
    8
    Aug 16, 2015
    Ratings:
    +8
    Local Time:
    3:55 AM
    Nginx 1.9.3
    MariaDB 10.0
    So the prestashop thread for CMM is quite old. Is it a good idea to use CMM to host a prestashop site (along with varnish/memcached) ? Any pointers on how to go about it ?

    Regards
     
  2. Jun 11, 2017 #2
    buik

    buik “The best traveler is one without a camera.”

    2,026
    524
    113
    Apr 29, 2016
    Flanders
    Ratings:
    +1,674
    Local Time:
    11:25 PM
    No.
    Never use beta software on your money site (webshop and such)
    About caching and such things.

    1. Seems you are preparing a new webshop site.
    Always make sure that you webshop is running perfect.
    After that optimization. Not in reverse order.

    Hint. Create a test schedule so you know exactly what function, option etc. works and what still need some attention.
     
  3. Jun 11, 2017 #3
    eva2000

    eva2000 Administrator Staff Member

    54,107
    12,179
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,739
    Local Time:
    8:25 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    CMM Beta = Centmin Mod 123.09beta01 - AFAIK, it's only beta as I haven't finished updating and writing the official site documentation, faq, guide updates yet. Need to do that before 123.09 stable is released :)

    But it's always good to setup a test server/instance for testing first.
     
  4. Jun 12, 2017 #4
    harryneopotter

    harryneopotter Member

    70
    3
    8
    Aug 16, 2015
    Ratings:
    +8
    Local Time:
    3:55 AM
    Nginx 1.9.3
    MariaDB 10.0
    Yes, I meant to ask, will prestashop work OOB with the default CMM installation or are there any further tweaks/changes required to be done ?
     
  5. Jun 12, 2017 #5
    eva2000

    eva2000 Administrator Staff Member

    54,107
    12,179
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,739
    Local Time:
    8:25 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
  6. Jun 13, 2017 #6
    harryneopotter

    harryneopotter Member

    70
    3
    8
    Aug 16, 2015
    Ratings:
    +8
    Local Time:
    3:55 AM
    Nginx 1.9.3
    MariaDB 10.0
  7. Jun 13, 2017 #7
    harryneopotter

    harryneopotter Member

    70
    3
    8
    Aug 16, 2015
    Ratings:
    +8
    Local Time:
    3:55 AM
    Nginx 1.9.3
    MariaDB 10.0
    Also, any way to redirect all HTTPS traffic to HTTP ? CMM beta.
     
  8. Jun 13, 2017 #8
    eva2000

    eva2000 Administrator Staff Member

    54,107
    12,179
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,739
    Local Time:
    8:25 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    why would you want to do that ? shopping carts and logins should be HTTPS protected as Google Chrome will also give users warning of insecure site if non-HTTPS
     
  9. Jun 13, 2017 #9
    harryneopotter

    harryneopotter Member

    70
    3
    8
    Aug 16, 2015
    Ratings:
    +8
    Local Time:
    3:55 AM
    Nginx 1.9.3
    MariaDB 10.0
    well, dont ask me. That is how the client wants it. Also, need to this for a personal blog as well. so any pointers ?
     
  10. Jun 13, 2017 #10
    eva2000

    eva2000 Administrator Staff Member

    54,107
    12,179
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,739
    Local Time:
    8:25 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Just don't setup HTTPS to begin with if the site vhost isn't created yet.

    Otherwise if already HTTPS, just do reverse of http to https redirects posted at centminmod.com/nginx_domain_dns_setup.html#httpsredirect

    key to testing is using 302 temp redirect first in a private incognito browser session otherwise the problems you can experience may end up being due to browser caching or 301 permanent redirects unless you clear browser cache and reboot local computer(s) and even then some web browsers don't let go of 301 permanent redirect browser cache that willingly :)
     
Previous Thread Next Thread
Loading...

.