Sign in Register
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • kleptbit 42 posts 98 karma points
    Aug 13, 2020 @ 11:51
    kleptbit
    0

    Local to Development workspace transfer fails. 'create manifest on source' is changing the case of macro parameters

    I cannot send changes from Local to the Development workspace.

    It seems the Deployment Engine is changing the case of parameters macros when it gets to ‘create manifest on source’.

    System.Collections.Generic.KeyNotFoundException: Parameter not found: documentroot, on macro: SeftonDocumentList.

    The Parameter name is documentRoot.

    This happens for all parameters.

    Anyone got any clues, please?

    0f33b51d - Executing, 10% - Get remote session 0f33b51d - Executing, 20% - Create manifest on source ❤ ❤ ❤ ❤ 0f33b51d - Executing, 80% - Exception! 0f33b51d - Executing, 80% - Abort remote session 0f33b51d - Failed, 80% - Total time 00:00:16.639.

    -- EXCEPTION --------------------------------------------------- (proper exception traces at the end of this log)

    System.Collections.Generic.KeyNotFoundException: Parameter not found: documentroot, on macro: SeftonDocumentList.

    EXCEPTION:

System.Collections.Generic.KeyNotFoundException: Parameter not found: documentroot, on macro: SeftonDocumentList.
   at Umbraco.Deploy.Core.MacroParser.<>c__DisplayClass8_1.<ProcessValue>b__1(Match attributeMatch)
   at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat)
   at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator)
   at Umbraco.Deploy.Core.MacroParser.<>c__DisplayClass8_0.<ProcessValue>b__0(Match macroMatch)
   at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat)
   at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator)
   at Umbraco.Deploy.Core.MacroParser.ProcessValue(String value, ICollection`1 dependencies, Direction direction)
    Copy Link
  • kleptbit 42 posts 98 karma points
    Aug 13, 2020 @ 15:55
    kleptbit
    1

    The wonderful Umbraco Support sorted me for this one:

    'The issue here is that the aliases of the macro parameters have been changed. So the parameter used to have the alias locationheader but it was changed it to loctionHeader. Which means that a node which had the macro added when it had the old parameters alias does not recognize the new parameters. Therefore they will be empty. So by going to this node and adding in the values again it will work'

    Turns out that a big load of content embedded as XML was imported as text by CMSImport - and has macro parameters in it lower cased (we're not sure why, they've never been changed by hand). So when it gets deployed from the backoffice to live - it doesn't get parsed as text and it all falls over. Sigh.

    Thanks to Support for the help with this one.

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft