Just noticed a couple issues trying to use uDateFoldersy (with and without uBlogsy) in v6.0.3
1 - Null reference exception in ContentService_Creating when creating a new node It looks like e.Entity is now null in this event - not sure if this changed in a recent version? Anyway, replacing this line:
if (!ConfigReader.Instance.GetTargetDocTypeAliases().Contains(e.Entity.ContentType.Alias)) { return; }
with:
if (!ConfigReader.Instance.GetTargetDocTypeAliases().Contains(e.Alias)) { return; }
seems to fix that issue.
2 - Nothing happening on create/save/publish/etc Everything appears to be configured properly, but the DateFolders never get created on any of these events. I debugged and it looks like everything stops when it hits the Flagged checks. My guess is these were a workaround for Umbraco calling the event several times, but I wonder if that got fixed in v6.0.3? If I comment out those lines (117-127), it seems to work again.
I haven't dug in too deep on #2 yet, just wanted to let you know and see if you've ran into this yet.
Thanks for your hard work on what looks to be an awesome package :)
Thanks for the big report. Your completely correct with #2.it's a work around for an umbraco big which they now fixed. Now my workaround is a bug. Doh.
DateFolders in 6.0.3
Hi Anthony,
Just noticed a couple issues trying to use uDateFoldersy (with and without uBlogsy) in v6.0.3
1 - Null reference exception in ContentService_Creating when creating a new node
It looks like e.Entity is now null in this event - not sure if this changed in a recent version? Anyway, replacing this line:
with:
seems to fix that issue.
2 - Nothing happening on create/save/publish/etc
Everything appears to be configured properly, but the DateFolders never get created on any of these events. I debugged and it looks like everything stops when it hits the Flagged checks. My guess is these were a workaround for Umbraco calling the event several times, but I wonder if that got fixed in v6.0.3? If I comment out those lines (117-127), it seems to work again.
I haven't dug in too deep on #2 yet, just wanted to let you know and see if you've ran into this yet.
Thanks for your hard work on what looks to be an awesome package :)
Thanks,
Tom
Thanks for the big report. Your completely correct with #2.it's a work around for an umbraco big which they now fixed. Now my workaround is a bug. Doh.
Not sure what #1 is though. Will look into it.
is working on a reply...