o2xav

The error came from this module : https://www.ads-software.com/plugins/imagemagick-engine/

AH01071: Got error 'PHP message: PHP Fatal error: Uncaught ImagickException: cache resources exhausted `

Thanks for your help, and sorry for wasting your time.

I’ll take a look, also, when I list ACF fields in the relevanssi dashboard, I can see some old fields that have been deleted in the past in the list, i’ll try to look at that too

Oh yes, sorry : 500

This is what I get :

I started the process of disabling from index all fields referencing images and files, but it did not help.

If I disable custom fields indexing it works to 100% without issue.

Thanks for your fast reponse and great support.

Indeed I have some flex fields referencing some custom taxonomies, how would I exclude them from the indexing process? Do I have to chose “some” and list all fields in the dedicated field except this specific one?

Nevermind I found out directly in the ACF field settings.

I Searched all my fields and excluded all fields making a reference to other posts or taxonomy from the index, but the indexing process still halts at 70%. Do I still have to disable indexing of image and galery fields? Is there some kind of debug log I can activate for the indexing process?

• This reply was modified 1 year, 3 months ago by o2xav.
• This reply was modified 1 year, 3 months ago by o2xav.

I’d gladly help, but what is the question?
If it is “Does ImageMagick Engine work without ImageMagick?” the answer is obviously no.
The author cannot embed ImageMagick in the plugin package, it has to be supported by your hosting plan.

Oui en effet ?a fonctionne à présent, j’avais testé cette solution mais j’avais oublié de vider le cache,
Merci!

• This reply was modified 3 years, 6 months ago by o2xav.

Hi, thank you for your answer, but i do not have the “generate missing webp” in settings page, i’m using the latest version of the plugin

That’s awesome, please keep us informed !

Regards,

Thanks, it’s what i figured, will try that later,
Many thanks again !

@vipa please could you explain in what way you changed this policy file?

Well in fact i disabled gutenberg, and i am using the classic editor.
Still, since the 5.0 update, disable autop does not work anymore.

Yes, i can confirm it has nothing to do with DG, it has to do with WP 5.0+, and the arrival of gutenberg.

Before 5.0 you could disable autop, now you can’t.

And i was hoping to find a module that disables gutenberg, and removes these pesky p tags, or make “disable autop” work as it did before gutenberg.

For now, i did not find a premade solution, i’ll try to look into it myself next week, if i find something, i’ll share with you, maybe you can make it an option.

Hello Rermis, did you find a solution to this inability to disable autop?
Those unwanted P tags are really causing some editing problems here.

You know what, it was unfair for me to put three stars, because it’s not the plugin’s fault, i just did not think it through, did not want to hurt anyone.

But you can try on your side, even with gutenberg disabled (with the help of your plugin or another):
-create a post,
-insert an image on the first line,
-create a new paragraph underneath
-publish
Now check the page’s source, the image is surrounded in P tags. Whether you have wpautop disabled or not. Same for double line breaks. And this happened when WP5.0 came out.

One of the reasons i’m starting to consider moving to ClassicPress

• This reply was modified 5 years, 10 months ago by o2xav.