Custom Query (49 matches)
Results (7 - 9 of 49)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #37 | fixed | Allow login using email address instead of username | borja | borja |
| Description |
or maybe allow both? |
|||
| #61 | fixed | Better templates for "verify your account" emails | borja | borja |
| Description |
Follow up of #29 (signup users). Now that we have the "sign up and verify your account" feature (changeset:76ebb1b/OpenWorkouts-current, changeset:b5d87e0/OpenWorkouts-current) we send an email with the verification link as soon as the user signs up. Right now that email is text/plain email, that can be improved:
|
|||
| #77 | fixed | Bulk workouts upload | borja | borja |
| Description |
So, we already have some code to add workouts in batch mode from a local directory on the filesystem (browser:OpenWorkouts-current/ow/load_workouts.py), but that works only if the workout files (gpx, fit) are located in the filesystem of the computer where openworkouts is running on. In the case of running it in a separate server, users don't have an easy way to upload those workouts. The idea would be to allow users to upload a compressed file containing all the workout files, like a zip, tgz, 7z, etc. Then, openworkouts should uncompress that file into a temporary destination, and run our load_workouts code from there (in a separate, background, process of course). One obvious problem of that is that those compressed files could be quite big, which usually don't work well with traditional http file uploads. One solution for that would be to use something like this js library: |
|||
