Closed (fixed)
Project:
Domain
Version:
7.x-3.x-dev
Component:
- Domain Settings
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Jan 2013 at 14:03 UTC
Updated:
10 Feb 2013 at 21:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
agentrickardHave you run update.php? That should be accounted for in
domain_update_7308Comment #2
danharper commentedYes I have, I think this is due to a failed update in the past but I'm not sure.
I am competent at manually chainging the DB if required if I you can tell me what the structure should be as I think that is the problem (am I correct)
Fortunately this is a test installation which I built from my live installation to make sure the this and other modules upgraded correctly, so whatever the solution I will have to apply to live as well.
Thanks for the quick response.
Cheers Dan
Comment #3
agentrickardI think you can just re-save these options from the 'Content defaults' screen. That should fix it.
/admin/structure/domain/nodes
Comment #4
danharper commentedThis solved the issue.
Cheers Dan
Comment #5
pfrenssenWe are using continuous integration and I could repeat this problem 100%. It is not caused by failed updates but it is a bug in the Domain module.
The problem is caused by the domain module failing to remove the
domain_node_{bundle}variables when a bundle is removed. These variables stay behind and are not updated bydomain_update_7308(). This problem will occur on all websites that have ever removed a content type while the domain module was enabled.This is how the variables would look on a site where the "News" content type was removed.
domain_get_node_defaults()loops over these variables and cannot flip the news variable as it is not an array:Attached patch fixes the problem and contains and update hook that will clean up the stale variables.
Comment #6
agentrickardAh! This is the key point "This problem will occur on all websites that have ever removed a content type while the domain module was enabled."
Thanks.
Comment #7
pfrenssenI have run our test suite overnight and was still getting these notices. I need to investigate a bit further.
Comment #8
pfrenssenThe problem from #7 was not related to the patch. It was caused by a Feature that I forgot to update.
The patch from #5 fully solves the issue for us.
Comment #9
agentrickardCommitted.