search

mediacms-io / mediacms

MediaCMS is a modern, fully featured open source video and media CMS, written in Python/Django and React, featuring a REST API.
https://mediacms.io
GNU Affero General Public License v3.0
2.67k stars 495 forks source link

Summary of improvement suggestions for some functions of Mediacms #768

Closed cdorsat closed 1 year ago

cdorsat commented 1 year ago

Suggestions for improving some functions of Mediacms

I like this system very much, thanks to the hard work of the developers. The current test found the following problems:

File Upload:

  1. The file cannot be uploaded when the file name is too long or has special characters (this is a BUG).

  2. When multiple files (the average size of a single file is 1.4G) are uploaded and transcoded at the same time, the upload of the second or third file fails (this is a BUG). The situation when an error occurs is as follows: Capture1

User experience (function improvement):

  1. Add the logo corresponding to the user on the player homepage and the left side of the media file.

Youtube compare

User Icon

  1. The mouse pointer cannot be automatically hidden when it is not in full screen state.

  2. In the About section of the user profile page, the text processing is not beautiful enough, such as support for text wrapping, color Logo, and text editing.

  3. The player adds the HD logo. Mediacms current: Untitled

About HD Icon: HD Icon 2 HD Icon

  1. The player cannot play webm format and 2160p HD files.

  2. Add multi-language function, and the translation work can be done by the user.

  3. Tags do not support text other than English, such as Chinese.

  4. Username does not support the symbol "-", for example: "user-abcd123".

  5. Suggestion for improvement: When a media file containing a playlist is found, the playlist should be displayed in the search content. for example: Untitled

  6. These two buttons. User information and classifications of the entire website may be leaked here, and it is recommended to improve it to ensure the security of the website. Untitled

mgogoulos commented 1 year ago

Thank you for your good words and for taking the time to make these suggestions.

In general I see two categories here, a) bugs, b) feature requests. Ideally each of the bugs should be opened as an issue here, and each of the feature requests as a request on the Discussion section.

It is very hard to track a specific item out of these now and possibly work on it, versus having each of the items filled as an issue (for bugs) and feature requests on Discussions for the requests. Thus each issue or request can have their own tags/priority and text. Also some of the issues would be closed, if they are already opened as duplicates.

cdorsat commented 1 year ago

I am really sorry, the reason is that I am not familiar with the operation and use of Github, I will pay attention next time.

I think the mediacms system is great. The above are the problems I found. For the details of each problem, you can use YouTube as a reference and comparison. It is undeniable that YouTube is worth learning from.

Thanks again for your contributions, I very like Mediacms !

mgogoulos commented 1 year ago

Thanks again for the aim to contribute and the effort!

mgogoulos commented 1 year ago

I see you've opened all of the items as separate ones (and as you've seen I've moved some of them to discussions/feature requests, to reserve the Issues section for problems/bugs mostly) so this can be closed. Thanks!