New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong permissions to photos in PMs #5721
Comments
This isn't coded at all and it could mean much work to implement it. I would prefer just to hide the functionality to post pictures than to add this whole functionality. |
As the initial problem was fixed with this milestone, I'd rather prefer it really fixed then totally useless as it is at the moment. |
The problem is that it can get really complicated to solve and test. So this could easily move the whole release some time in the future - and this is time that we then don't have for things like AP. Since now I heard that Mastodon will remove OStatus in the beginning of the next year, I really would prefer having more time for AP. At this time of the RC, we really shouldn't add complicated things any more, since we don't have much time testing it. |
Then we should remove this feature from the UI until it is fixed. At the moment it is totally broken and useless and in this state a blocker. |
I tried to find the Javascript that does invoke the picture browser. I haven't found it. When we want to replace the picture browser with a button that simply adds |
Just remove the button for this release. |
No. Before the change, the button just inserted that |
hmm difficult. Here is the js code for inserting bbcode formations. This code opens also the image browser when the element which should be inserted is the |
The workaround is ugly - but working. |
Moving milestone then. There's only the relationship issue to go before we can wrap up this release. |
This is now coded, need some testing. |
Tests are under way... |
Works at least between RC and RC, locally and remote. |
@ben-utzer reported in the support forum that the permissions of newly uploaded photos in private messages don't get the correct permissions in the current 2018.08-RC code.
Additionally the reader of a PM don't get remote authed when opening the PM so that the image permissions have to be set to public manually after the sending of the PM so that the image can be viewed in the PM by the receiver.
Followup to #5544
The text was updated successfully, but these errors were encountered: