I just noticed that the guests are now shown on the public website. The former version had an option to handle this.

As the guests being shown on the pulic registration list is almost never desirable, I propose to either bring back the old option to manage this or to not display guest by default.

implement a basic mailer to send emails to competitors (confirmation when competitor state changes from new to confirmed). in the old software, you can save a mail template for things like that on the competition.

I suggest we also use https://github.com/Shopify/liquid for the templating here instead of those ugly text-replace hacks I did in the old app...

looks like this in the old app:

the old app shows a financial overview to tell organizers how much they will make from the entrance fees. also allows them to compare pricing models.

looks like this:

So a todo item here would be to implement something similar. needs to take into account:

• Day#entrance_fee_guests
• Day#entrance_fee_competitors
• Competitor#guest_on?(day) vs. Competitor#competing_on?(day)
• Competitor#free_entrance?

The old code also had an option to set the competition to use "alternative pricing model" where you would define a price for the whole competition rather than for each day individually. The statistics (the $2 column) then shows which pricing model would lead to how much money.

I think we should restructure this a little bit and add another pricing model.

I would like to compare the following three and have an option in the settings to select which one you want:

• each day has it's own price
• you pay a fixed price for the whole competition, regardless of which days you register for
• you pay a fixed price for the whole competition, but only if you sign up for all days (to encourage people to come on all days)

for each of those 3, we should always be able to differentiate between competitor price and guest price.

might be useful to have two of those tables, one for "confirmed" competitors and one for "new" competitors maybe? not sure if that makes sense

destroying an item from a table (competitor, theme file, user, competition, ...) should not reload the whole page but destroy the item via ajax and remove the table row from the dom

After having learned that old users need to remain for different purposes, I'd like to have the users grouped in "allowed to login: yes" and "allowed to login: no", with the former users being listed first of course.

This way, it is way easier to manage the truely active users and not having them mixed up with the majority of users that only need to remain for other purposes.

Old software has this feature to compare past results of registered competitors:

@timhabermaas, how hard is this to do with your API?

Started GET "/assets/codemirror/modes/htmlmixed.js?body=1" for 127.0.0.1 at 2014-10-03 00:41:10 +0200


Started GET "/assets/codemirror/modes/xml.js?body=1" for 127.0.0.1 at 2014-10-03 00:41:10 +0200


Started GET "/assets/codemirror/modes/javascript.js?body=1" for 127.0.0.1 at 2014-10-03 00:41:10 +0200


Started GET "/assets/codemirror/modes/css.js?body=1" for 127.0.0.1 at 2014-10-03 00:41:10 +0200

I don't care...

My first approach (#121) to fix #119 didn't work. See discussion in patbenatar/jquery-nested_attributes#11. Reverted in 60be0c4.

Need something better (maybe fetching the data from the server instead of just cloning the previous row).

• the checkboxes for both languages German and English should better be selected by default (also, they are unselected once a submit was not successful)
• the entrance fee text boxes are required to be filled when creating a competition. However, the person creating a competition usually is not aware of those. I suggest a default value of 0 to fix this.
• when a new competition day is added, the default date shows January 1st 2010. If not too much work, the subsequent days of the previously set day would be a way better default.

The old software had this feature where we showed the number of competitions for a competitor if it was a special number (like multiples of 10). See here.

Not sure how best to do this now that the WCA db is an external service and not sure if the API even supports that yet. Ideally, we would do some kind of batch request and not do one request for each competitor.

@timhabermaas, thoughts?

Feature so that admins can "import" a theme from another competition and "apply" it to theirs.

I added the bundler-audit gem which can generate a report of the gems in your Gemfile that have known security vulnerabilities. We should have those reports either as part of test runs or in a cronjob with email notifications or something like that.

Something like that might already exist as a free service?

When clicking various "delete" buttons, we show a popup that asks "Are you sure?". Some models (competition for example) have several dependent_destroy associations. Would be nice if counts for those would be shown in the popup, e.g. "Are you sure you want to delete this competition? This will also delete 17 competitors, 3 theme files, 2 email templates, ...".

the old software has an action to display printable schedules, centred in a very basic layout. we need to have the same for the new app.

maybe for this case it is better to be directed back to "Competition" -> "Settings"

The settings page only supports entering entrance fees for individual days and then calculates the price for multiple days by adding the values.
The payment system I'm using costs 7.50 euros for either single day but 10 euros for both days instead of 2*7.50 = 15. I'd like to have an option to enter such an alternative price model (which existed in the old admin panel, afaik?) so that the dashboard financial calculations are correct.

Save leads to some 404 and Cancel registers the competitor.

There are some blank events in the competitor registration form

The old software had this feature for nametags. Would be fancy to have the same here (nametags already exist, just not the WCA stats in the bottom line).

Again the question: Should we do this once and then cache it or do it in a batch every time the nametags page is rendered?

@timhabermaas

And so, currently new competitions cannot be created. :/

We probably want to a) notify someone about it and b) fail gracefully.

Something like https://github.com/jnicklas/capybara or similar for everything that depends on JavaScript.

Things like

• WCA ID autocomplete
• jQuery nested attributes
• Load email templates
• Admin menu navigation
• Tooltips (?)
• ...

old software shows this on the admin competitors index:

and this on the dashboard:

Registering a competitor from the user interface for GO15 I get this error:
"Event registration event is not for registration".
I only get this with some combinations of events and couldn't reproduce when. Registering as guest works.

should be able to pull a couple of things from the WCA db, based on a competitors WCA id.

• first name, last name, gender, country (to autocomplete registration form)
• best single and best average time for a given category (for comparison sheets)
• number of competitions attended (for nametags)
• position in wca ranking (global/national, single/average, ...)
• ...

ActiveRecord::RecordInvalid: Validation failed: Entrance fee guests must be greater than 0

So, there's no way to host a competition with no entrance fee? Or do I miss some free flag somewhere?

It would be very helpful to have those as well under "Email addresses".

There are few issues with full_name = first_name + last_name:

• For Hungarians it's full_name = last_name + first_name
• Some people don't have last names
• Some people don't have first names
• ...

See also: http://www.w3.org/International/questions/qa-personal-names#singlefield

What do we need the separation between first and last name for?

A user should only be allowed to change their password or email address if they confirm knowledge of the current password (unless admin).

Something for exception notification

One common problem in the old website was that people would often misspell their own email addresses which then would have to be manually corrected (if even noticed at all).

Would be nice to match a new competitor registration to existing registrations with the same name or same WCA ID and suggest a correction if the email address of the new registration is different than an email address of an old registration.

Also suggest fixes for common typos (such as .co instead of .com).

The nametags are obviously larger than before.
For the nametags we usually use they should be about 8,9 x 5,3 cm

There are a bunch of (auto generated) files with no content:

• Helpers
• CSS files
• CoffeeScript files

for admins (who can see all competitions), the top right corner competitions drop-down in the admin can get pretty big and hard to navigate. would be nice to implement a fuzzy search, something like http://experiments.muditameta.com/fuzzyDropdown/

With our frequently used pre-payment system this has to be selected for almost all competitors, currently by editing the person, scrolling, checking the right check box and saving, which is quite annoying.

There should be a "reset password" link on the login page that sets a reset token on the User model and sends an email to the user's email address with a URL that has the token in it. Using that URL, the user should be able to set a new password. (reset tokens should be hashed as well)

Should have a README with some basic instructions on how to get this app running locally and remotely, how to contribute, etc.

This is actually more an issue than a feature:

• it is misleading if competitions have combined fees for multiple days, like 10€ for one day, 15 € for two days, which is quite common
• for German Open 2015, I had entered 4,55 € as this is what I receive after Paypal removes its fees. I didn't know that this was automatically displayed somewhere and was told by someone who noticed it today.
• also, after now entering "5", the page shows "5.0 €"

I think I would prefer to simple remove this from the registration page.

Want a feature so that admins are able to "import" an event schedule of a day of another competition and "apply" it to their competition.

http://brakemanscanner.org/

Having something similar to http://cube.hackvalue.de/muc14/s/de/stats would be nice

Use something like https://github.com/holli/auto_strip_attributes to auto strip/squeeze whitespace in string fields

Trying to access the website on Android 5.1, Firefox Mobile 37.0.1 by simply typing the URL (no typos) results in:
"An error occured during a connection to admin.cubecomp.de. The OCSP server has no status for the certificate. (Error code: sec_error_ocsp_unknown_cert)"

https://github.com/fw42/cubecomp/blob/master/app/services/registration_service.rb#L22

def register_as_guest!(day_or_day_id)
  register_for_day!(day_or_day_id)
  @competitor.event_registrations.on_day(day_id(day_or_day_id)).each(&:destroy!)
end

If this fails while destroying the event registrations there will be a guest which is registered for some events.

That's probably not the only method where things can go wrong.

Admin area should be forced to SSL (and everything else should work with both SSL and non-SSL).

Would be cool to ensure that all HTML and CSS is W3C conform... Maybe automated.

https://github.com/jmuheim/headhunter

https://github.com/alexdunae/w3c_validators

I'd like to be able to edit registration comments as it was possible in the previous version.

The goal is, to remove unnecessary information from the checklist, usually by removing the registration comment and aggregating important information as an admin comment.

http://fusiongrokker.com/post/heavily-customizing-a-bootstrap-typeahead

should do something like this, otherwise it makes a new request on every single character, which is annoying and kinda heavy on the server

@timhabermaas