Jump to content

tomerg3

Global Moderators
 View Profile  See their activity

  • Posts

    6,627

  • Joined

  • Last visited

  • Days Won

    17

tomerg3 last won the day on February 13 2022

tomerg3 had the most liked content!

20 Followers

See all followers

About tomerg3

Profile Information

  • Activity
    Agency

Recent Profile Visitors

58,947,179 profile views

tomerg3's Achievements

Apprentice

Apprentice (3/14)

  • Conversation Starter Rare
  • Very Popular Rare
  • First Post Rare
  • Collaborator Rare
  • Posting Machine Rare

Recent Badges

636

Reputation

8

Community Answers

  1. B3yond started following tomerg3
  2. tomerg3
    I'm not quite sure what is the issue here, should it not collect payment, or is it supposed to be in a different place? To be sure if it is coming from the payment module or not, try to disable the payment module and reload the page.
  3. tomerg3
    I'd like to add on point #2, if you mean 130k products, you may experience slowness in PS 1.7. While I have not personally tried using PS 1.7 with such a high number of products, I have seen several reports of people with over 50k products experiencing slow speeds.
  4. tomerg3
    Great, we're glad to hear it's working for you. We also have other useful modules that work
  5. tomerg3
    I suggested twice to check the php version, I'm glad you found that out.
  6. tomerg3
    You should check the PHP version of the new server, and make sure it is compatible with your version of PrestaShop. You can also look for an error_log file in the root directory of PrestaShop, and see if it exists and has more insight.
  7. tomerg3
    Can you access the backoffice? If so, try to regenerate the htaccess file from there. You should check the PHP version of the new server, and make sure it is compatible with your version of PrestaShop. You can also look for an error_log file in the root directory of PrestaShop, and see if it exists and has more insight.
  8. tomerg3
    Try to turn on the browser console (Usually F12), click the network tab, run the transaction again, and look at the response from the last file that's called. It seems that some text might be outputted that is preventing PS from properly processing the response
  9. tomerg3
    This module should help you save some time https://www.presto-changeo.com/prestashop-17-modules/147-prestashop-mass-combination-editor-module.html
  10. tomerg3
    You can also check out Attribute Grid https://www.presto-changeo.com/prestashop-17-modules/122-prestashop-attribute-grid-module.html
  11. tomerg3
    If it works with friendly URL turned off, but doesn't wok when it's turned on, then it is a server issue (double check you are not using Nginx), and make sure your htaccess file is writeable.
  12. tomerg3
    I started a new thread for this question, as it is not really related to the speed tips, but rather an issue with a module. I suggest you contact the module developer and ask them about this. You can also try to modify the code your posted so it only displays for ContactController and remove the other conditions.
  13. tomerg3
    You may need to clear the cache in the Performance page
  14. tomerg3
    1) Check with your hosting provider if you use Nginx. 2) Ask them for help. 3) Ask Google about Nginx and URL rewrite
  15. tomerg3
    Check with your hosting provider, if you server is using Nginx, then you need to so something extra to use friendly URLs.
  16. tomerg3
    It's generally good not to use too much memory, as it can lead to high server use during a potential attack. With that said, PrestaShop can sometimes use a lot of memory, especially in backoffice functions. You can set one limit for the main site, and another to the /admin folder you use, which is higher if you need. Did you run into any memory issues? For most front ends, 256, and definitely 512 should be enough.
×
×
  • Create New...