Skip to content
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

Handle protected attachments the same as non-protected attachments #9787

Merged
merged 4 commits into from
Dec 23, 2024

Conversation

Pinkeltje
Copy link
Contributor

@Pinkeltje Pinkeltje commented Dec 21, 2024

Pull Request for Issue #9769 .

Summary of Changes

When setting Protect Attachments to Yes, protected attachments are now "behaving" like non-protected attachments
When testing discovered another bug: When saving message first and then edit and insert attachment, id was not retreived. Result: [attachment=undefined]hash[/attachment]

Testing Instructions

Please test carefully, because there ar so many variables in this file.

@xillibit xillibit added the 6.3 label Dec 21, 2024
@xillibit xillibit added this to the 6.3 milestone Dec 21, 2024
@rich20
Copy link
Member

rich20 commented Dec 21, 2024

Now it doesn't work properly even without protecting attachments. I have uploaded three attachments.
One not inserted in the message
one inserted in the message
set one as private
Bildschirmfoto vom 2024-12-21 17-35-07


Result if you click on edit

g20397

@Pinkeltje
Copy link
Contributor Author

Think it is ok now. Took me a while to find that protected attachments have value 1 in field protected in attachments table where as private attachments have value 32.

@Pinkeltje
Copy link
Contributor Author

@xillibit latest commit is concerning
https://www.kunena.org/forum/k-6-3-0-support/168674-incorrect-use-of-label-for-from_element#232590
Chrome thinks that labels should match id.

@xillibit
Copy link
Member

xillibit commented Dec 23, 2024

My commit change for the title input for quickreply on a subject, when i look with developper tools i have label and id matching : <div class="form-group"> <label for="subject103" class="col-md-12 control-label" style="padding:0;"> **Subject**: </label> <input type="text" id="subject103" name="subject" class="form-control" maxlength="80" value="topic test"> </div>

@Pinkeltje
Copy link
Contributor Author

Yes, that one is ok. So shouldn't be changed. Maybe create seperate issue for Chrome and label "errors". My pull request was added automatically to this pull request, but it gets confusing now.

@rich20
Copy link
Member

rich20 commented Dec 23, 2024

  • Fix for protected attachments - Success
  • Label issue Chrome - Chromium no longer shows an error, so I think it also works with Crome

@xillibit xillibit merged commit c2598f5 into Kunena:K6.3 Dec 23, 2024
4 checks passed
xillibit pushed a commit that referenced this pull request Jan 6, 2025
…ents (#9787)

* Handle protected attachments the same as non-protected attachments

* Fix for protected attachments

* Fix errors in Chrome with label

* Label issue Chrome - fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants