Problem/Motivation
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork schemadotorg-3548302
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
jrockowitz commentedComment #5
jrockowitz commentedComment #7
ultimikeWhen trying out the latest -dev release (after this MR), I went to the /admin/config/schemadotorg/settings/types page and received this fatal error:
Maybe the
jsonld_valuesvalue isn't initialized properly?I tried adding
jsonld_values: { }to my localschemadotorg_additional_type.settingsconfig, to no avail.-mike
Comment #8
jrockowitz commentedDid you run `drush updb`?
Comment #10
jrockowitz commentedYep, the update hook is missing. I commited the fix the 1.0.x-dev.
Comment #11
ultimikeI did some debugging and I think the issue is with
ignored_typesfromschemadotorg_additional_type.settings- I ran out of time before I found a reasonable fix.I can circumvent the issue by adding
|NULLto the$valueargument of:-mike
Comment #12
ultimikeSetting back to Fixed, as I think this was just a bad config issue on my part.
As part of my earlier debugging attempts with this, I had manually added an
ignored_types: {}to my active config. At some point after adding this is when I ran the update hooks and I think this is where things went just a teeny bit sideways for me.I just did the following and all appears to be working fine on my local now:
ignored_types: {}schemadotorg_additional_type_update_10003()andschemadotorg_additional_type_update_10004()hooks toschemadotorg_additional_type_update_10013()andschemadotorg_additional_type_update_10023(), and then re-ran database updates.Sorry for the false alarm!
thanks,
-mike
Comment #14
jrockowitz commentedYeh, I was also looking into this and couldn't reproduce the bug.