- πΊπΈUnited States smustgrave
With D7 approaching EOL soon I've started the process of triaging the D7queue here. Since there hasn't been any movement on this going to close out.
Currently the entire schema is full of single value properties (settings) which could actually all be moved into one serialized data property. Is there a reason why every setting currently has its own column? Using a data property for the settings makes a lot of sense if you ask me and it is also way more flexible and could be used by other implementing modules to store additional information to customize specific quizzes, etc.
Closed: outdated
5.0
Code - Quiz core
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
With D7 approaching EOL soon I've started the process of triaging the D7queue here. Since there hasn't been any movement on this going to close out.