I’m getting an error when accessing the page to create a new post, however only when I have at least one media uploaded with that account, and there is no issue with /~/<blog>/<slug>/edit
GET /~/Yoloswagg/new/ text/html:
=> Matched: GET /~/<blog>/new (new)
=> Error: Error rendering Tera template 'posts/new'.
=> Error: Failed to render 'posts/new'
=> Error: Variable `form.cover` not found in context while rendering 'posts/new'
=> Error: Template 'posts/new' failed to render.
=> Outcome: Failure
=> Warning: Responding with 500 Internal Server Error catcher.
=> Response succeeded.
About the cover selector, to be frank I don’t really like how medias works currently, it feels strange to go to /medias/ to change your avatar. It feels strange too to upload medias on a page different than the one where you write your posts (which will hopefully be better when we start working on a rich text editor), and choosing from a <select> what media will be the cover feels the same, maybe even worth for peoples having a lot of uploaded medias as the time goes. It can stay like that for the moment, but we will need to address this in the future.
Also make me through of one thing : while it’s using a <select>, you should filter to only show images, not audio content for example (actually the same goes for peoples avatar, currently they can be an audio file)
Yes, I agree the way media are currently working is not ideal. I think we can change it once will we will switch to a new editor, by adding the possibility to upload an avatar directly from the profile edition page, and to add any other media directly from the editor.
Anyway changing how we handle medias is neither the goal nor in the scope of this pr, so even if it’s less than ideal, it shouldn’t affect how we merge this pr (and actually making sure people are not using a song as a picture is not that important as in the end how they select those will be totally changed latter on)