- π¨π¦Canada tklawsuc
Although this is an old post, I came across it having the same question. Since I couldn't find the answer, I did a trial with both options. "Retroactive" will run through all the nodes and update the paths right after saving the content type. "Active updating" will only update the path when the node is saved. So use retroactive if you want to update all paths immediately. Otherwise use "Active updating" for a more manual process where you have to update/save each node.
- First commit to issue fork.
- Merge request !27Expanded descriptions of the retroactive_update and active_updating options. β (Merged) created by megachriz
- π³π±Netherlands megachriz
Here is my proposal for the field descriptions:
Retroactive update
Move and rename previously uploaded files. After saving the field settings, the paths of all previously uploaded files will be updated immediately. This will only occur once. So after the operation is done, this option will be disabled again.
Warning: This feature should only be used on developmental servers or with extreme caution.Active updating
Actively move and rename previously uploaded files as required. If necessary, the paths of previously uploaded files are updated each time the entity they belong to gets saved.
Warning: This feature should only be used on developmental servers or with extreme caution. - π©πͺGermany marco.b
thx megachriz - your proposal for the field descriptions in #6 makes it clear to me.
- First commit to issue fork.
-
voleger β
committed 6cd90fd3 on 8.x-1.x authored by
megachriz β
Issue #3258865 by megachriz, marco.b, tklawsuc, solideogloria: Document...
-
voleger β
committed 6cd90fd3 on 8.x-1.x authored by
megachriz β