Press Ctrl / CMD + C to copy this to your clipboard.
Copied to clipboard
Flag this post as spam?
This post will be reported to the moderators as potential spam to be looked at
Topic author was deleted
Mar 04, 2014 @ 16:31
v7.0.4 Creating phantom nodes
I'm trying to pin this down to DateFolders or the core.
But when creating a new item, it works but it's also creating phantom nodes that go unpublished.
They have no name so umbraco simply keeps incrementing the name (i.e. blank, (1), (2), (3))
The first file it creates has no name (blank) and it makes it undeleteable (500 server error). To fix you have to give it a name; attempt to publish (which fails), but then it becomes deleteable.
Heya, it may well be a problem (or at least an idiosyncrasy) with the core. I've just installed DateFolders in 7.1.6 and I've downloaded the DateFolders source.
Stepping through the code it seems that selecting a DocumentType after clicking "Create" in the content tree triggers the ContentService.Created event. At this point the Entity has no name etc but is still processed by the DateFolder code.
A simple fix is just to check for the presence of a name on the Entity:
if (itemDocType.Contains(newEventArgs.Alias)) {
if (String.IsNullOrEmpty(newEventArgs.Entity.Name)) {
return;
I have finally had time, to look at this within business hours, I have pushed a new version (2.1.2) with Document_New removed and also fixed a sort issues raised in another post. Hopefully this also fixes this issue
Topic author was deleted
v7.0.4 Creating phantom nodes
I'm trying to pin this down to DateFolders or the core.
But when creating a new item, it works but it's also creating phantom nodes that go unpublished.
They have no name so umbraco simply keeps incrementing the name (i.e. blank, (1), (2), (3))
The first file it creates has no name (blank) and it makes it undeleteable (500 server error). To fix you have to give it a name; attempt to publish (which fails), but then it becomes deleteable.
Any ideas?
Comment author was deleted
It puts the blank items in the current month/year.
I don't think it's directly a core issue anymore.
I'm running into this same problem, too!
I had the same problem.
I downloaded the source code to debug it.
I don't understand why when I create a new node (ItemDocType) on event Document_New the new node is moved to the current date tree folder.
I removed completely the code on Document_New event and everything seems to work fine.
kipusoep, why are you moving the node on Document_New event?
Hi Kevin and others
Has this been reported on the issue tracker?
/Jan
Comment author was deleted
@Jan, I think it's possibly a package issue and not a core issue.
Not entirely sure.
Ok, fair enough then :)
Have fun at the uWestFest mate - I'm having the blues for not going. But perhaps I'll be able to make it next year.
/Jan
Has anything ever happened with this? I really want to keep using this package ;)
Heya, it may well be a problem (or at least an idiosyncrasy) with the core. I've just installed DateFolders in 7.1.6 and I've downloaded the DateFolders source.
Stepping through the code it seems that selecting a DocumentType after clicking "Create" in the content tree triggers the ContentService.Created event. At this point the Entity has no name etc but is still processed by the DateFolder code.
A simple fix is just to check for the presence of a name on the Entity:
I am actually having the same issue with umbraco 7.3 and I have removed this package.
Hi,
I have finally had time, to look at this within business hours, I have pushed a new version (2.1.2) with
Document_Newremoved and also fixed a sort issues raised in another post. Hopefully this also fixes this issueSweet, thanks Matthew. I'll check it out later.
is working on a reply...