Michael posted a very nice tip in the German RedDot Usergroup forum: When you want to publish all pages of a certain SmartTree branch to a separate folder (e.g. all news pages into yourdomain.com/news/) and assign a publication package to the navigation list, the parent page of this branch still gets published to the folder level above.
You can publish the news door page into the news-folder by simply including the path before the file name (see “page properties”): news/index.html
Note: Your Windows RedDot user must have write access to all sub folders inside the CMS directory to create the news-folder in his temporary publishing path, otherwise the page doesn’t get published.
You need to set the path inside the filename? Awesome
Where’s the grumpy fred from last weekend?
Ah! That’s absolutely brilliant. We’ve been looking for a workaround to that little navman flaw.
Reddot UK told us there wasn’t anything we could do…
[...] of weeks ago, Paul pointed me to an entry on the “Unofficial RedDot CMS Blog” – “Publishing page to subfolder” – which would seem to be both a simple *and* elegant solution. Basically, just modify the [...]
This is not working. I get an error in the publishing logs that the path is not found when I add news/index.html to the properties. Any suggestions?
You have to create this folder in the temporary publishing path (ASP\RedDotTemp\[Project-GUID]\[Language variant-GUID]\yourfolder) first. It’s a bit complicated, I know. It’s just a proof of concept.
Seeing that you have to create a temp folder for this to work. Is there at any stage that the CMS might delete the temp folders manually created?
If you hit “Delete reference directory” on your publishing target, all temp folders should be gone.
But you could create a batch script which checks for the folders (and recreates them) and run it as a scheduled task.
I know, this whole method is not the best solution, but it’s definetely better than nothing.