You found a bug! We've classified it as
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
Unanswered: Deletion of fiddles from sencha fiddle
Does anyone out there know how to delete a fiddle from sencha fiddle? I have a lot of fiddles that are not really of any use and I would like to get rid of them. I cannot seem to find a way to do this.
If you are logged in and viewing your own Fiddle, you should be able to delete them using the 'Delete Fiddle' menu option under the red 'Admin' button (above your code).
Deletion of Fiddle
Thank you for responding to my thread. I was able to get past the issue of not seeing the delete button. Interestingly enough, I was logged in a as a different user and seeing the fiddles from a different user name that I own. I did not know that was possible. When I logged in under the correct user, the admin button appeared.
I am still unable to delete however. When I attempt to delete a fiddle, the browser hangs in a disabled state, with the "deleting..." icon displayed in the center. It never returns to a normal state and the fiddle is never deleted. I tried this with different fiddles on different browsers all with the same result. Any ideas on that?
interesting... I see the following error in my browser console when I attempt to delete a fiddle.
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3)
Timestamp: Fri, 7 Mar 2014 19:23:46 UTC
Message: 'firing' is null or not an object
I have the same problem with Chrome. After I press the 'Delete Fiddle' button, I get the following error:
Uncaught TypeError: Cannot read property 'apply' of undefined app.js:1
(anonymous function) app.js:1
(anonymous function) VM120:6
Can't Delete my Fiddles...
I am also unable to delete my fiddles from sencha fiddle. Anyone help me to delete it urgently.
Yep, looks like a bug. Thanks for the report! I have opened a bug in our bug tracker.