Macro Partials don't work on virtual pages about articulate HOT 6 CLOSED

1.0.4 is a minor release and only contains bug fixes, should be a very straight forward upgrade but of course you should test before you launch. Worth a try to see if it fixes it, can't say for sure. I won't have time to look into this for a few weeks.

from articulate.

Thanks for the quick response. I tried upgrading, but that didn't resolve the issue. I'll just work around this issue with the old way of building macros for now.

from articulate.

The underlying problem is that for any virtual pages, the ID assigned to it is 'virtual', meaning that there is no corresponding real node in umbraco.

The error comes from this line in UmbracoHelper:

m.renderMacro(attributes, umbracoPage.Elements, this.UmbracoContext.PageId.Value);

As you can see it's using this.UmbracoContext.PageId.Value as the current page id. On a virtual page this will be based on a simple algorithm and int.Max value. So when the old macro object tries to look this up it gives an error since that id doesn't exist.

I think in order for this to work (even though i still think there might be issues), we'll have to modify the Umbraco core. Unfortunately the way macros render is based on code made a century ago so it's difficult to work with.

I'll log an issue on the umbraco tracker for this.

from articulate.

http://issues.umbraco.org/issue/U4-5943

from articulate.

Instead of using macros though, you can just use partial views directly... will be faster too. The only real reason to use macros nowadays is if you need support for your editors to insert macro parameters, which generally only pertains to the rich text editor or grid.

from articulate.

This is fixed in umbraco now in rev: umbraco/Umbraco-CMS@73e9ff0

from articulate.