U4-4510 - nuget targets file creates an invalid path in the property group

Created by Daniel Gardiner 24 Mar 2014, 00:12:50 Updated by Sebastiaan Janssen 17 Mar 2017, 14:49:49

Is duplicated by: U4-4519

Is duplicated by: U4-4580

Is duplicated by: U4-7944

Is duplicated by: U4-9635

There must be an extra ; or a missing one. When I run our TeamCity build we get this error message...

The key part is this.. Could not find a part of the path '(removed)\packages\UmbracoCms.6.2.0-RC\UmbracoFiles\umbraco\Xslt\Web.config;\umbraco\Xslt\Web.config'.

This is with the surrounding content.. [10:44:11]Step 4/7: MSBuild (13s) [10:44:13][Step 4/7] Bauer.Corp.Web\Bauer.Corp.Web.csproj.teamcity: Build target: Package (11s) [10:44:25][Bauer.Corp.Web\Bauer.Corp.Web.csproj.teamcity] AutoParameterizationWebConfigConnectionStringsCore [10:44:25][AutoParameterizationWebConfigConnectionStringsCore] ParameterizeTransformXml [10:44:25][ParameterizeTransformXml] C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(2262, 5): Could not open Source file: Could not find a part of the path 'D:\TeamCity\BuildAgents\BuildAgent1\work\157abd2951c544ee\packages\UmbracoCms.6.2.0-RC\UmbracoFiles\umbraco\Xslt\Web.config;\umbraco\Xslt\Web.config'. [10:44:25][Bauer.Corp.Web\Bauer.Corp.Web.csproj.teamcity] Project Bauer.Corp.Web\Bauer.Corp.Web.csproj.teamcity failed. [10:44:25][Step 4/7] Step MSBuild failed

Comments

Sebastiaan Janssen 24 Mar 2014, 13:09:29

Aha, weird that it works when publishing from VS but not with TC. I've uploaded an updated package to NuGet could you try: Update-Package UmbracoCms -Version 6.2.0.1-RC -Pre and see if that helps? Hopefully this is then fixed and can be included in the final release.


Sebastiaan Janssen 24 Mar 2014, 13:09:47

Whoops, hang on, still uploading to NuGet, posted too soon.. ;)


Sebastiaan Janssen 24 Mar 2014, 13:24:30

Alright, that's been uploaded now, would love to hear if that helps!


Daniel Gardiner 25 Mar 2014, 00:53:14

The same issue still happens. I hadn't tried with doing it straight from VS. The file it says isnt there is there.. but its not getting copied for transforms properly.

http://blogs.msdn.com/b/webdev/archive/2010/11/10/asp-net-web-application-publish-package-tokenizing-parameters.aspx

Disabling the tokenizing of the connection strings (which we dont use anyhow) has fixed the problem.


Sebastiaan Janssen 25 Mar 2014, 10:32:08

Thanks Daniel, I'll have to have a look at how to fix that, @vincentb is also getting it in Visual Studio (U4-4519).


Andrew Swerlick 25 Mar 2014, 14:49:11

I'm getting it in visual studio as well with the 7.1.0 release candidate. Daniel's solution resolved the issue for me.


Sebastiaan Janssen 25 Mar 2014, 19:55:41

Alright guys, it would be AWESOME if you could test the attached updated versions. These are fresh builds from the very latest source, unfortunately I don't have the time to put them up on NuGet so it would be great if you could test them locally and publish to a Web Deploy Package or Azure Websites.

Download the versions you want and put them somewhere like C:\Temp and type the following command:

v6: Install-Package UmbracoCms -Version 6.2.0.2-RC -Pre -Source C:\Temp https://dl.dropboxusercontent.com/u/3006713/NuGet/UmbracoCms.6.2.0.2-RC.nupkg https://dl.dropboxusercontent.com/u/3006713/NuGet/UmbracoCms.Core.6.2.0.2-RC.nupkg

v7: Install-Package UmbracoCms -Version 7.1.0-RC2 -Pre -SourceC:\Temp https://dl.dropboxusercontent.com/u/3006713/NuGet/UmbracoCms.7.1.0-RC2.nupkg https://dl.dropboxusercontent.com/u/3006713/NuGet/UmbracoCms.Core.7.1.0-RC2.nupkg


Vincent Baaij 25 Mar 2014, 20:33:35

Seb, Daniel's solution worked for me too. Will try the rc2 package tonight/tomorrow and post my findings here


Sebastiaan Janssen 25 Mar 2014, 21:43:34

Changes also available in the latest nightly on MyGet: https://www.myget.org/F/umbraco7nightly/

@vincentb The point was to fix the actual issue instead of making a workaround that is broken for people who need to tokenize their connection string! ;) Thanks for trying in advance!


Vincent Baaij 25 Mar 2014, 23:08:19

Well, tried a completely new project, did the install-package you mentioned above with those files, and now I don't have the 'UmbracoFiles' files and folders from the package in the project. Could this be because of the following in install.ps1? (this not being an upgrade) # Copy umbraco and umbraco_files from package to project folder

This is only done when these folders already exist because we

only want to do this for upgrades

$umbracoFolder = Join-Path $projectDestinationPath "Umbraco" if(Test-Path $umbracoFolder) { $umbracoFolderSource = Join-Path $rootPath "UmbracoFiles\Umbraco" Copy-Item $umbracoFolder $backupPath -Force robocopy $umbracoFolderSource $umbracoFolder /e /xf UI.xml }


Sebastiaan Janssen 26 Mar 2014, 10:03:40

D'oh! #facepalm! Sorry, no that is just there fore upgrades, I forgot to update the version in the targets file to RC2. I've updated the package file, sorry to waste your time. You can re-download them and they should work better now. :) I'll check if the nightly actually works, it should've done the update automatically (this, of course was human error because I didn't follow my own automated build scripts.. lesson learned!).


Sebastiaan Janssen 26 Mar 2014, 10:53:25

Okay, don't bother with these packages, now getting the following error consistently, while it does work sometimes. I'll have to have another look next week, I have a few days off first! :)

Install failed. Rolling back... Install-Package : Failed to add reference to 'System.Net.Http'. Please make sure that it is in the Global Assembly Cache. At line:1 char:1

  • Install-Package UmbracoCms -Version 7.1.0-RC2 -Pre
  •   + CategoryInfo          : NotSpecified: (:) [Install-Package], InvalidOperationException
      + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
    
    


Mark Bowser 28 Mar 2014, 16:46:42

I'm experiencing a very similar issue on umbraco 7.0.3. I'm attempting to deploy using webdeploy on TeamCity. Here is the error I'm getting:

[10:02:22]Step 1/1: Build Site (MSBuild) (29s) [10:02:36][Step 1/1] src\MySite.Umbraco\MySite.Umbraco.csproj.teamcity: Build target: Build (14s) [10:02:50][src\MySite.Umbraco\MySite.Umbraco.csproj.teamcity] AutoParameterizationWebConfigConnectionStringsCore [10:02:50][AutoParameterizationWebConfigConnectionStringsCore] ParameterizeTransformXml [10:02:50][ParameterizeTransformXml] C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(2352, 5): Could not open Source file: Could not find a part of the path 'C:\BuildAgent\work\c1d89add5b38ab48\src\MySite.Umbraco\umbraco\Xslt\Web.config;\umbraco\Xslt\Web.config'. [10:02:51][Step 1/1] Step Build Site (MSBuild) failed

What really gets me is that this only happens on the staging server. On our dev server with nearly identical build configuration, this issue does not appear.

Here are some other relevant posts: [http://devnet.jetbrains.com/message/5511686] This is another post I made for this issue on the Jetbrains forum. It has more details about my situation.

[http://www.cpodesign.com/blog/could-not-open-source-file-could-not-find-a-part-of-the-path-webconfig-umbraco-xslt-webconfig/]

Is this resolved? Any clues are welcome. I tried setting the BuildAction to 'None' on the offending web.config. The /umbraco and /umbraco-client directories were originally excluded from the solution, but they have been included now. Both ways yield the same results. I cannot set to false because we need the transforms.

Thanks!


Daniel Gardiner 29 Mar 2014, 02:17:58

We dont have that file in source control, we just get it from nuget when deploying. I tried adding it to the project and changing the build action also, and no settings helped.

http://blogs.msdn.com/b/webdev/archive/2010/11/10/asp-net-web-application-publish-package-tokenizing-parameters.aspx

Disabling the connection string parametrization bypassed the problem. We use the config transforms, I'm not sure what the point of this step is. An alternative to config transforms I guess, but there is not much point with config transforms now.


Sebastiaan Janssen 01 Apr 2014, 11:37:25

@mark@proworks.com @Daniel.Gardiner FYI: 7.1.0 will fix that exact issue. I can't retro-actively fix NuGet packages that have been released already.


Sebastiaan Janssen 01 Apr 2014, 12:04:45

Alright, I've been able to install successfully three times now AND WebDeploy package works without the web.config error.

These are fresh builds from the very latest source, it would be great if you could test them locally and publish to a Web Deploy Package, Azure Websites or TeamCity.

Download the following files put them somewhere like C:\Temp and type the following command:

Install-Package UmbracoCms -Version 7.1.0-RC3 -Pre -Source C:\Temp https://dl.dropboxusercontent.com/u/3006713/NuGet/UmbracoCms.7.1.0-RC3.nupkg https://dl.dropboxusercontent.com/u/3006713/NuGet/UmbracoCms.Core.7.1.0-RC3.nupkg

These are built from the automated system so the references to the RC3 folder are now correct, unlike the version earlier where I tried to do something manually that was just wrong. :)

Note that if you do this a few times, always start with a fresh instance of Visual Studio, whenever I just close the solution that I just made and install the NuGet package in a new project, it gives me the error Failed to add reference to 'System.Net.Http'. Please make sure that it is in the Global Assembly Cache. However, when I start a new instance of VS, it's fine and installs perfectly. Super weird.


Sebastiaan Janssen 01 Apr 2014, 12:21:09

And here's a 6.2.0 version that now works as well, please let me know if you have any problems: Same instructions as earlier..

Install-Package UmbracoCms -Version 6.2.0.3-RC -Pre -Source C:\Temp https://dl.dropboxusercontent.com/u/3006713/NuGet/UmbracoCms.6.2.0.3-RC.nupkg https://dl.dropboxusercontent.com/u/3006713/NuGet/UmbracoCms.Core.6.2.0.3-RC.nupkg


Sebastiaan Janssen 03 Apr 2014, 09:51:29

Got some confirmations that it now all works from outside of the tracker so I'm going to REALLY set it to fixed now (famous last words `ey..)


Robert Mulder 25 Apr 2014, 17:47:26

Hey Sebastiaan, I realise this issue has been closed, but I wanted to let you know that I'm getting this error with a fresh 7.1.1 install from NuGet. It's a completely empty website with just Umbraco and only the Bootstrap and FontAwesome extra NuGet packages.

I've followed the steps from this URL which seem to work: http://blogs.msdn.com/b/webdev/archive/2010/11/10/asp-net-web-application-publish-package-tokenizing-parameters.aspx

But it does seem that the issue is not completely resolved. It happens when I try to publish the site to a webserver via web deploy.


Mark Bowser 25 Apr 2014, 22:32:19

What version of WebDeploy are you using? I've seen this problem when I was using an old version of WebDeploy. I believe I saw it on WebDeploy 2.0. Upgrading to WebDeploy 3.5 solved it for me.


Matt Perry 28 Apr 2014, 16:09:39

I'm still getting the very same error... Fresh install with no dependencies.


Mark Bowser 06 May 2014, 19:26:22

I just got the same error on one of our new Umbraco 7.1.0 sites as well.

C:\Program Files\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(2262, 5): Could not open Source file: Could not find a part of the path 'C:\BuildAgent\work\aeac905a68d79922\src\Test.Umbraco\umbraco\Install\Views\Web.config;\umbraco\Install\Views\Web.config'.

The Umbraco directory is not in the solution. I can work around the problem by specifying /p:AutoParameterizationWebConfigConnectionStrings=False as a parameter to my MsBuild that is doing the webdeploy.


Tim Peel 07 May 2014, 08:31:44

This fix caused issues for me post install when building. I had to remove the assembly binding on System.Net.Http for it to work. This was an example of one of the many warnings caused:

Warning 34 The primary reference "umbraco.XmlSerializers, Version=1.0.5234.23402, Culture=neutral, processorArchitecture=MSIL" could not be resolved because it has an indirect dependency on the framework assembly "System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v4.0". To resolve this problem, either remove the reference "umbraco.XmlSerializers, Version=1.0.5234.23402, Culture=neutral, processorArchitecture=MSIL" or retarget your application to a framework version which contains "System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a". C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets 1635 5


Dennis Spijkerboer 06 Jun 2014, 08:27:02

I still run into this problem on 7.1.4. How can i fix this?

Could not open Source file: Could not find a part of the path 'C:....\umbraco\Install\Views\Web.config;\umbraco\Install\Views\Web.config'.


Hannes Bohm 09 Jun 2014, 06:16:42

The same is true for me as well, it doesn´t seem fixed. Fresh Visual Studio Empty Web -> Installed Umbraco 7.1.4 via NuGet -> Started site and did basic configuration with CE SQL Database -> Included the umbraco and umbraco_client folder in the project to have them under source control as well as have them avilable when publishing -> When trying to publish to Azure it gives this error:

Could not open Source file: Could not find a part of the path 'D:\Dev\Repos\Web\umbraco\Install\Views\Web.config;\umbraco\Install\Views\Web.config'.

Publishing to a local folder however works without problems, it´s just the Azure profile that get´s this error. Also, I can publish to Azure when I exclude the umbraco folder from the project but then its not under source control and wont get published either.


Sebastiaan Janssen 09 Jun 2014, 07:41:47

@686d7066 It will get published, we have a specific publish target for that. As for source control, don't you control what is in source control? I don't understand how things that are not included in the solution wouldn't be under source control.

You don't need any of the umbraco folder under source control, we check on each build if it's there, if not we copy it from the nuget package folder back into the root anyway.


Hannes Bohm 09 Jun 2014, 08:12:00

I guess Im doing something wrong then. When I dont include umbraco and umbraco_client and publish it to the local file system these folders are missing from the result. But when I include them Azure publishing isnt working anymore. As with source control I am getting used to GIT and just found out I can include items that are not part of the solution itself. So that one is solved.


Vincent Baaij 16 Jun 2014, 12:14:53

Hi Seb,

With a 7.1.4 install I'm getting the .config file error again. The error has returned after installing the the Optimus Package which has a \Views folder in App_Plugins.

Error: ...\Microsoft.Web.Publishing.targets (2291): Could not open Source file: Could not find a part of the path 'C:\a...\App_Plugins\Optimus\Views\Web.config;\App_Plugins\Optimus\Views\Web.config' (... are deleted parts of the path)

Tried solving it by adding a .wpp.targets file but then it doesn't deploy the right project to my (Azure) staging server.


Sebastiaan Janssen 16 Jun 2014, 12:46:00

@vincentb Works fine over here, the App_Plugins folder and all descendant files are already included in the targets file. Just make sure not to include the Optimus folder in the VS project.


Vincent Baaij 16 Jun 2014, 13:44:46

I've excluded the Optimus folder, but it still tries to transform :( Weird huh? Why would it still include that?

Can you please look at the following (part of the) log: PreTransformWebConfig: Found The following for Config tranformation: Web.config Creating directory "C:\a\src...\obj\Debug\TransformWebConfig\transformed". Creating directory "C:\a\src...\obj\Debug\TransformWebConfig\transformed\Views". Creating directory "C:\a\src...\obj\Debug\TransformWebConfig\transformed\macroScripts". Creating directory "C:\a\src...\obj\Debug\TransformWebConfig\transformed\xslt". Creating directory "C:\a\src...\obj\Debug\TransformWebConfig\transformed\App_Plugins\Optimus\Views". Copying Web.config to obj\Debug\TransformWebConfig\original\Web.config. Copying C:\a\src...\Web.Debug.config to obj\Debug\TransformWebConfig\assist\Web.config. TransformWebConfigCore: Transforming Source File: C:\a\src...\Web.config Applying Transform File: C:\a\src...\Web.Debug.config Output File: obj\Debug\TransformWebConfig\transformed\Web.config Transformation succeeded PostTransformWebConfig: Transformed Web.config using C:\a\src...\Web.Debug.config into obj\Debug\TransformWebConfig\transformed\Web.config. PipelineTransformPhase: Publish Pipeline Transform Phase PreAutoParameterizationWebConfigConnectionStrings: Creating directory "C:\a\src...\obj\Debug\CSAutoParameterize\transformed\Views". Creating directory "C:\a\src...\obj\Debug\CSAutoParameterize\transformed\macroScripts". Creating directory "C:\a\src...\obj\Debug\CSAutoParameterize\transformed\xslt". Creating directory "C:\a\src...\obj\Debug\CSAutoParameterize\transformed\App_Plugins\Optimus\Views". Copying Views\Web.config to obj\Debug\CSAutoParameterize\original\Views\Web.config. Copying macroScripts\Web.config to obj\Debug\CSAutoParameterize\original\macroScripts\Web.config. Copying xslt\Web.config to obj\Debug\CSAutoParameterize\original\xslt\Web.config. Copying App_Plugins\Optimus\Views\Web.config to obj\Debug\CSAutoParameterize\original\App_Plugins\Optimus\Views\Web.config. Skip copying .\App_Plugins\Optimus\Views\Web.config to obj\Debug\CSAutoParameterize\original\App_Plugins\Optimus\Views\Web.config, File obj\Debug\CSAutoParameterize\original\App_Plugins\Optimus\Views\Web.config is up to date Copying obj\Debug\TransformWebConfig\transformed\Web.config to obj\Debug\CSAutoParameterize\original\Web.config. AutoParameterizationWebConfigConnectionStringsCore: Transforming Source File: C:\a\src...\Views\Web.config Applying Transform File: No element in the source document matches '/configuration/connectionStrings' Not executing SetTokenizedAttributes (transform line 6, 15) Output File: obj\Debug\CSAutoParameterize\transformed\Views\Web.config Transformation succeeded Transforming Source File: C:\a\src...\macroScripts\Web.config Applying Transform File: No element in the source document matches '/configuration/connectionStrings' Not executing SetTokenizedAttributes (transform line 6, 15) Output File: obj\Debug\CSAutoParameterize\transformed\macroScripts\Web.config Transformation succeeded Transforming Source File: C:\a\src...\xslt\Web.config Applying Transform File: No element in the source document matches '/configuration/connectionStrings' Not executing SetTokenizedAttributes (transform line 6, 15) Output File: obj\Debug\CSAutoParameterize\transformed\xslt\Web.config Transformation succeeded Transforming Source File: C:\a\src...\App_Plugins\Optimus\Views\Web.config;.\App_Plugins\Optimus\Views\Web.config C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(2291,5): error : Could not open Source file: Could not find a part of the path 'C:\a\src...\App_Plugins\Optimus\Views\Web.config;\App_Plugins\Optimus\Views\Web.config'. [C:\a\src.......csproj] Transformation failed


Craig Stevens 28 Feb 2015, 23:31:28

I'm seeing this in 7.2.2 as well

Could not open Source file: Could not find a part of the path 'C:\VS2012\myProject\myProject\umbraco\Install\Views\Web.config;\umbraco\Install\Views\Web.config'


Kevin Giszewski 02 Mar 2015, 18:24:54

Ran into this today as well with v7.2.2 - VS2013 Ultimate.

Fixed (temporarily) by changing that files' build action to None.


Richard Kingston 04 Mar 2015, 08:44:14

Also just ran into this with v7.2.2 - Same message as Craig just posted. I tried Kevin's solution but after changing the build action to None on \umbraco\Install\Views\Web.config and \umbraco\Xslt\Web.config, it then seemingly needed me to do the same for various files in App_Data\TEMP\ExamineIndexes\External\Index.


Sebastiaan Janssen 05 Mar 2015, 10:38:21

Hey could one of you please open a NEW issue for this with exact steps to reproduce? A video would be even better. I don't get this error so I must be doing something slightly different from you. Please start with a new solution in VS for the steps to reproduce as all of your configurations may be different and the problem COULD be self-inflicted.. :)

@Richard.Kingston Please tell me you're not trying to deploy your App_Data\TEMP\ folder? It should never be deployed.


Richard Kingston 05 Mar 2015, 12:31:34

I must have been having one of those days! That never even occurred to me. If anyone asks, this conversation never happened ;-)


Eric Schrepel 10 Mar 2015, 20:04:27

I had this happen just now but was because of not starting VS2013 as an administrator. (Note to Chrome users: starting VS2013 as administrator then trying to build a site can cause Chrome to hang; copy the localhost://nnnnn url into a Firefox window and the Umbraco-install splash screens will continue.)


Stefan Kip 23 Nov 2015, 08:20:27

We just ran into this issue with Umbraco 7.3.0 and 7.3.1 via NuGet. Adding this to the publish profile fixed the issue:

false

and

False

The last addition (UpdateDestWebConfig=false) is needed because you'll get an error:

{{The 'umbracoDbDSN-Web.config Connection String' argument cannot be null or empty.}}


Lars-Erik Aabech 26 Jan 2016, 12:43:12

Same here. Adding AutoParameterizationWebConfigConnectionStrings=false did the trick. Using 7.4 beta. ;)

It hicks up due to App_Plugins\OurArea\Views\Web.config. I guess it's trying to replace connectionstrings there, but there ain't any.


Bjarne Fyrstenborg 29 Feb 2016, 21:06:47

I also had a similar issue in Umbraco version 7.2.6 when publishing via web deploy, where it returned an error about it couldn't find a part of the path to web.config i /App_Plugins/Optimus/Views/Web.Config The file does exist (I guess Optimus use it to to modify the main web.config in some way) .. anyway, the suggestions from @kipusoep fixed it :)


Bart De Meyer 30 Aug 2016, 09:20:00

@sebastiaan We're still having the same issue in Umbraco version 7.4.3. In VS 2015, created new project, added the Umbraco Nuget package. We've did some configuration (no extra custom development but already added the extra projects in the solution). The folders (Umbraco and Umbraco_client) are not under source control and won't be checked out on the Teamcity server. On Teamcity we first do a nuget restore, then a solution build (for the future custom development projects like Data access Layer) and then a MS Build of the website project. As soon we are trying to package the website, the same error occurs: [ParameterizeTransformXml] C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(2295, 5): Could not open Source file: Could not find a part of the path 'C:\BuildAgent5\work\95578bf4833c16a5\Brabo\umbraco\Install\Views\Web.config;\umbraco\Install\Views\Web.config). If I run the MSBUILD command locally on my development PC, I got the same errors.

Is there any way we can resolve this issue without disabling the config transforms (that we need in our deploy sequence)?


Lars-Erik Aabech 30 Aug 2016, 10:05:32

Guys, this really isn't up to Umbraco to fix. It's a flaw in the web publishing engine. Just add the AutoParameterizationWebConfigConnectionStrings element to your pubSettings file.


Bart De Meyer 30 Aug 2016, 10:11:53

@lars-erik changing AutoParameterizationWebConfigConnectionStrings to false isn't a solution in automated deploy scenario's. We didn't had these problems on earlier versions of Umbraco. There is something changed in the way these files are handled in the Umbraco NuGet package that causes this errors.

I'm sure it isn't simple enough to just change it again to how it was done before, but you can't expect anybody outside Umbraco to resolve this issue as they are the creators of the Nuget package...


Lars-Erik Aabech 30 Aug 2016, 11:32:31

@BartDeMeyer If you use regular config transforms (web.config.release etc) you can automate and still have web publish ignore connection strings. This problem occurs if there are web.config files in uncommon folders like App_Plugins and they don't have connectionstrings in them. It can be reproduced without Umbraco. Hence - it's a problem with the web publish stuff itself. They should never have introduced the "change connection string on publish" feature in web publish - it's perfectly handled by config transforms.


Priority: Normal

Type: Bug

State: Fixed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 6.2.0

Due in version: 7.1.0, 6.2.0

Sprint:

Story Points:

Cycle: