You need to be logged in to post in the forum - Log In
An active JCE Pro Subscription is required to post in the forum - Buy a Subscription
Support is currently Offline
Official support hours:
Monday To Friday
From 09:00 To 17:00 Europe/London (BST)
From 09:00 To 17:00 Europe/London (BST)
Please post your question in the Forum and we will get back to you as soon as we can.
Hello, I have a server at 1 & 1, 6 GB Ram (3 GB Consumed), 50GB Webspace (8 GB Consumed).
I can choose between PHP versions 5.6, 7.0, 7.1 and 7.2.
Joomla 3.8.12 and JCE Pro 2.6.32 are intsalliert
If I upload an image with ~ 250 KB and want to insert a watermark, I can not upload images, it works without watermarks.
Is this on the server (gd-lib/image magick), or on the JCE Pro 2.6.32?
I can choose between PHP versions 5.6, 7.0, 7.1 and 7.2.
Joomla 3.8.12 and JCE Pro 2.6.32 are intsalliert
If I upload an image with ~ 250 KB and want to insert a watermark, I can not upload images, it works without watermarks.
Is this on the server (gd-lib/image magick), or on the JCE Pro 2.6.32?
If you are getting the "Insufficient memory available to process this image" error message then your server is using GD2 for image processing, not PHP IMagick
Please speak to your host about enabling PHP IMagick.
When using PHP GD2, a check of the available PHP memory at the time of processing is done to determine whether there is sufficient memory available to perform the action. The amount of memory required is estimated based on the width x height of the image, not the file size. If insufficient memory is available, the error is generated and the action cancelled to prevent a PHP fatal error on the server.
This can be prevented by increasing the amount of memory available to PHP - usually 64MB+ is recommended - or by enabling PHP IMagick.
Please speak to your host about enabling PHP IMagick.
If I upload an image with ~ 250 KB and want to insert a watermark, I can not upload images, it works without watermarks.
When using PHP GD2, a check of the available PHP memory at the time of processing is done to determine whether there is sufficient memory available to perform the action. The amount of memory required is estimated based on the width x height of the image, not the file size. If insufficient memory is available, the error is generated and the action cancelled to prevent a PHP fatal error on the server.
This can be prevented by increasing the amount of memory available to PHP - usually 64MB+ is recommended - or by enabling PHP IMagick.
Just because you're not paranoid doesn't mean everybody isn't out to get you.
more than a month ago
·
#103451
Hey, Ryan! How are ya?
So, I have GD2 installed but still getting this error when cropping in Image Manager Extended. Will adjust memory_limit and let you know.
Please advise.
So, I have GD2 installed but still getting this error when cropping in Image Manager Extended. Will adjust memory_limit and let you know.
Please advise.
The are only 3 solutions to this issue:
1. Increase the php memory limit to a large amount, I would advise 128Mb or more.
2. Pre-process the image before uplpading so it is smaller (not really a constructive option I know)
3. Get you host to enable PHP IMagick. This is the best solution overall.
1. Increase the php memory limit to a large amount, I would advise 128Mb or more.
2. Pre-process the image before uplpading so it is smaller (not really a constructive option I know)
3. Get you host to enable PHP IMagick. This is the best solution overall.
Just because you're not paranoid doesn't mean everybody isn't out to get you.
- Page :
- 1
There are no replies made for this post yet.
Be one of the first to reply to this post!
Be one of the first to reply to this post!