Jump to content

1.4.8.2 Fresh Install Memory_Limit error in Payment Modules


Recommended Posts

Hi Peeps,

 

I'm extremely new to Prestashop and was wondering if someone could shed some light on an issue i'm having.

 

I installed version 1.4.8.2 yesterday the only red flag i got when installing was the magic quotes (recommended) i thought i'd look into this later.

 

In the mean time everything seemed okay until i clicked to see the list of payment modules.

we instantly receive an error:

  1. All the modules cannot be loaded due to memory limit restriction, please increase your memory_limit value on your server configuration

Now the error seemed like an easy fix just edit the config.inc.php file and add the entry: ini_set('memory_limit','128M'); under the heading: /* Improve PHP configuration to prevent issues */

 

I managed to do this without any problems. i got the hosting company to confirm that i did indeed increase the limit to 128M properly. So it leads back to why is it that a fresh install has this issue?

 

I have tried removing all Modules and sticking them in one-by-one but as soon as i get a single payment module activated i get the error message. Google checkout, Money bookers all the same thing. any help would be appreciated. This is my first customer to use an online store and i'm stressing..

 

Cheers

Sam

Edited by LaurimarIT (see edit history)
Link to comment
Share on other sites

Hi Sam,

Who is your hosting provider? Depending on your host's default limits, you might see this error on a fresh install if it is too low, but increasing it as you say you did should fix this.

 

In addition to increasing your memory limit, it can also be helpful to delete via FTP any modules which you have no intention of ever using. Even if they are not listed as Installed in your Back Office, they still occupy some of your server's memory.

 

Once you've done that, you should no longer have this sort of error when activating a module in the latest version of PrestaShop. Can you please post a screenshot of the exact error you are receiving in this situation?

 

-Mike

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...