Fork without renaming leads to "We're having a problem" message
Reproduction Steps
On the back end:
- Setup a clean instance of Occam.
- Pull down the XSim-collab object from occam.social (
occam objects pull QmSyF8TfqeXDMkffDhXXmv4rP99L3bh2PqYyDnzxNtp941
).
Then on the front end:
- Create an account.
- Search for xsim-collab.
- Navigate to the xsim-collab object page.
- Attempt to fork the object (Lightning-bolt icon > "Fork"). Do not rename the object when forking.
Expected Behavior
Object should be forked.
Actual Behavior:
User sees the "We're having a problem" page offering no explanation as to what went wrong.
Per @wilkie, this is due to our attempt to deduplicate objects. Forked objects are stored in the same location as the object from which they were forked. If the object is renamed during the fork, or the ownership would be different from the original then the forked object is given a different id. The problem is trying to have two versions of the same object with the same name.