When I use Auto publish to a location that is set up to work with uDateFoldersy, all the imported nodes are placed in a month according to the current date.
If I then publish the nodes one by one they're moved to the correct year/month structure.
It's like "Auto Publish" isn't the same as "Save and Publish" ?
I'm not sure whether it's CMS Import or uDateFoldersy that's the problem ?
Sorry I don't receive notifications anymore on forum threads but I thinbk you can create an extra property and in udatefoldersy config specify that field as the date field. It' s because Umbraco always stores current date as create date. The date will be edited in DB directly after the import but then the datefolder functionality is already been called.
Auto Publish doesn't play nice with uDateFoldersy
When I use Auto publish to a location that is set up to work with uDateFoldersy, all the imported nodes are placed in a month according to the current date.
If I then publish the nodes one by one they're moved to the correct year/month structure.
It's like "Auto Publish" isn't the same as "Save and Publish" ?
I'm not sure whether it's CMS Import or uDateFoldersy that's the problem ?
Anything on this ?
Sorry I don't receive notifications anymore on forum threads but I thinbk you can create an extra property and in udatefoldersy config specify that field as the date field. It' s because Umbraco always stores current date as create date. The date will be edited in DB directly after the import but then the datefolder functionality is already been called.
Aah - sneaky :-)
/Chriztian
It's the only way to achieve this..
So during import I should do like this
and then afterwards switch to
when I'm done importing ?
You should set the alias for uDateFoldersy to
date(if that's the new property) and then tell CMSImport to fill that one with the createdDate too.Then it'll have the correct value when CMSImport triggers the publish event. I guess...
is working on a reply...