Posts by Stoobers


    After removing ImageMagick from PHP.INI, I've now got PDF's uploading. However, this now means that no images get a thumbnail (which kinda says GD isn't being used to thumbnail images as per Drew's explanation a while back). I guess my customer will have to live with that.

    I'd say this means that my instance of MAMP Pro was at fault here, possibly not compatible with Windows 2019 (which I'll take up with MAMP) but for anyone else getting this issue in the future here's some tips...

    In MAMP Pro, under Languages > PHP unticking Imagck/ImageMagick does not disable Imagemagick (which is what you'd expect it to do!!). To disable it you should go to the File menu (in MAMP Pro UI) > Edit Template > PHP > and select the version of PHP you're running. In the editor find "magick" and you'll find the line "MAMP_Imagick_MAMPextension=php_imagick.dll". Change this to be commented out by using a semi-colon to ";MAMP_Imagick_MAMPextension=php_imagick.dll" (without the quotes). Save the file, close the editor and restart the Apache service. This will disable it properly.

    You can confirm this is no longer loaded by checking Perch extended diagnostics for "ImageMagick: No".

    The next issue though is why are image thumbnails not being created if GD is loaded and should be working?

    I am fairly sure that I successfully added PDF assets for which Perch did not generate thumbnails.

    Does the issue happen when you upload any PDF? Or are you only testing with the same PDF?

    And where does this happen? In a content region?

    Thanks for your reply.

    Apparently (according to Drew in an old post) turning off ImageMagick should turn off PDF thumbnail generation, however turning it off in MAMP Pro seems to make no difference for me. I'm only suspecting this is the issue as it's been mentioned in the forums before and I appear to have the very similar symptoms in that when I upload the PDF it saves it in the designated folder but Perch logs me out so looks to be a hard error crashing Apache or something.

    I've tried numerous PDF's, all are not large (under 1mb in size) and from various sources. All have the same outcome.

    This is happening when logged in to Perch, Assets, Add New Asset (in to any buckets I have configured).

    I feel I need to find a way to confirm ImageMagick is actually working in my installation. I can retrieve the version number (in my first post) but I'm not sure how I can test it. As far as I know uploading an image file doesn't use ImageMagick as Drew had previously mentioned images only use GD for resizing etc, PDF's use ImageMagick as GD can't handle PDF's.

    Any further thoughts or ways to test ImageMagick would be gratefully received.


    Hi all,

    Hopefully the hive mind can help me here.

    I'm currently moving a Perch site from one server (Windows 2012 running MAMP) to another (Windows 2019 running MAMP Pro). So far, I've got everything working as it should, with the exception of uploading PDF files via the Assets screen.

    I've tested the upload using TXT, PNG, JPG etc, all work fine, however PDF files get uploaded in to the specified folder fine, but the user then gets logged out of the Perch interface. and no entry in to the database takes place. This seems to point to that the thumbnail for the PDF cannot be generated and causes a pretty hard PHP error. However, I'm seeing nothing in the PHP or Apache error logs.

    I've been digging around old forum posts, and read that this may be an indication that ImageMagick is not installed on the webserver. When I test for the ImageMagick version using...

    $imagick_version_string = $imagick_version['versionString'];

    I get this:

    ImageMagick 6.8.9-1 Q16 x86 2014-05-08

    In the extended diagnostics in Perch, I can see ImageMagick is loaded:

    Extensions: Core, bcmath, calendar, com_dotnet, ctype, date, filter, hash, iconv, json, SPL, odbc, pcre, Reflection, session, sockets, standard, mysqlnd, tokenizer, zip, zlib, libxml, dom, PDO, bz2, SimpleXML, soap, xml, xmlreader, xmlwriter, apache2handler, openssl, curl, fileinfo, gd, intl, mbstring, memcache, mysqli, Phar, pdo_mysql, pdo_sqlite, sqlite3, xsl, exif, imagick

    GD: Yes

    ImageMagick: Yes

    I'm stumped as to how to move forward with resolving this, can anyone help with any suggestions on how to resolve or any PHP to test ImageMagick or any of its dependants are actually working properly?

    Thanks in advance,


    Hi all, hoping I can get a little help here with investigating what the issue may be (or even better, a fix!)

    I've copied my site to a new server ready for a migration, and while I'm at it decided to update Perch and it's addons and I've run in to a little issue with the Blog addon updating. I've downloaded the latest Perch (3.1.7), perchforms (1.12), perchmembers (1.6.4) and perchblog (5.6.1) and copied the files to the addons folder replacing any files that needed replacing.

    On logging in to /perch/ I was greeted with the usual site update page, which appeared to run through without any issues and confirmed that under /perch/core/settings/diagnostics/ my site is showing as:

    • PHP 7.4.1 is up to date
    • MySQL 5.7.24 is up to date

    • Image processing available

    Under /perch/core/settings/diagnostics/add-ons/ I have the following:

    • Blog 5.6.1 is up to date
    • Forms 1.12 is up to date

    • Members 1.6.4 is up to date

    • Backup 1.2 is up to date

    When I view the blog posts from the actual site, everything looks to be in order and normal. However, when I go to Blog from inside Perch (/perch/addons/apps/perch_blog/) I am shown the following:

    Software Update

    Updating posts 0 to 9 of 55.

    The URL for this is /perch/addons/apps/perch_blog/update/?force=update&page=2

    The issue is that this page reloads every 10 seconds or so, and doesn't appear to get any further forward. In an attempt to fault find, I tried the URL /perch/addons/apps/perch_blog/update/ and this refreshed a number of times, counting up through posts 10 to 19, 20 to 29, etc, up to 55. I was then given a "continue" button which suggests the update finished. On pressing this it went back to updating 0 of 9 and continues to refresh the page and does not move forward.

    It appears that the updating of the posts is failing between post 0 and 9 (which would be /perch/addons/apps/perch_blog/update/?force=update&page=1) , as when it moved to posts 10 to 19 the URL was showing page=2. However, I'm not able to confirm that is the cause. I've examined the data in the posts and everything appears to look correct. I've checked on the live site, and the Blog section (/perch/addons/apps/perch_blog/) loads fine.

    I've gone as far as removing all but one of the entries in blog_posts table to see if it's being caused by a weird post entry, however this then simply jumps to the end of the update process, shows the continue button, and when clicked, goes through the update again (instantly as there's only one post) and displays the continue button again. I'm semi-confident that would mean the post data isn't the issue here.

    Would anyone be able to suggest anything to help with finding what the issue is? The apache log files don't seem to give much in the way of any clues.

    Many thanks in advance of any pointers :)