Instead of an upgraded version with my data, I have an empty one. On top of that the output in the terminal I posted suggest that when a DB is configured, one should 'refuse' the option which I think is no out of a yes/no option. I wouldn't expect any changes to happen, certainly not overwriting a file that had the db config, especially not when in other cases, at least there is a question if a file should be changed.
So I don't know at what level the best improvement can be made, but as it is it is certainly not good.
My suggestion: - if chosing (yes/no) now at current formulation of the text, do not change anything or behave the same as the other ones ( show diff, etc ) - make the updater simply process db config and leave it unchanged, no matter the config - if for some reason current behaviour is wished for, explain in text what happens and have the script make a backup
Just to be clear, I think the current behaviour is a major bug and has no place in an enterprise environment and it made me reconsider the use of Xwiki, because I simply don't want to be faced with this type of issue, needing to restore config from backup. Thank you!
Vincent on 09/Oct/25 10:18
hi, I don't know about the components, so thank you for explaining. The thing is that I just had a working Xwiki installation that I apt update as described here: [https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Upgrade/] ( 1.A )
Instead of an upgraded version with my data, I have an empty one. On top of that the output in the terminal I posted suggest that when a DB is configured, one should 'refuse' the option which I think is no out of a yes/no option. I wouldn't expect any changes to happen, certainly not overwriting a file that had the db config, especially not when in other cases, at least there is a question if a file should be changed.
So I don't know at what level the best improvement can be made, but as it is it is certainly not good.
My suggestion: - if chosing (yes/no) now at current formulation of the text, do not change anything or behave the same as the other ones ( show diff, etc ) - make the updater simply process db config and leave it unchanged, no matter the config ( merging new options if needed ) - if for some reason current behaviour is wished for, explain in text what happens and have the script make a backup
Just to be clear, I think the current behaviour is a major bug and has no place in an enterprise environment and it made me reconsider the use of Xwiki, because I simply don't want to be faced with this type of issue, needing to restore config from backup. Thank you!
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
