I am experiencing a bizarre bug in EPiServer Commerce when creating a new Category / Node.
The steps I take to replicate this bug every time are:
Does anyone have any insight? Is this a problem others have experienced? How can this be fixed?
I just tried to reproduce this in the latest (yet to be released) version and wasn't able to. It's definately possible that there could have been a bug there that have been fixed.
I suggest that you register an incident with our support and they might be able to help you: http://world.episerver.com/Support/Register-Support-Incident/
Thank you for your response. I cannot submit an incident report for some reason. (Please see this screenshot)
I can get one of the other developers here to submit an incident for me. Although, it would be great to have the ability to do this with my own account.
I see. I think that in order to be able to register incidents your account here on episerver world need to have something called "partner access". I'm not sure but I think you can try mailing the web masters for world at email@example.com about that.
Here is a screencast of the bug if anyone would like to view what is happening: http://www.screencast.com/users/nbaiel/folders/Default/media/3934f479-5ade-4917-be35-6c6adc18b9b6
Can you replicate that using other browser/machine?
Sure thing. This has happened on various machines running Windows 7. I have replicated this issue in the latest version of Firefox and also IE10. http://screencast.com/t/znwMjc5jcd
I Can Confirm I can replicate this, You need to raise this with EPiServer.
Click On Some Existing Category, Press Cancel.
Click On New Node and press save, Previously selected category will be updated.
There is a cache settings that you can try in ecf.app.config <Cache enabled="false" appTimeout="0:0:0" />
We have an incident report open for this issue and EPiServer have yet to resolve.
Thank you for confirming that this bug can be replicated outside our environment. We'll try the cache setting you suggested.
Thanks for the detailed description of the issue, we have now been able to recreate this issue both on R2 and R3 and reported it as a bug.
Bug #108182: Cancel editing on one catalog node and instead create a new one will have the changes written to the one already present.
Once it has been through triage and accepted as a bug you can view it online: http://world.episerver.com/Support/Bug-list-beta/