Closed (fixed)
Project:
ImageMagick
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Jan 2019 at 22:56 UTC
Updated:
5 Oct 2020 at 21:03 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mondrakePatch
Comment #3
mondrakeComment #5
mondrakeAdjustment for fileeye/mimemap 1.0.0-alpha3
Comment #7
mondrakeCommitted to 8.x-3.x. To be ported to 8.x-2.x for deprecation of
ImagemagickMimeTypeMapper.Comment #8
mondrakeNeed to adjust for fileeye/mimemap 1.0.0-beta1
Comment #9
mondrakeComment #11
mondrakeComment #12
mondrakeHere's the backport, now fileeye/mimemap has its first stable release.
Comment #14
mondrakeNo deprecations reported in contrib tests, yet.
Comment #15
mondrakeAdded deprecation triggers.
Comment #17
mondrakeCommitted to 8.x-2.x.
Comment #18
mondrakeComment #19
jonasdk commentedAfter upgrading to 2.4 going to the status page (/admin/reports/status) creates this message:
I have tried the normal remedies like clearing cache and update db.
Comment #20
mondrakeCan you try a
composer showon Drupal root, and see if it showsfileeye/mimemapComment #21
fonant commentedMine, updated using drush, didn't.
The command
composer require fileeye/mimemapsorted the problem for me.Looks like I need to use composer for the imagemagick module...
Comment #22
mondrakeNot a drush user, sorry...
Yes, the composer way to update the module, if already installed, is
composer update drupal/imagemagickor to install anew
composer require drupal/imagemagick:^2.4That will also bring in the required dependencies,
fileeye/mimemapbeing one of them.Comment #23
sachariew commentedHave the same problem as #19. But on shared hosting without drush/composer. Could you advice me which module/library to put where in order for this to work?
Thanks a lot!
Comment #24
mondrakeRe #23
From the project page:
Requirements
Installation
then enable the module as usual. If your build cannot use Composer, an earlier alpha-level release 8.x-1.x-alpha6 is generally working, but no longer supported.
Comment #25
sachariew commentedRight, so Drupal is not usable without composer anymore? Wasn't there a discussion some time ago, that Drupal should not lose all those who use shared hosting? I know that I can keep the module at the previous version, but someday there will be a security vulnerability preventing me from using older versions. And there are other modules, that might implement imagemagick, but not as well supported and maintained. So, I don't want to sound rude and I am grateful for the work being done here. I can't code php myself. It's just that it is a pity, that the move to composer leaves many users and use cases behind. Ok, I should be able to use composer locally, but still. A pity. :-(
Comment #26
jens peter commentedJust ran a standard update and now my site is broke as the ImageMagick now needs Composer for dependencies and was not warned clearly enough on the update page.
I have no clue on what to do now.
Any idea?
I got a very long list of errors, I can only get to a few pages of the administrations menu and almost none of the content pages of the site.
THis is really not a good way to upgrade between minor versions.
Comment #27
ressaYou could create an issue, requesting Ludwig integration (like Address module has) as an alternative to Composer?
Comment #28
sachariew commented@Jens Peter: Just downgrade to previous version. Seems to work without problems on my site...
Comment #29
jens peter commented@Sachariew thank you. I did just that and it solved the issue.
I still think it is wrong to make a standard update with a change this big as I now have a module not updated and cannot be updated because dependencies are not listed - for the lifetime of this site, I am forced to ignore this one module update.
@ressa Good idea, I have not head about the Ludwig module before. I will give it a test.
Interesting to be able to do updates like this - should be developed as standard function in Drupal and not as a module developers need to set each module up for. It should be possible to update every installation without the need for extra modules or developer styled commands - this way push users away from using Drupal more than include more to our world.
Comment #30
jjmackow commentedThanks @fonant #21. I had updated modules through the admin UI, among which was the latest ImageMagic update here, and wound up with the error showing up after attempting to edit content types that relied on Image fields on the site.
I, fortunately, do use composer, and was able to quickly fix my issue with your suggestion of running from the instance's webroot directory,
composer require fileeye/mimemapComment #32
mondrakeComment #33
hongpong commentedLudwig is the way to go here for ducking composer problems including on Pantheon. see #3035270: ImageMagick - Ludwig integration
Comment #34
Eduardo Alvarez commentedJust in case this might be usefull to someone I left here some instructions to have this working without composer.
The idea is to download the PHP library (https://github.com/FileEye/MimeMap) to ./vendor/fileeye/mimemap within the Drupal directory.
And then apply the patch attached to update the autoload.
Comment #35
devad commented@mondrake, please change this issue to "Closed as duplicate" of:
#3035270: ImageMagick - Ludwig integration
So that users can go to the solution-seeking issue.