Closed (fixed)
Project:
Open Social
Version:
8.x-1.x-dev
Component:
Code (back-end)
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Sep 2017 at 14:59 UTC
Updated:
7 Nov 2017 at 11:19 UTC
Jump to comment: Most recent


Comments
Comment #2
ribelHere is PR, which fixes this issue: https://github.com/goalgorilla/open_social/pull/549
Comment #3
wim leershttps://github.com/goalgorilla/open_social/pull/549 contains more information:
(Emphasis mine.)
This is reducing security of Open Social. It also increases vulnerability to link rot and therefore broken content over a longer period of time.
If I were a maintainer of Open Social, I would not accept this. You'd still be free to change the configuration, but I'd recommend against this.
Comment #4
ribelWim Leers, thank you for bringing this to the attention.
I was treating the symptom, not the disease. Because the problem was with local images, not remote.
Now I found that this issue was caused by Drupal Core issue: https://www.drupal.org/node/2528214
In PR, I have reverted Basic HTML text format settings and applied patch to core from the issue.
Please advise if that's correct.
Thanks!
Comment #5
wim leersYes, #2528214: "Restrict images to this site" blocks image style derivatives is then likely the cause of your problems, and is indeed the proper fix! :)
Comment #6
wim leersComment #7
maikelkoopman commentedWill released in version 1.6
Comment #9
wim leers@maikelkoopman I think this is a very bad idea. You've just enabled hotlinking of images. Which means:
Comment #10
maikelkoopman commentedWim, we have added the patch form the 2528214 https://www.drupal.org/files/issues/image_restrict_image_styles-2528214-.... So the option to disable Restrict images for Basic HTML is not enabled now. We have to go forward with a solution, because it is blocking users from uploading images in the ckeditor.
https://github.com/goalgorilla/open_social/pull/549/files
In your previous comment you said 'and is indeed the proper fix!", I was assuming this is okay to move forward?
Comment #11
wim leersThe proper fix is to get #2528214: "Restrict images to this site" blocks image style derivatives fixed in core, and in the mean time, the proper solution is to include that patch. You did that in https://www.drupal.org/commitlog/commit/60333/7a7aae1d1db4354b3e4412b3be... (great!), but you also committed https://www.drupal.org/commitlog/commit/60333/109aa3b5a495aede2ef0c9cac7... (bad!).
I think perhaps https://www.drupal.org/commitlog/commit/60333/109aa3b5a495aede2ef0c9cac7... was an accidental commit then? :)
Comment #12
bramtenhove commentedHi Wim,
The changes in 109aa3b5a495aede2ef0c9cac7b29d8c812b57d1 have been undone in 7a7aae1d1db4354b3e4412b3be5cff5fd48edd0a.
We do not squash the commits when merging pull requests on GitHub, this is probably where the confusion comes from.
The final diff that was committed is https://github.com/goalgorilla/open_social/pull/549.patch. Hope that clears everything up ;)
Comment #13
wim leersEh … ok. This is exactly why you need to squash commits. All good then, but your commit history is now super confusing and pretty useless (since it first makes a change and then undoes it).
It's fine to not squash commits that touch different areas, to have logical commits, but these aren't remotely logical.
Anyway: 👍
Comment #14
bramtenhove commentedI see your point.
@jochemvn mentioned we can start squashing commits when a PR on GitHub is closed.
Anyway, thanks for raising the point! I’ll throw it in the group.
Comment #15
wim leersCool :)