From your stack trace it sounds like the stylesheet doesn't actually exist (its null).
Have you tried refreshing the tree by right clicking on the root node and choose Refresh Tree? If you look at the file system is there actually a css-file? Maybe double check security settings - Network Service should have at least Modify access to the css-folder.
yes I have tried refreshing multiple times, the node will not go away.
The file was there originally, now it is not.
So I created a new file to be there and tried to delete it again.
It deletes the file, but still not the node from the tree.
The permissions are correct, I created a new style sheet that I can actually use and add styles to and that works. I just cannot delete this one node, it just won't go away.
But the file you created, did you give it the same filename as the one node that doesn't seem to go away?
If style1.css is shown in the tree under the CSS-folder and is the one node that throws errors, doesn't it make a difference if style1.css is also present in the filestructure within the Css folder?
I'm a bit unsure if its the same file that is created again, deleted, but remains in the tree as a node...
Stylesheet won't delete, can't add styles to it
I have this style sheet that I can't add any styles to, and I can't delete it.
When I try to delete it, I get this error:
At /umbraco/tree.aspx?rnd=03da401d-560b-4f2d-afef-c8ef1cc886ab&id=1131&treeType=stylesheetProperty&contextMenu=true&isDialog=false (Referred by: http://lakepowell.stage.rtp.com/umbraco/TreeInit.aspx?app=settings): System.ArgumentNullException: Value cannot be null. Parameter name: value at System.Web.Caching.CacheEntry..ctor(String key, Object value, CacheDependency dependency, CacheItemRemovedCallback onRemovedHandler, DateTime utcAbsoluteExpiration, TimeSpan slidingExpiration, CacheItemPriority priority, Boolean isPublic) at System.Web.Caching.CacheInternal.DoInsert(Boolean isPublic, String key, Object value, CacheDependency dependencies, DateTime utcAbsoluteExpiration, TimeSpan slidingExpiration, CacheItemPriority priority, CacheItemRemovedCallback onRemoveCallback, Boolean replace) at System.Web.Caching.Cache.Add(String key, Object value, CacheDependency dependencies, DateTime absoluteExpiration, TimeSpan slidingExpiration, CacheItemPriority priority, CacheItemRemovedCallback onRemoveCallback) at umbraco.cms.businesslogic.cache.Cache.GetCacheItem[TT](String cacheKey, Object syncLock, CacheItemPriority priority, CacheItemRemovedCallback refreshAction, CacheDependency cacheDependency, TimeSpan timeout, GetCacheItemDelegate`1 getCacheItem) at umbraco.cms.businesslogic.web.StylesheetProperty.GetStyleSheetProperty(Int32 id) at umbraco.cms.businesslogic.web.StyleSheet.get_Properties() at umbraco.loadStylesheetProperty.Render(XmlTree& tree) at umbraco.cms.presentation.tree.LoadTree(String treeAlias) at umbraco.cms.presentation.tree.Page_Load(Object sender, EventArgs e) at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at umbraco.BasePages.BasePage.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain
From your stack trace it sounds like the stylesheet doesn't actually exist (its null).
Have you tried refreshing the tree by right clicking on the root node and choose Refresh Tree? If you look at the file system is there actually a css-file?
Maybe double check security settings - Network Service should have at least Modify access to the css-folder.
- Morten
yes I have tried refreshing multiple times, the node will not go away.
The file was there originally, now it is not.
So I created a new file to be there and tried to delete it again.
It deletes the file, but still not the node from the tree.
The permissions are correct, I created a new style sheet that I can actually use and add styles to and that works. I just cannot delete this one node, it just won't go away.
But the file you created, did you give it the same filename as the one node that doesn't seem to go away?
If style1.css is shown in the tree under the CSS-folder and is the one node that throws errors, doesn't it make a difference if style1.css is also present in the filestructure within the Css folder?
I'm a bit unsure if its the same file that is created again, deleted, but remains in the tree as a node...
- Morten
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.