- 🇳🇿New Zealand jonathan_hunt
fwiw, I found changing from source field
timestampto source fieldchangedworked for me, no patches needed.
When you have a node migration and run "migrate:import" a second time with the "--update" option it modifies the "changed" value of the node to be the current timestamp and ignores the value from the migration.
Run a node migration.
Run the node migration a second time with the "--update" option.
Fix the entity logic so that rerunning a migration does not change the "changed" timestamp if it is specifically defined in the migration (which is usually is).
Work out where the fix should go.
n/a
TBD
TBD
Active
6.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
fwiw, I found changing from source field timestamp to source field changed worked for me, no patches needed.