Publish to an auto-created folder

[johnhaller]

I am using publishing profiles to publish RH to SharePoint (native sharepoint output) and this works very well, except for the fact that I must first create a folder to publish to, and then set that as the location in a specific publishing profile for the project.  

Why doesn't RoboHelp create the project folder when publishing, like it does for version control.  Or perhaps I am missing a setting somewhere.

[johnhaller]

I don't think I stated my question very clearly.  Let me try again.

Connection profiles are used both to specify where to store files for version control and for where to publish content.  The connection profile specifies a path to a root directory, in my case, a document library in SharePoint.

When I add a project to that connection profile for version control, a folder is automatically created in the document library using the project name, and the project files are synced to that folder. Very neat and simple.

When I use that connection profile in the creation of a publishing profile, I must specify the full path (document library/Folder) where I want the content published, rather than just selecting the connection profile, and allowing the publishing process to automatically publish to a folder created with the name of the project.

This is not a horrible way for this to work, but the result is that I will have at least one publishing profile for every project I publish to SharePoint.  For me this means I will wind up having one connection profile, but hundreds of publishing profiles.  Furthermore, the list of publishing profiles seems to be shared by all project I create. So every project will eventually have this listing of hundreds of publishing profiles.  This seems messy and unnecessary.

Perhaps I am missing some setting in the publishing profile that could handle this better.

[Amebr]

I couldn't say for sure why Adobe chose to implement this they way they did, but in the normal web server world I may publish one project to multiple locations. For example I may publish to a Test environment, then once I'm happy with that I'll publish to a PROD environment. Or maybe I need to publish slightly different versions of one project - for example an admin guide and a user guide.

So for me, specifiying the specific folder to publish to for a specific publishing profile makes sense.

Having said that, I haven't worked with publishing to Sharepoint, so couldn't say if this was a common or sensible need in that environment.

[johnhaller]

I agree with your points that there are times a project needs to be published to different locations for various reasons.  We also publish to dev first, then production.  And use of conditional markers are another time I would publish one project to different locations even in production.

So I would not want to do away with the ability to specify a full folder path in the publishing profile.  What I am thinking is having the ability to use a system variable(field?) in the Remote Path field for the publishing profile.  

The example below would be a single publishing profile that could be used by all projects that you wanted to publish to the location specified in the Connection Profile. Each project would be published in a folder named for the project.

[Peter Grainge · Accepted solution]

Please follow this link to report bugs or request new features. https://tracker.adobe.com. Post the link to your bug report / feature request in this thread and others can vote for it. The more people who do so, the higher it gets prioritised.

Meantime duplicate a preset and just amend as required?

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

[johnhaller]

agreed, this is not a bug, but I will put in a feature request.  and the way to handle it now is to just have multple publishing profiles.  For me this just gets messy and feels unecessary since I am just publishing to a folder named for the project anyway.