Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
ViewExecutable
employs a custom serialization mechanism in ::(un|)serialize()
. It fails to populate the the $viewsData
and $routeProvider
member variables, however, so that after serializing and unserializing a view executable, fatals can occur.
Proposed resolution
Populate the member variables properly in ViewExecutable::unserialize()
.
Comments
Comment #2
tstoecklerInterestingly this is also fixed by #2849674: Complex job in ViewExecutable::unserialize() causes data corruption, so marking as related at least. This is a separate symptom, though, so keeping open for now.
Comment #9
pameeela CreditAttribution: pameeela commented@tstoeckler found this triaging an old issue that was postponed. You seemed to think this might not be fixed in that other issue, do you think it's still a bug?
Comment #10
tstoecklerHey there. It does seem to have been fixed by #2849674: Complex job in ViewExecutable::unserialize() causes data corruption like I noted in #2 so yes, I think, this can be closed as duplicate.
#2699957: routeProvider is null in ViewExecutable was also opened (and discussed) before that went in so I think that can also be closed as a duplicate of #2849674: Complex job in ViewExecutable::unserialize() causes data corruption, will do that now.
Thanks for the pointer!
Comment #11
pameeela CreditAttribution: pameeela commentedYay! Two in one! Thanks Tobias.