I was interested how other go projects handle their db stuff and took a look on gitea. They seem to use https://gitea.com/xorm/xorm which abstracts the specific db as well as table generation from structs etc.

I know you dont want to introduce external dependencies but this might lower the db pain, esp when some changes in the table Layouts are still likely.

When creating more than 5 movies (i.e. 6) and voting for each one results in one vote for each movie (even though the user only has 5 votes).
In the account page the available votes are displayed as -1

Pages that will need these:

• User Login
• User Account
• Add Movie

I'm not too concerned about adding CSRF tokens to the admin pages, but they should probably be added there eventually too.

For certain usecases only movies should be able to be added (i.e. Zorchs Movienight).
Still it should be optional to filter to only movies (or only one episode series) and be configurable in the admin panel.
Also a total "ban" of certain "tags" (see https://imgur.com/a/qB6Cuie for reference) should be configurable.
Maybe also make the max amount of episodes configurable.

For the episodes the field "episodes" on the same level as the title should be used.
For the entrytype the field "type" is used (see above link for reference).

This should give an error, not panic the server:

Looks like the regex matches slice isn't checked for non-empty before trying to access it at server.go:363

This was not implemented in #18 and is therefore still todo

Add a search for movies to see if it has already been watched or added.

As mentioned by th3ep1cunkn0wn some users might have issues with not installed fonts

We should add a small banner/button/something else to advertise this repository to an average user.

With that a admin user doesnt have to move to the admin view via the address bar.

This issue is relevant for #11 and the accompanying branch at https://github.com/CptPie/MoviePolls/tree/issue11-movienight-info

This caused the issue described in #27.

We already have all movies saved in the database with the corresponding cycle dates.
It should be feasible to display some sort of history (maybe combined with the search functionality).

Similar to #31, only for movies instead of users.

• Delete a movie
• Edit a movie's details (title, description, links, poster)
• Force-add a movie (eg, a duplicate)

For notifications, password reset etc.

At the moment the current not working links are:

• https://myanimelist.net/anime/468/Innocence
• https://myanimelist.net/anime/2972/Kindan_no_Mokushiroku__Crystal_Triangle

Add the ability to create an account, and login with an OAuth account from another service. Allow linking an additional OAuth account after the first account is created. Focus on:

• Twitch
• Discord
• Patreon

Currently a user is able to add a movie without an cycle being active.
This causes a "0" in the current json database implementation.
This also will also cause issues with other database implementations.

I think i introduced this bug in #10, but it should be fixed.

The count of currently available votes and the list of current movie votes is incorrect as it still counts watched movies.

Add RSS to notify people that a new movie night has started with the link and the pin to get in.

as described in the readme

This feature was planned from the beginning but not implemented yet, let's change that.

A user should be able to choose a picture from the local disk and upload it to the moviepolls server.
The file then should be saved within the posters folder (as done with the api posters).
The file upload dialog is already handled by the browser (its a default html file upload).

Nice to haves:

• Drag and Drop

• Loglevels [DBG] [WARN] [ERR] [CRIT]
• Log to file?

User management in the admin panel needs a lot of work. Namely:

• Deleting a user
• Reset passwords (a better method than just typing in a new one. force change?)
• Banning a user (IP & cookie ban?)
• Renaming a user
• Promote user to Mod or Admin (or generate a url/key pair for a user to use. or both?)
• Probably more stuff I'm forgetting right now.

EDIT:
When deleting a user give the option to delete that user's votes.

Either when adding a movie or/and afterwards.
Size wise 200-250 chars would be enough.
This field would be intended for notes which will be displayed when selecting movies (i.e. "please watch the b/w version").

Requirements:

• Addition of a remarks field in the movie struct
  • Adapt the db connectors
• Addition of a remarks field on "add-movie.html"
  • This field should also be filled when autofill is used (the only field that does not get ignored)
• Render remarks on movie-info.html
• Render remarks on cycle end view for the admin

We have some "small" issues in some places

IMDB links typically have a tracking component tacked on the end of the URL: ?ref_=[...]. These should be removed before saving the link to the database.

When autofilling (both IMDB and MAL) as well as when uploading an image the image is not displayed.
This might have been introduced in fb94861

Limit the length of the various text input fields. Username was already added, but does need to be tweaked to not count zero width spaces (and other weird space characters).

• Movie Title
• Movie Description
• Movie Links

When a user uses the search functionality from #7 and a cycle is currently running, the vote button is rendered for the already watched movie, when voting the server returns code 400.
Error Message in console: Unable to cast vote: Movie has already been watched

Maybe we should give the user a better response than "something went wrong".

In the current state the connector does not support series (since the returned json has a different format).
Do we want to change that?

i.e. https://myanimelist.net/anime/32937/ works but myanimelist.net/anime/32937/ doesnt

I have used all three votes, and when I click "Remove", I get an error saying I have no votes. I clicked on westworld on the main site, and it sent me to https://moviepolls.zorchenhimer.com/vote/67

Make the limit something reasonable (length of 100?).

Don't allow this:

Similar to vote decay, but for movies.

Auto-remove a movie after N cycles if it doesn't have any votes at the next cycle end. The number of cycles should be configurable, and must be a higher value than the vote decay setting.

That does not look nice - more margins on the borders would be nice:

The "Planned End" value for the current cycle should probably be modifiable. There isn't any mechanism to do this yet aside from modifying the database directly.

How to deploy...

How to setup your dev environment ...

The MoviePolls site should crossreference to the corresponding MovieNight instance to direct users there when a movie is watched.

Requirements:
Show some sort of notification if a movienight is planned (and/or running)
- maybe with some sort of closeable banner?
Save link to the MovieNight instance in the database

Questions to be asked:
Maybe use a countdown for the upcoming movienight?
Should we request the movienight url to check if the movie is running already?

Paginate the list on the history page. Currently, it only displays the previous 10 cycles.

Create links just for RSS that pass the pin in as a URL parameter so that after clicking on the link you get straight to the movie.

Clean up input tests
Improve enabled/disabled handling
extract logic into distinct functions to improve readability

Dockerfile and docker-compose needed

When adding a movie there is a field for the user who added the movie.
This field is never updated.

For example, this should be valid:

In the readme you described a moderator and admin role and the differences, do you still intend to use that approach?
It seems to be overkill to add an additional moderator role for the currently expected usecases.

Implement a postgresql connector via the database interface

It would be nice to have some tags (i.e. "drama", "comedy") for movies.
It would also be nice to have the ability to filter for a tag (i.e. all movies with the "drama" tag).

Add an option for an unlimited amount of votes for users.