You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WireCloud is leaving garbage on the behaviours descriptions when removing a widget using the rest API. The wiring editor is designed to ignore that garbage, but other operations fail if this garbage is found. For example, if you package a workspace with that garbage, and the you try to create a new workspace using this template, the operation will fail.
Steps for getting a corrupted wiring status:
Create a workspace with several widgets, enable the behaviour engine in the Wiring Editor, connect them.
Go to the workspace view, remove one of the connected widgets.
Refresh the browser
NOTE: If you don't refresh the web browser, and you enter into the Wiring Editor view, the wiring status will be fixed because the client part handles this correctly.
Steps for getting an error:
Create a packaged version of the workspace using the Upload to My Resources
Try to create a new workspace using that template
WireCloud will fail with a 500 error code
The text was updated successfully, but these errors were encountered:
aarranz
changed the title
Bug removing widgets from workspace view
Garbage in the behaviours descriptions after removing widgets from workspace view
Oct 27, 2016
jpajuelo
added a commit
to jpajuelo/wirecloud
that referenced
this issue
Oct 27, 2016
WireCloud is leaving garbage on the behaviours descriptions when removing a widget using the rest API. The wiring editor is designed to ignore that garbage, but other operations fail if this garbage is found. For example, if you package a workspace with that garbage, and the you try to create a new workspace using this template, the operation will fail.
Steps for getting a corrupted wiring status:
NOTE: If you don't refresh the web browser, and you enter into the Wiring Editor view, the wiring status will be fixed because the client part handles this correctly.
Steps for getting an error:
The text was updated successfully, but these errors were encountered: