Understand the difference between Retroactive updates versus Active updating

Created on 17 January 2022, almost 3 years ago
Updated 29 May 2023, over 1 year ago

Problem/Motivation

Thx for the great work!

I can't understand the difference between the described features Retroactive updates versus Active updating, especially what the term 'active' here means.

  • Retroactive updates - rename and/or move previously uploaded files.
  • Active updating - actively rename and/or move previously uploaded files.

Proposed resolution

Thank you in advance for a clarification and for eventual updating of the features description on the project page.

πŸ’¬ Support request
Status

Active

Version

1.0

Component

Documentation

Created by

πŸ‡©πŸ‡ͺGermany marco.b

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¨πŸ‡¦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.
  • πŸ‡³πŸ‡±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.

  • Pipeline finished with Failed
    21 days ago
    Total: 265s
    #336091
  • πŸ‡©πŸ‡ͺGermany marco.b

    thx megachriz - your proposal for the field descriptions in #6 makes it clear to me.

  • Pipeline finished with Success
    1 day ago
    Total: 414s
    #356146
  • Pipeline finished with Skipped
    about 8 hours ago
    #357354
  • First commit to issue fork.
  • πŸ‡ΊπŸ‡¦Ukraine voleger Ukraine, Rivne

    Thanks

Production build 0.71.5 2024