U4-362 - After RenderTemplate() Node.GetCurrent() is replaced with the node id from RenderTemplate

Created by Sebastiaan Janssen 19 Aug 2012, 14:51:29 Updated by Shannon Deminick 21 Jun 2017, 07:52:13

Umbraco 4.6.1 Umbraco.Library and Umbraco.presentation.nodeFactory

The issue is exactly the same as described in http://umbraco.codeplex.com/workitem/21983 So if I have a rendertemplate called the next time I request Node.GetCurrent() I do get the wrong Node.

The workarround will be to cache the GetCurrent() before hitting RenderTemplate().

''Originally created on CodePlex by [StephenMaij|http://www.codeplex.com/site/users/view/StephenMaij]'' on 2/7/2011 12:56:20 PM [Codeplex ID: 30001 - Codeplex Votes: 3]

Imported comments

''Comment by [sebastiaan|http://www.codeplex.com/site/users/view/sebastiaan] on 8/9/2012 11:50:28 AM:'' We haven't been very good at maintaining the issue tracker and with 1250+ open bugs we can't be sure which ones have been fixed and when (if they are even fixed).

To keep the issue list maintainable, on Monday the 13th of August, we will be moving the issue tracker over to YouTrack (http://issues.umbraco.org) where we'll only import the issues that have been updated in the past 12 months (which means: they had comments or votes in the past year).

If you think this issue (that has had no activity in the past year) is still worth looking at then please comment and we'll look into re-opening it.

** Closed by sebastiaan 08/09/2012 2:50AM

''Comment by [StephenMaij|http://www.codeplex.com/site/users/view/StephenMaij] on 8/9/2012 2:54:07 PM:'' I think it's worth looking into this bug.

''Comment by [sebastiaan|http://www.codeplex.com/site/users/view/sebastiaan] on 8/9/2012 5:04:27 PM:''


Comments

Edward Marden 21 Aug 2012, 08:26:04

This does still seem to be an issue - I've just ran across this in a new 4.8 site.


Rune Grønkjær 21 Aug 2012, 09:03:08

Yes, this is certainly still an issue. I have just replicated it on umbraco v 4.8.0. If you use RenderTemplate just once the whole sites currentPage will be changed to the node just used in RenderTemplate. This is both in xslt's and in the master pages.

Only way for this to not happen is to send a template id to RenderTemplate as the second parameter. But that's not really a solution.

Really hope some of you guys can fix this. RenderTemplate looks great, but it doesn't work right now.

Thanks /Rune


Shannon Deminick 21 Jun 2017, 07:52:14

Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/


Priority: Normal

Type: Bug

State: Closed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:

Sprint:

Story Points:

Cycle: