Perch and php.ini file

    I get this error in my Perch portal under diagnostics:

    Memory limit is low. Memory use is limited to -9.5367431640625E-7M, which could cause problems manipulating large images.


    I don't think it is a big issue, but thought I would increase my server memory for it through my php.ini file as it may solve my other issues.


    However, when i upload a php.ini file, I get a load of error messages above each page:

    Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/htdocs/team.php:1) in /homepages/30/htdocs/perch/core/lib/PerchUtil.class.php on line 1405
    Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/htdocs/team.php:1) in /homepages/30/htdocs/perch/core/lib/PerchUtil.class.php on line 1406
    Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/htdocs/team.php:1) in /homepages/30/htdocs/perch/core/lib/PerchUtil.class.php on line 1407
    Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/htdocs/team.php:1) in /homepages/30/htdocs/perch/core/lib/PerchUtil.class.php on line 1415
    Warning: session_set_cookie_params(): Cannot change session cookie parameters when headers already sent in /homepages/30/htdocs/perch/addons/apps/perch_shop/lib/PerchShop_Session.class.php on line 14
    Warning: session_start(): Cannot start session when headers already sent in /homepages/30/htdocs/perch/addons/apps/perch_shop/lib/PerchShop_Session.class.php on line 15
    Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/htdocs/team.php:1) in /homepages/30/htdocs/perch/addons/apps/perch_shop/lib/PerchShop_Session.class.php on line 34


    The only line i have in my php.ini file is: memory_limit = 512M


    Is there another way around this, or should I not worry?


    Cheers,

    Sam

  • drewm

    Approved the thread.

    You don't need to worry so much about the memory error, as long as you know there's sufficient memory configured. For some reason, your installation is reporting an unexpected memory value back to PHP, so the calculations go a bit squiffy.