mbsharp

Likewise, and anyway it is not possible to change the Lightbox choice/setting. Using Fancybox.

I contacted Weaver Xtreme support. They suggested installing the Classic Widget plugin which reverts widget editing from the block editor to the classic editor. This proves to be the complete cure. No PHP errors thrown from the NextGen code now.

As Weaver Xtreme is the only theme I use and have loaded, I cannot deactivate it to test. Al the problem is relatively trivial I will just wait and see if it gets cured sometime.

Thanks for your reply. The issue reported is showing up on three different sites all with the same php and WP versions, and with fully up to date NGGallery. So I would rule out a code file corruption.

It might be related to the theme which is Weaver Xtreme in all three cases.

As it stands, the only operational problem is the creation of lines in the error log and the widgets do not display correctly in the block editor. It has been this way for a very long time ie, years, and across numerous NG versions. I can work around it.

My experience is that there is a hierarchy in the way fields are filled:

Alt is displayed when the user hovers over a thumbnail.
Alt is populated during image upload from the field identified variously as:
ExifTool fieldname: IPTC > ObjectName
IrfanView fieldname: IPTC > Document Title
Photoshop Elements File Info fieldname: IPTC > Status > Title.
If this first choice field is null, the second choice is to populate Alt from the field used for Title (see next). In this case, Alt and Title will acquire the same data. If the second choice is also null, then the final choice is to populate Alt using the file name with any blanks filled with ‘-‘ or ‘_’ (option)

Title is displayed when the user clicks on a thumbnail and the image is displayed in a pop-up.
Title is populated during image upload from the field identified variously as:
ExifTool fieldname: IPTC > Caption-Abstract
IrfanView fieldname: IPTC > Caption (Description)
Photoshop Elements File Info fieldname: IPTC > Content > Description
If this field is null, the default Title is null.

Tags is populated during image upload from the field identified variously as:
ExifTool fieldname: IPTC > Keywords
IrfanView fieldname: IPTC > Keywords
Photoshop Elements File Info fieldname: IPTC > Content > Keywords.
If this field is null, the default Tags is null.

As noted, you can prefill the EXIF fields as you wish eg, using an EXIF editor tool.

It certainly does. The directives you need in php.ini placed in your root folder are (eg to set 64MB):
upload_max_filesize= 64M
post_max_size = 64M

There might have been another reason for my user getting [U012]. We recently had to change hosting provider and package. When uploading 20 images, and with a limit of 2MB per image, the whole set could exceed the default 32MB upload limit which I had forgotten to change to the larger value we used before.

I thought you were running out of space on your server. Wouldn’t mp4 files aggravate that?

Appears to be solved in 3.59

Appears to be solved in 3.59

Well that certainly is a good reason.

I checked all my permissions and they are OK – 755 on all folders. My user with [U012] uploaded a few at a time, and anyway no repetition.

There is the workaround which is to disable the breadcrumbs in gallery settings. That forces the user to either use the main page breadcrumbs list or use backarrow. Backarrow goes back to the album and a second gallery does display from there. However it would be nice if this workaround was only temporarily required.

Likewise. v3.58 still has the same error

I have a user who is getting [U012] messages for some uploads. I don’t know if that may be the same reason. I will have to look at folder permissions when I can get access as we recently had to migrate our site. In your view what should be the folder permission setting.

Correction. widget-id is a constant. The error is in $args[‘widget-id’] ie the array value is undefined or invalid.