<?xml version="1.0" encoding="UTF-8"?>    <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
      <channel>
        <title>Having trouble with uploads: Fatal Error</title>
        <link>https://interactivetools.com/forum/forum-posts.php?Having-trouble-with-uploads-Fatal-Error-79548</link>
        <description></description>
        <pubDate>Tue, 17 Mar 2026 09:30:04 -0700</pubDate>
        <language>en-us</language>
        <atom:link href="https://interactivetools.com/forum/forum-posts.php?rss=1&amp;Having-trouble-with-uploads-Fatal-Error-79548" rel="self" type="application/rss+xml" />

                <item>
          <title>Having trouble with uploads: Fatal Error</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2234108#post2234108</link>
          <description><![CDATA[<p>Steve,</p>
<p>Thanks for taking the time to reply and sharing the article with me. It makes sense... I was able to finally get things going. I was resizing the photo (CMSB section editor upload) down to Max H 960 X Max L 960 and it wasn't until I changed that setting to 1600 X 1600 along with changing memory in php-ini on the web server that the fatal error went away. </p>
<p>Kevin</p>]]></description>
          <pubDate>Wed, 04 Jun 2014 14:12:39 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2234108#post2234108</guid>
        </item>
                <item>
          <title>Having trouble with uploads: Fatal Error</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2234104#post2234104</link>
          <description><![CDATA[<p>Hi Kevin,</p>
<p>File size itself doesn't directly equal the amount of memory needed. The factor here is the image resolution. </p>
<p>The most straight forward article I've seen on this topic regarding the GD library and memory: <br /><a href="http://alexrabe.de/2008/05/13/understand-gd-library/" rel="nofollow">http://alexrabe.de/2008/05/13/understand-gd-library/</a></p>
<p>Here is a recent example I used with a client of ours. Let's say you have a photo that is 4.3MB file size, but the resolution actually equates to 5,920 x 7,714. This would actually translate to over 130MB of memory needed. </p>
<p>In photo editing programs such as Photoshop, you can see the sizes in the bottom of the window (generally displayed like this: 4.3MB/130MB).</p>
<p>Hope this helps.</p>
<p>Best,<br />Steve</p>]]></description>
          <pubDate>Wed, 04 Jun 2014 13:04:29 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2234104#post2234104</guid>
        </item>
                <item>
          <title>Having trouble with uploads: Fatal Error</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2234088#post2234088</link>
          <description><![CDATA[<p>I am having trouble with uploads and am getting a Fatal error. Allowed memory size of 134217728 bytes exhausted (tried to allocate 15364 bytes in /home/kevbarker/raingonc.com/admin/lib/image_functions.php on line 100.</p>
<p>Server Upload Limits are as follows</p>
<p>max_input_time: -1<br />post_max_size: 100M<br />upload_max_filesize: 100M</p>
<p>The photo I was trying to upload: (just one photo ) is 6.74 MB</p>
<p>Shouldn't the above settings allow for one photo of 6.74 MC to be uploaded?? Is it a problem with the server? It seems to work fine with smaller photo filesizes.</p>
<p>I am hosted with Dreamhost.</p>
<p>See attached screenshots.</p>
<p>I would appreciate input and suggestions. My client has been trying to upload photos with no success and is not happy.</p>
<p>Thanks</p>
<p>Kevin</p>]]></description>
          <pubDate>Mon, 02 Jun 2014 17:30:04 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2234088#post2234088</guid>
        </item>
              </channel>
    </rss>
  