mbsharp

As you say, this is a great plugin.
As an entrant can make a partial entry and then top it up later, it would hardly be possible (except by extra-sensory perception) to know whether your entrant has made a partial entry and intends to return later, or your entrant has failed your requirements.
Nor is there any connection between the individual entries to know whether someone has submitted over a quota. They could easily alter their name by one character to defeat such a check.
In the end, the plugin does a great generic job but nobody could build in all the possible local uses to which it can be put. You have to enforce your local rules afterwards. It wouldn’t take more than a couple of disqualifications to get your message over.

As Josie says, if you can code like this, then go the lower risk route of writing in Excel VBA and do your post-processing locally.
One issue I have is that the various clubs use different competitions software, so could there be post-processing with a variable definition of the required output. There are only so many fields which you could want in a file name – Sequence, Title, Photographer, Entrant (may not be the Photographer), Class/Section/Category, Organiser. And, there are only so many ways of separating those fields using keywords or characters. The Entrant may include characters in a Title which are invalid in filenames eg, !, so clean up is required. DiCentra normally requires each Entrant to be submitted in a different folder, which would involve file copying as well as renaming. All in all enough to keep a coder happy and productive.

Could it be that the user didn’t use the submit button correctly?

You can implement the review page where a user can see the current state of all images uploaded to all forms.

Fair point, but compare with the message when the form is closed which does refer to a form.
Either way, no user can actually do anything.

If the webform was closed, then the user should not even have seen the form, let alone be able to upload. But, you point out the glitch that a user could be entering data exactly at the closing time.
The suggestion to close the form later than you advertise, and perhaps at an unreasonable hour of perhaps 5am might be a workaround.

Uploaded files tend to get some renaming anyway to manage blanks and possible duplicates.
To answer your question specifically, files do not get renamed based on a category selected. The category is a field which you can include as a column in your download spreadsheet and work from there.

Are you sure that is correct.
The browser shows text on hover from the content of the Alt field. In Gallery Management, the Alt field is set in the upper text field next to the thumbnail. By default this is usually filed by the filename, but you can easily clear it. If the Alt field is empty, then there should be no text on hover.

Hi,
Well, we now have this check in the latest update thanks to Josie.
The check is on the EXIF data. The EXIF field for colour space only has two defined values – sRGB and Undefined.
Undefined in EXIF may be divisible into eg, No profile, AdobeRGB, ProPhotoRGB or some other bespoke profile, but that requires looking outside EXIF at other segments in the JPEG file.

Long ago, when digital image projection started seriously, it was stated by most events that sRGB is required. Time has moved on. Most competition software can now handle colour management either in advance (eg, DiCentra) or on the fly during projection.
sRGB is effectively no longer mandatory, although most events still say they require it. For the events I run, I typically get 5% errors (non-sRGB), but I have had some clubs in an interclub event with up to 80% errors. I track the stats because I am interested, but the practical effects on projection are nil.

One of the great joys of a plugin like this is that the entrant doesn’t have to use any particular filename for each image.
Josie has explained why any blanks in the offered filename have to be filled, and underscore is typically used.
The format of filename you want looks like that for DiCentra. That’s fine, but somebody else will use different software and want a different filename structure. I use ImageCompPro and want TITLE by Photographer (including the blanks which we already know are not allowed). So the inevitable conclusion is that you let the entrants use any filename; you harvest the image files with whatever filenames they happen to have; and you design and implement your own process to rename all those files to the format required by your competition software.
The available competition software products variously use fields for Sequence, Title, Entrant, Photographer, Class. Whatever you need to make the filename format you require has to be implied or has to be collected at upload time alongside the image file You design your layout and webform accordingly.

You’re right that getting the colour space ‘reliably’ is a problem. There are at least three places in a jpg file where colour space information can be stored either as a tag value or as parameter sets or as a profile. It is not possible to assume that all these places agree.
Then there is the issue of image files without any colour space where sRGB may be assumed but the exact behaviour can differ.
In terms of managing an event entry, it is probably simpler to get the images regardless and have a checking method outside EntryWizard. Personally I open the downloaded images folder in Adobe Bridge, with appropriate metadata display options.

I have come here and found this thread because I have noticed the same effect. If I can be clear on the terminology.
When an image file is uploaded and there are spaces in the filename, then it is true and has always been true that the filename has to be modified on storage in the gallery by filling the space characters with non-space and that uses a hyphen (minus).
I believe that was not the issue raised, and that NextGen has misunderstood the issue. What has started happening now is that the ‘Alt’ field is taking the value of the STORED filename (with hyphens) when previously it took the value of the UPLOADING filename (with spaces). In either case, this is/was the default behaviour if there is no content in the relevant IPTC field.
The Alt field is what the viewer sees on hovering over the thumbnail. I agree with the original correspondent that this change to include hyphens is not desirable, and it would be nice to revert.

Assigning a specific class to the EWZ dialog boxes (version 1.3.10) has stopped any other plugin from getting a look in to overlay its own css. Looks good, so many thanks.

I use an EWZ upload file size maximum of 2MB for UXGA. Experimentally, files from multiple photographers for SXGA+ projection average about 750KB and those for UXGA average about 1MB. There are situations where image files can be much larger, but it is not desirable for an event organiser to allow enormous files into the system. The Photographic Alliance of Great Britain has published guidance on managing image file sizes, which you can see on their website.

I have managed to make a workaround for this problem. The narrow message is caused by the text taking on the left position of the ‘X’ button. In my case this comes from css within the Squelch Tabs and Accordions plugin.
My workaround is to force the ‘X’ button downwards into the text area, which then forces the text to start a new line on the left. I added this css to the area provided by my theme (Nirvana).
.ui-dialog-titlebar-close {position:static !important; float:right !important; margin -30px !important; }
This will affect all JQuery dialog boxes.

Incidentally, this fixes the EntryWizard U011 error message where ideally the ‘X’ button should never be used. It would really be better if the close button was hidden for this message, and the JQuery support documentation gives a way of doing this using a special class which could be added to the dialog <div>.