windracer wrote:

ran into this error:

Code:

"\u26d4 Invalid image dimensions in DB for ID 68536 (.\/galleries\/events\/sporting-events\/guardians\/IMG_2620.JPG) \u2013 width\/height missing"

Seems like this error was on a few HEIC files that had .JPG extensions. Even though the EXIF/metadata correctly showed the height/width, Piwigo was reporting it as empty. I had to "replace" the photos with actual .JPG versions and that resolved the issue with those.

Hi Windracer,

Thanks so much again for testing and for your feedback!

I just released version 0.3.0 of AlbumPilot, see https://github.com/HendrikSchoettle/Alb … tag/v0.3.0 - which I believe addresses most of the points you raised:

There is now a dropdown-based album selector with live text filtering.

A new "parent element" at the top of the list lets you select all albums at once for recursive processing. This should cover your case where no root album was visible before.

The plugin now supports granular control over thumbnail and video poster generation, including the ability to overwrite existing thumbnails and configure generation intervals, sizes, formats, and more.

See the release notes for detailed information.

I wasn't able to test the "select all albums" feature thoroughly myself, as I currently only have a single album in my test gallery - so I'd really appreciate if you could verify that it now behaves as expected on your end.

Regarding the error messages and processing failures you encountered: I've seen similar behavior myself, especially when testing on large galleries. In my cases, the root cause turned out to be corrupt or partially uploaded media files. The plugin's logic tries to detect this, and I would recommend double-checking those specific files using Piwigo's standard tools (or regenerating them, if possible). If the issue also appears in standard Piwigo operations, it's very likely a media-specific problem. If not, please let me know.

Still, if you continue to see consistent plugin-specific errors, feel free to share logs or reproduce steps, I'll do my best to look into them even though I can't promise fast turnaround times.

@All: Please test this version on different environments and report feedback, bugs, and compatibility notes.

From my side, this version is now feature-complete and feels "final", at least for now (yes, I know, famous last words...). Anyway, it includes all the functionality I originally had in mind.

If I get some positive feedback and a bit more confirmation from others that it's stable across various setups, I'd be happy to promote it to version 1.0.0 and submit it to the official Piwigo plugin directory. Since the plugin touches several central parts of the database architecture, I want to make sure it's been tested by more than just me before publishing it as an official version.

Thanks again for your time and effort. I really hope this plugin makes life easier!

Best,
Hendrik

Hey, thanks again for testing - and sorry I didn't mention the table change more clearly!

In version 0.3.0, the plugin finally uses Piwigo's table prefix properly. That means the settings table is now named something like pwg_album_pilot_settings instead of just album_pilot_settings, so the plugin won't find the old one anymore, which causes that error.

Easiest fix: just delete the old table entirely. It only stores UI settings (like checkbox states and the selected album), nothing critical - so there's really no data loss.

Normally, the plugin will recreate the table automatically on first run. If that doesn't happen, you can rename maintain.class.php.disabled back to maintain.class.php. Make sure the plugin folder is named exactly AlbumPilot (according to your screenshot, you did).

That way, the table will be created cleanly via the install hook when activating the plugin.

One side note: I intentionally made the plugin "folder-name agnostic" so I can rename the folder whenever I update it. That helps avoid issues with old JS or CSS files being cached and causing weird bugs after installing new versions. So if you run into any UI glitches, you can try just renaming the plugin folder to something like AlbumPilot-030 and reloading - that often fixed things in my case. Just note that if the folder is renamed, the install/uninstall logic in maintain.class.php has to be disabled, as you will not be able to activate/deactivate the plugin in that case. I am not sure whether this will change the broken header output you are seeing, but maybe you can give it a try.

Hope that helps! Let me know if anything's still broken.

Best,
Hendrik

Okay, can you send me the code that's visible in the beginning of the web page? If possible, just the entire html content (Ctrl - U in the browser, you may remove any internal text) and maybe any related logfile entries? Thanks! The code usually appears in case of errors thrown prior to the creation of the HTML body. Thanks!

I went back to v0.2.1 and it worked, so seems to be something specific to v0.3.0?

I'm really confused as to what is happening here.

I removed 0.2.1 and deleted the piwigo_ prefixed album_pilot_settings table via phpMyAdmin (I'm no stranger to SQL databases so I'm comfortable with all of that). No other "orphaned" tables.

Downloaded and extracted 0.3.1, but just like with 0.3.0, no matter how I name the plugin folder (AlbumPilot, AlbumPilot_beta, etc.), with maintain.class.php present (so it will create the table), the plugin fails to activate with just "an error occured":



At this point, activating or deactivating the plugin throws the same error. The only way I can "remove" it is to rename the maintain file back to .disabled or physically remove the plugin folder from my server (and then try again). I cannot figure out the proper order of events to get the plugin to install, create the table, and then work. Basically, whenever that maintain file is not "disabled" the plugin will not activate.

Sorry for the trouble, but I'm assuming things like this will need to get worked out before you can put the plugin into the extension library.

Last edited by windracer (2025-06-13 14:34:49)

I deleted the file, but when activating the plug-in, it's not creating the table so I get the wall of PHP code and this error:

Fatal error: Uncaught mysqli_sql_exception: Table 'piwigo-beta.pwg_album_pilot_settings' doesn't exist in /usr/local/piwigo-beta/include/dblayer/functions_mysqli.inc.php:132 Stack trace: #0 /usr/local/piwigo-beta/include/dblayer/functions_mysqli.inc.php(132): mysqli->query() #1 /usr/local/piwigo-beta/plugins/AlbumPilot_beta/admin.php(587): pwg_query() #2 /usr/local/piwigo-beta/admin/plugin.php(53): include_once('...') #3 /usr/local/piwigo-beta/admin.php(406): include('...') #4 {main} thrown in /usr/local/piwigo-beta/include/dblayer/functions_mysqli.inc.php on line 132

Want me to try manually creating the table again?