Hendrik57

I’ve nothing changed, but the update is now working. So it must have been a serverside issue in the process.

Only a site that has PHP 8.3 does not update. On the same server.

• This reply was modified 2 months ago by Hendrik57.

I found it out myself.
One can generate webp and avif outside WordPress manualy. That works.
But to have the WordPress plugin do that while (re)generarting the lib-heif-dev labirary has to be compiled with Imagick and after that the PHP versions to.

So the actions on Debian server with DirectAdmin PROI should be:
With PUTTY on admin level:

sudo apt install libheif-dev libde265-dev libaom-dev libavif-dev

Then go to the browser window of DirectAdmin to the option: Compilation scripts.

There you add in the script for Imagick this line:

imagemagick_build_options=”–with-jpeg –with-png –with-tiff –with-webp –with-avif”

Then you add to the scripts of the relevant PHP versions:

–with-avif

And then you start rebuilding with the Build options of DA, first Imagick and after completion the PHP editions you want to have AVIF support.

After that it works.

The — shown before ‘with’ should be – space –

• This reply was modified 2 months, 3 weeks ago by Hendrik57.
• This reply was modified 2 months, 3 weeks ago by Hendrik57.
• This reply was modified 2 months, 3 weeks ago by Hendrik57.

Webp files are also served as expected by WordPress (inspector, network shows that).

But avif is not shown although WPO supports that and those files exist. They can be manualy created on the linux termial, but are also created when uploading a file. Just serving them and regenerating and displaying those avif files fail.

So regenerating with webp enabled generates files. After that enabling avif instead just creates zero byte files and leaves the webp version.

The WordPress debog.log does not show any errors in the log.

• This reply was modified 2 months, 3 weeks ago by Hendrik57.

I did just what you suggested, and looked through FTPs to all files. There it says 0-bytes after regenerating the thumbnails. It did with other regeratings thumnaails the same. The other formats are generated. I will look what happens if i set .webp as output. But it looks as if the regenerate routines only generate the .jpg and .png files in various formats. When uploading a new file, .avif or .webp are correct.
I will also try the ‘replace image’ function in Media Library Files Pro.

OK. We disable the default Media button since we have installed Media Library PRO. Users should not use the default then.

Your Button seems to be added to that now ‘hidden’ Media button. Please do not add your button to others.

I see it is fixed now.

We use ‘Better Plugin Compatibility Control‘ from Oliver Schl?be

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

Alle websites (about 9) that use ACYmailing work now.

• This reply was modified 1 year, 4 months ago by Hendrik57.

That is no email address. And nothing seems to point to that on this site. We do not publish licences and email for that.
Our licence end with: ……..56767490a85973f5833b48c3
and it is for carien

• This reply was modified 1 year, 7 months ago by Hendrik57.

Stupid perhaps, but what email address should I use?

Latest: 7.0.3. with WP 6.2, php8.1.
The .zip: 10,6 MB (11.134.834 bytes)
I will send an email later this evening.

Re?nstall does not work since these folder/files are missing in the .zip also.
There is a variable $skin that is not found in $options. So the resulting path goes to …/.css without a filename. That was my first finding (line 18).

Looking at the code I found out this:
This folder with files in libs does not exist: ‘/libs/flexslider/flexslider.css’
It is used for maxgalleria-image-carousel .

OK. Normal reaction and correct.
But if they delete my reaction on their forum without reasons, that is not OK.
And this was not a typical user problem. It concerned the fact that their plugin was corrupt because of missing files and a variable that could not be loaded from the options. Therefore the plugin did not work at all as one should expect.

To us it seems that pointing to code errors is not what they want in the forum.
We have disabled all MaxGalleria and MaxButtons for now for all client sites.

And YES, we pay ! So no free user. The fact that this is indeed not shown at the site is your problem. We have a licence to use Media Library PRO and that includes the use of MaxGalleria and MaxButtons as your site says. And yes, the use and activation of Max Galleria PRO is not counted on your site. But this has nothing to do with the problems we encounter.

• This reply was modified 1 year, 7 months ago by Hendrik57.

Ok. But should do this manualy on all sites we manage, or wil this fix be done with a regular update?

Wow. Got a gateway timeout with his reply ….

Ok. But should do this manualy on all sites we manage, or wil this fix be done with a regular update?