I started this post as a plea for help. While writing it, I've solved the problem, but thought I may as well continue in case anyone else has the same problem.
I created a new script node in settings, but after initial creation, the script wasn't fully generated, and in the settings content tree where I created the new script, there was just the loading image sitting there.
I couldn't right click the new script and select delete. In fact, I couldn't right click and select anything anywhere in the backend - the options just appeared and disappeared before I can select anything.
I tried logging in and out. I tried recycling the application pool. I then tried restarting IIS. None of the above worked. But then I worked out that if I restarted IIS, the content tree was collapsed, and I could use the right click options again. So I deleted the folder above the new script, being careful not to open the folder first, and that deleted the new script as well. All now seems well. Hope that helps someone at some point in time!
Thanks for sharing this tip with us. I asume this is version 4.7 you have experienced this issue on? Seem to be a bit buggy to me so perhaps it should be reported on codeplex if you and others consider this a bug as well? Then there is a chance that the core team notices and tries to reproduce the issue to decide wether or not this is a bug that needs to be fixed. The more votes on codeplex the more likely it is that it's in fact a bug and the more likely it is that this get fixed with the next release.
Just out of curiosity why are you creating the script inside Umbraco instead of on your file system?
I've since been able to replicate the problem on a different Umbraco install - it only appears to happen when creating a script below a folder - so I've reported the issue on Codeplex as you suggested - see http://umbraco.codeplex.com/workitem/30293
Be interesting to know if anyone else has encountered this problem.
It was my first attempt to create a script inside of Umbraco - I normally use the file system. And I think I'll be using the file system in future!
I just voted for this issue on codeplex. Thanks for taking the time to report this. It might be a minor bug but of course this stuff should work without any problems.
I always use the filesystem but in some situations you don't have filesystem access and need to use the script folder in Umbraco...and then this could potentially be a showstopper.
new script node stuck in tree
I started this post as a plea for help. While writing it, I've solved the problem, but thought I may as well continue in case anyone else has the same problem.
I created a new script node in settings, but after initial creation, the script wasn't fully generated, and in the settings content tree where I created the new script, there was just the loading image sitting there.
I couldn't right click the new script and select delete. In fact, I couldn't right click and select anything anywhere in the backend - the options just appeared and disappeared before I can select anything.
I tried logging in and out. I tried recycling the application pool. I then tried restarting IIS. None of the above worked. But then I worked out that if I restarted IIS, the content tree was collapsed, and I could use the right click options again. So I deleted the folder above the new script, being careful not to open the folder first, and that deleted the new script as well. All now seems well. Hope that helps someone at some point in time!
Hi James
Thanks for sharing this tip with us. I asume this is version 4.7 you have experienced this issue on? Seem to be a bit buggy to me so perhaps it should be reported on codeplex if you and others consider this a bug as well? Then there is a chance that the core team notices and tries to reproduce the issue to decide wether or not this is a bug that needs to be fixed. The more votes on codeplex the more likely it is that it's in fact a bug and the more likely it is that this get fixed with the next release.
Just out of curiosity why are you creating the script inside Umbraco instead of on your file system?
/Jan
Hi Jan,
Yes I was using 4.7
I've since been able to replicate the problem on a different Umbraco install - it only appears to happen when creating a script below a folder - so I've reported the issue on Codeplex as you suggested - see http://umbraco.codeplex.com/workitem/30293
Be interesting to know if anyone else has encountered this problem.
It was my first attempt to create a script inside of Umbraco - I normally use the file system. And I think I'll be using the file system in future!
James.
Hi James
I just voted for this issue on codeplex. Thanks for taking the time to report this. It might be a minor bug but of course this stuff should work without any problems.
I always use the filesystem but in some situations you don't have filesystem access and need to use the script folder in Umbraco...and then this could potentially be a showstopper.
/Jan
is working on a reply...