how to get across history being disabled by default in 1.13.28 #4778
vladak
announced in
Announcements
Replies: 2 comments
-
For example with
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Alternatively, if using read-only configuration, enable the history there, i.e.: <void property="historyEnabled">
<object idref="true"/>
</void> Then merge the configurations and upload them to the webapp. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The changes in #4746 made history disabled by default. I belive most of the deployments run the indexer with the
-H
option which will make it enabled, however there is stil a potential for breakage. This has just bitten me when upgrading so I will describe the scenario here.If you run the indexer also with
-W
and-U
, this is most probably something that will be taken care of automatically on next reindex. Otherwise, read on.With pre-exising configuration, the
historyEnabled
will not be recorded/serialized in the XML file, I believe because it does not differ from the default (might consider this for #2329). After deploying the 1.13.28 webapp with the changes and adding new project via the API, it will have history disabled because it is inherited from the global configuration which has it now set to false.The solution is to enable history in the webapp and only then add the project. Lastly, save the configuration to disk as usual.
Beta Was this translation helpful? Give feedback.
All reactions