Thanks for the reply.  It's an older version of the CMSB and does need an upgrade so it would be good to know how to enable more verbose logging for the PHP Mailer version, if that's possible?

We've added some logging for the existing version which writes to a new field that we've created in outgoing_mail and that seems to work but these changes will be lost when we upgrade.

Regards, Paul.

This is working in general but occassionally an email is sent which is then logged within the CMS but not at the third party SMTP host.

Is there any more verbose logging that we can enable for SwiftMailer to work out why some emails are failing?

Thanks, Paul.

I've had a few enquiries about this as it's something that's available with WordPress so it would be great to see it built into CMSB.

I think WordPress plugins can use Authenticator apps but even if it just emailed a code then that would be a good step up in security.

Thanks, Paul.

Adding ?__debug did the trick so thanks for that.  Toggling the switch in the Admin -> General Settings only seemed to add the debug info within the CMS screens, not the front end.  

Regards, Paul.

I can see it on the CMS Admin pages but can't seem to get it working on front end pages, do I need to do anything specific to enable this?  I'm logged in as Admin.

Thanks, Paul.

Paul.

I'm using v3.73.

Is there a way to debug this?

Thanks, Paul.

I'll see if I can get WebP support enabled in ImageMagick but in the meantime have applied your patch and tested successfully.

Thanks for your help.

Paul.

WEBP isn't listed there.  Is it possible to get CMS Builder to use GD instead of ImageMagick?  Or do you think there's another workaround?

Thanks, Paul.

Thanks for your reply.

So the first point returns 'imagecreatefromwebp() is available'

I've created the section with upload field, unchecked all of the options and ensured WebP is turned on and get the same error message as before:

Unable to set image format
in httpdocs/cmsAdmin/lib/image_functions.php on line 401.

Regards, Paul.

I'm also getting this error.  I'm trying to upload a jpg image with the option to 'Automatically convert image uploads to WebP format' selected.

I've checked phpinfo() and get the same as your screenshot, WebP support is enabled.

OS is CentOS 7.9.2009, PHP is v8.0.13.

Regards, Paul.

There's a Google update coming in May which threatens to use next gen images as a ranking factor so we're getting a lot of enquiries about support for it.

Thanks, Paul.

The browser opens a blank window with 'about:blank#blocked' in the URL.

Do you know what could be causing this?

Thanks, Paul.

I've just tried ping localhost and it returns 127.0.0.1 so it's odd but guess it's got something to do with the MySQL setup.

I've commented that line out which is fine for me but if you can think of a fix for the next release then it will avoid me having to remember to apply the patch.

Thanks, Paul.

I've noticed that each time it runs, it's changing the 'localhost' value in settings.dat.php to be '127.0.0.1' (see line 56 of database_functions.php) which breaks the connection on this site.  I'm not sure why 127.0.0.1 isn't working on the server but I've had to comment this line out to prevent it from breaking as soon as I change the setting back.

Is there a reason why it's trying to update 'localhost' to '127.0.0.1'?

Thanks, Paul.

Did the problem occur for you following an upgrade to MariaDB?

Paul.

Did you find a resolution to this as I'm facing the same problem.  It's in trying to add a new field to a section I get the following:

Error:
Notice: There was an error creating the MySQL Column, the error was:

Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs - in editField_functions.php on line 357 by _updateMySQL() in /var/www/vhosts/**********/httpdocs/Admin/lib/common.php on line 278

This is also with MariaDB 10.3 and CMSB 3.53

Thanks, Paul.

Thanks for the reply.  There isn't a specific project at the moment but I have had requests for this functionality in the past so that secure documents can be uploaded and only accessed via PHP and not a direct URL.

If I have a specific need then I'll get in touch to see if you can help but I think this would be a good feature for CMSB in general, maybe to have a 'secure storage' checkbox on upload fields that if selected stores them outside of web root and then uses PHP to retrieve them instead of just giving the user a direct URL to the file.  Uploads without this checked will work in the same way.

Just a thought for now!

Regards, Paul.

Is anything like this on the roadmap?

Paul.

Thanks for the response. 

PHP was upgraded from v5.4, CMSB 3.13 is installed which was installed after the PHP upgrade.

The following errors are listed in the developer console:

There are no recent messages in the CMSB developer log.

Hope this helps!

Thanks, Paul.

I've been through all other posts in the forum relating to this but nothing has worked.

Can anybody shed any light on this?

Thanks, Paul.

You're right, I was using thumbUrlPath to display the image which of course doesn't exist for SVG's.  Changing this to urlPath works.

The image isn't displayed in the CMS admin but that not a major problem.

Regards, Paul.

Is there a workaround for this as we're trying to write a system which allows users to upload replacement icons which lends itself very well to using SVG.

Thanks, Paul.

Is there a way to have it so that it can't be overwritten?

Regards, Paul.

I've seen a section called field add ons which has a before and after and looks like it could do what I need but I've tried entering a value in the before and it doesn't save this in the Permalinks DB.