I encountered some strange behaviour when playing around with a custom (local) module and its version.
It seems like the latest module version, who has ever been installed, will remain in key_value > schema.
I uninstalled my module after I applied version 8.0.0.2 to it to "test" the update_hooks, which failed. Then trying to set 8.0.0.0 and re-enabling it again, didn't work. The old version number (.0.2) is still present in table "key_value" > schema and the desired update hooks won't run again.
Which flags in {module}.info.yml or any other configuration are related to the module version?
And how to update the schema value?
Another thing: I updated D8 from 8.0.0 to 8.0.1 by replacing the core, but no database updates were "tracked" within /update.php or "drush updb". But, there are updates in core modules, which didn't get applied @see file block_content.install > block_content_update_8001: there must be a field "block_content.revision_translation_affected", but it does not exist...
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | update_test_module.tar_.gz | 1015 bytes | seppelM |
Comments
Comment #2
seppelM commentedComment #5
pameeela commented@seppelM I know this was a really long time ago, but I see that you are still active on d.o.
I am triaging old tickets, but this is outside of my area of expertise. I wondered if you found a resolution for it? I'm not totally sure whether you were suggesting a specific bug, or asking some questions.
If you think there are aspects of this that are still unclear, perhaps we can fix with documentation? Otherwise feel free to close it, if you are thinking 'well this was 4 years ago, I can't remember' :)
Comment #6
pameeela commentedComment #7
pameeela commented