Sign in Register
Go to solution
Copied to clipboard

Flag this post as spam?

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


  • Nico Lubbers 151 posts 175 karma points
    Feb 15, 2010 @ 01:01
    Nico Lubbers
    0

    Macro error after deploy in production env

    I have an issue on my production server after deploying some new documenttypes, masterpages, macro's and content.
    - I added some document types to my production server (using export and import of .udt files)
    - Added the same templates to the template-tree, then uploaded the masterpages
    - Added XSLT and macro's and uploaded the XSLT files

    - oh... and I upgraded from 4.0.2.1 to 4.0.3

    Now the output on my production server is showing me simply the following output on the place where the result of the macro (xslt) should be rendered.

    <Macro: (,)>

    ?umbdebugshowtrace=true does not shine a light on this... and the visualise XSLT function in umbraco is working fine...

    ... does it ring a bell to someone how to solve?

    Nico

    Copy Link
  • skiltz 501 posts 701 karma points
    Feb 15, 2010 @ 01:07
    skiltz
    1

    Doesn't this happen when a macro with the name specified doesn't exist. Did you rename the macro alias? I'm sure you've probably checked this. 

    Copy Link
  • Neil Campbell 58 posts 182 karma points
    Feb 15, 2010 @ 02:04
    Neil Campbell
    1

    I have seen that issue before. Like Skiltz said it usually happens when the macro does not exist, but I have also seen it happen without any reason.

    Try re-pointing the macro to the correct xslt, or .net usercontrol, then saving, and see if that fixes it.

    Otherwise re-create the macro, and re add it to the template.

    Cheers,
    Neil

    Copy Link
  • Nico Lubbers 151 posts 175 karma points
    Feb 15, 2010 @ 08:56
    Nico Lubbers
    0

    @skiltz: I double-double checked that :-)

    @Neil: That did the trick !!
    On the macros I used the dropdown to select the XSLT again (although it was already there) and saved the macro then on the XSLT I saved the XSLT again... and the problem is fixed !!

    Thanks... this little nifty problem costed me some hours :-)

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft