Closed (fixed)
Project:
File (Field) Paths
Version:
8.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Jan 2022 at 07:37 UTC
Updated:
17 Dec 2024 at 09:04 UTC
Jump to comment: Most recent
Comments
Comment #2
tklawsuc commentedAlthough 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 field. "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.
Comment #3
solideogloria commentedThe above description is correct. I agree that it should be made clearer in the UI.
If you select "retroactive", the setting only applies on save (causing the updates to run). After the operation completes, and refreshing the page, the option won't be selected anymore. This is the correct behavior.
Comment #6
megachrizHere 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.
Comment #7
marco.bthx megachriz - your proposal for the field descriptions in #6 makes it clear to me.
Comment #10
volegerThanks