Problem/Motivation
"Active updating" worked well after forcedly changing the upload destination of a file field from public to private and vice versa. It no longer work after the following commit was made.
The following issue is related with this commit.
The setting "Retroactive update" depends on "Active updating" and it will also be fixed when we fix "Active updating".
Some users consider that this function helps to switch the visibility of a file field:
Proposed resolution
I'd like to restore the support of the upload destination change. I believe the condition below to check if the "Active updating" should be applied for fields can be loosen.
if (in_array($source_scheme, array($temporary_scheme, $destination_scheme)) && !empty($wrappers[$destination_scheme])) {
Remaining tasks
- Make a patch
- Review the patch
User interface changes
None.
API changes
None.
Data model changes
None.
If this is not a bug, please feel free to change the category.
Comment | File | Size | Author |
---|---|---|---|
#2 | filefield_paths-add_support_for_different_schemes-2895035-2.patch | 1.44 KB | hgoto |
|
Comments
Comment #2
hgoto CreditAttribution: hgoto at Studio Umi commentedHere is a first patch. I'd like someone to review this.
Comment #3
hgoto CreditAttribution: hgoto at Studio Umi commented