Provide unstable1 -> unstable2 upgrade path documentation for #1836934: Entityreference selection handler for project behaviors [#1955726]

Splitting this off from #1836934: Entityreference selection handler for project behaviors.

In that issue, we're fixing the default release and project issue node types to make use of a new entityreference selection handler that's tied to project behaviors instead of explicit node types. Given #1852386: Create point 7.x releases of Project* - support database updates between [un]stable releases we're supposed to support unstableN => unstableN+1 DB updates for D7. So, in theory, we want a DB update that swaps out the field settings to make use of the new selection handler. I'm not 100% sure this is a good idea, since we might wipe out existing field customizations D7 sites have already done to these node types. But, I don't want to spend time worrying about it now, so I'm splitting this off for Greg to worry about. ;)

Thanks,
-Derek

Comments

Comment #1

greggles

he/him

English

Denver, Colorado, USA

commented 10 October 2013 at 13:04

Title:

Provide unstable1 -> unstable2 upgrade path for #1836934: Entityreference selection handler for project behaviors

» Provide unstable1 -> unstable2 upgrade path documentation for #1836934: Entityreference selection handler for project behaviors

I'm not 100% sure this is a good idea, since we might wipe out existing field customizations D7 sites have already done to these node types.

Yeah, I think a comment in the UPGRADE.txt that mentions this issue is the best solution so we neither ruin people's data with a half-baked update nor spend a lot of time coming up with the perfect solution. Updating metadata to reflect that.

I did come across #2108693: Node changes field settings need to be updated during upgrade from unstable which is not directly related to project/project_issue but it seems like the settings for it are being managed in project_issue's hook_updates so far so maybe it does deserve to be fixed there OR just documented there? Once I find the true root cause I'll have more of a sense of where I want to fix it.