Copied to clipboard

Flag this post as spam?

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


  • Dan 1250 posts 3747 karma points admin c-trib
    May 28, 2012 @ 19:50
    Dan
    0

    Macro error when building uComment from source

     

    Hi,

    I'm building uComment from the latest source on Codeplex, but this may be a more generic error anyway.  I've set up NAnt so that a package is created after compiling the build (the source uses NAnt to do this, so I'm just using it as it is) pulling in all the relevant resources.

    However, there are a few issues with the package which is produced.

    1. There are supposed to be two macros created for this package: 'UCommentForm' (a usercontrol macro) and 'UCommentListComments' (an xslt macro).  The XSLT macro is added correctly, however the 'UCommentForm' usercontrol macro isn't created when installing the package.  The usercontrol is there in the correct directory (usercontrols/UComment/UCommentForm.ascx) but the macro isn't created during installation of the package.

    2. Following on from the above, if I create the 'UCommentForm' macro manually and create the macro parameter (alias: RegisterScripts) manually too, the form renders correctly on the site but doesn't submit correctly (just seems to refresh the page).  Using ?umbdebugshowtrace=true gives the following error:

    macro  control property 'RegisterScripts' doesn't exist or aren't accessible (public)  0.00313809568451835 0.000066

    (Full, horribly formatted pastebin output here: http://pastebin.com/FMzwnpSz)

     

    Does anyone know what could be causing the error with the macro here?  I've tried taking the NAnt package build process out of the equation and copying the compiled files over to the site, but it gives the same error.

    Any pointers greatly appreciated!

     

  • Dan 1250 posts 3747 karma points admin c-trib
    May 28, 2012 @ 22:13
    Dan
    0

    I actually just tried building one of the branches of this project (branch 1.2), which has worked perfectly.  Phew!  I think the reason the original source failed was because it's built for Umbraco 4.0.x rather than 4.7.x (which is the version running my site) so although I don't know why exactly it failed, it now makes sense that it did!

  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies