Closed (works as designed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
migration system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
8 Jan 2014 at 12:12 UTC
Updated:
8 Feb 2015 at 03:46 UTC
Jump to comment: Most recent
Comments
Comment #1
chx commentedComment #2
dawehnerI wonder whether we could just deal with the config objects instead of the entity types internally?
Comment #3
chx commentedThis is now very doable. The IS listed these problems:
> However, at the writing of this issue we have no ways to express that a) the entity needs to be upgraded
This is now the default.
> in case of a conflict, the destination property actually set wins.
We migrate into a D8 site.
> This likely would need updates to the Row class to collect the
$propertyargumentssetDestinationPropertywas called with.Which is indeed done.
> This mechanism will be added but until then this is not doable and after that I do not have a burning desire to write a whole migration for a single variable.
Eh, why not.
Comment #4
ultimikeHmm - I'm going to assume that we're talking about the "Who's online" block and say that there is no "User activity" (seconds) setting in D8 (http://note.io/1IpqfIO) similar to in D6, so this is a non-issue.
I confirmed that the D6 "User list length" setting is migrated in D8 (now called "Items per block") but there isn't a test for it (or for any of the other core block settings, so I'll open a new issue #2422229: D6->D8 Core block migrations missing settings tests for that.
Feel free to re-open this issue if I'm incorrect.
Thanks,
-mike