And so my question is - when importing the product specials (which will be a specified doc type for the autofolders) will the products be automatically saved within the relevant alpha folder?
I am more than willing/able to undertake testing of this but at this stage thought I quick question here might be a quicker option so I can get past the tedium of completing documentation.
AutoFolders uses the Document.BeforePublish (or similar) event to move the node underneath the right folder when the document gets published, whereas the CMSImportPackage most likely just publishes the doc/node after it gets created (I haven't worked with CMSImport yet, it might be that the docs only get saved and not published, in which case you have no trouble at all anyway). This means that CMSImport creates a new node, then publishes it at which point AutoFolders takes over to quickly put it in the right pot. So IMHO that should work out nicely.
I have used AutoFolders with dynamically created content in a .Net usercontrol and that seemed to work quite nicely without any problems.
Do Multiple Packages Play Nicely Together
Hi there
I am working on a scope for a new website for a supermarket chain.
They are wanting to have product specials on the site which are date bound.
I was thinking of using both the AutoFolders Package and the CMSImport Package
And so my question is - when importing the product specials (which will be a specified doc type for the autofolders) will the products be automatically saved within the relevant alpha folder?
I am more than willing/able to undertake testing of this but at this stage thought I quick question here might be a quicker option so I can get past the tedium of completing documentation.
Thanks
Nigel
Hi Nigel,
here are my 2 cents:
AutoFolders uses the Document.BeforePublish (or similar) event to move the node underneath the right folder when the document gets published, whereas the CMSImportPackage most likely just publishes the doc/node after it gets created (I haven't worked with CMSImport yet, it might be that the docs only get saved and not published, in which case you have no trouble at all anyway). This means that CMSImport creates a new node, then publishes it at which point AutoFolders takes over to quickly put it in the right pot. So IMHO that should work out nicely.
I have used AutoFolders with dynamically created content in a .Net usercontrol and that seemed to work quite nicely without any problems.
Hope that helps,
Sascha
Hi Sascha
Thanks for your quick response - that sounds very promising.
I definitely look forward to the development stage to see that it works as you outline - man I hate documentation.
is working on a reply...