Adding object to a page results in version conflict

Hello there

Not sure if it is only with my installation, but there is an odd behavior when adding an object to a page.

  1. I select the object to add
  2. I fill in the properties of the object

This is what I believe happens:
When adding an object, the page is saved as new major version programmatically. If I add the property values and save the page, the current view of the page is without the programmatically added version for the object, which in turn triggers the merge wizard.

This is much better with 11.10.4 then it was with 11.3, but yet, this is not the expected behavior IMHO.

Does someone else experience the same behavior?
Thank you

Hi @Beat_Burgener,

If I understand it properly you got a version conflict each time you perform the following scenario:

  • add an object
  • edit the properties of the object

in xwiki 11.10.4? It’s definitely an unexpected behaviour: you should raise a JIRA issue with some details on how to reproduce the bug.

@surli, this does not happen since 11.10.4 but already in 11.3, but in 11.3 it was way worse …

The steps are:

  1. Edit dropdown, Objects
  2. In the new object field, type a class like “TagClass”
  3. Hit Add, which will show you the properites of the class (in this case, Tags)
  4. Add some tages to the tags field now visible
  5. Add some summary notes (as we require this)
  6. Save and view
  7. Conflict

BUT, since I cleared the browser cache regarding the other challenge reported with the summary field being wiped, I cannot reproduce this problem any more?! So it looks like this was an cache issue …

The warning on conflict mechanism started to be integrated in 11.2 or 11.3 actually and the early version were not really stable, so not a real surprise if you have been hit by some weird behaviours in those versions. We improved it later in the cycle around 11.4/11.5. And it indeed relies on some javascript, so it’s possible that clearing the cache helped here.

Now the feature is still new, so it’s possible that we don’t handle properly some corner cases: don’t hesitate to open an issue if you encounter the problem in the future.

Okey, sure I will if I stumble upon again. It was not only on my computer but consistently on another employees one … Thank you and have a great weekend