Hello,

Now, I don't know if these things are possible... However

Could the make/upload listing (under notifications) only be cleared when another MultiMaker operation is started ?

As it would enable reopening to view it more than once.

Also, could the MultiMaker window be made to 'stay on top'... ?

Many Thanks, Peter

Thank You,

I never realised I could use the notifications button multiple times. Am sorry about that.

I ask about being always on top, as it is a struggle to get both windows back together again, MultiMaker on top.

I my case, I am not sure how others use it, but I would just close MultiMaker when I am finished then restart it again when I need it. Its not something I would need to leave open.

For me, if it could be always on top, that would be far simpler and much appreciated.

Regards Peter

Am not sure what you mean by 'ready'... ?

In my case, once I am happy that an album can be uploaded, and that its not a brand new album........ Thats it really.

I think, if an album is about to be uploaded, then its up to the person uploading it to ensure everything is ready and that the upload will be successful, MultiMaker is just a great tool for uploading a lot of albums, any issues found are displayed in the red bar. Where upon, in my case, I sort them out.

I apologise if I have misunderstood.

The notifications listing shows that all went/uploaded ok. just click on the megaphone after the event.

The glorious red bar will appear during upload if the album needs to be manually uploaded for the very first time.

Other than that, its Go for Launch!

Regards Peter

Edited by: PeterGibb on 7 Sep 2022, 12:31

André, it's these kinds of snide, nasty remarks that got you suspended before. Shall we do that again?

Well if I click on notification after the batch is finished, I see only green entries, so it looks OK.

However it is not OK, if I open the console window I see this:

Making "Portfolio_LG" (Changes)
Non existing themeimage: https://andrewolff.jalbum.net/SamplePortfolio_LG/ThemeImage.png
Non existing themeimage: https://andrewolff.jalbum.net/SamplePortfolio_LG/People/ThemeImage.png
Non existing themeimage: https://andrewolff.jalbum.net/SamplePortfolio_LG/Objects/ThemeImage.png
Non existing themeimage: https://andrewolff.jalbum.net/SamplePortfolio_LG/Travel/ThemeImage.png
Non existing themeimage: https://andrewolff.jalbum.net/SamplePortfolio_LG/Nature/ThemeImage.png
"Portfolio_LG" made in 2,493s
Using cached scriptEnvironment

This should also be indicated in a final pop-up message.
Now you don't see it at all if you do not open the console window and investigateall output lines!

Edit:

I don't understand the error message given above and I don't see it if a make the album by hand, so this is apparently a Multi maker problem: I do not use a ThemeImage.png image, only folderimage.jpg images.

Edited by: AndreWolff on 7 Sep 2022, 14:08

André, what skin are you using when you see these error prints to the system console?

You said above ‘I do not use a ThemeImage.png image, only folderimage.jpg images.’ Your sample lightGallery project has skin settings indicating ThemeImage.png could be invoked:
skin.imgTheme=ThemeImage.png
skin.imgThemeMaxWidth=728
skin.imgThemeWidthNr=98
skin.imgThemeWidthUnit=%
So, is it possible it is a skin coding issue. Obviously only you can investigate further.

It is not a skin coding issue, a predefine theme image was damaged.

But the source is not important, there was an error which should be reported in a final pop-up message!