Item9888: ActionTrackerPlugin edit links broken outside System web if AliasPlugin enabled

With ActionTrackerPlugin 9577 (2010-10-17), edit links in %ACTION% and %ACTIONSEARCH% are broken if used outside the System web. Instead of the edit form, the new window displays some kind of raw view of the page you came from.

-- KerstinPuschke - 25 Oct 2010

Problem occurs only if AliasPlugin 7677 (2010-06-07) is installed. Might be related to Item2455.

-- KerstinPuschke - 25 Oct 2010

Is there a solution jet??

-- EnrikGuenter - 11 Nov 2010

I have version 3.03 of Alias Plugin installed. Still doesn't work, even thou it's supposed to be fixed Item2455 . I deaktived the AliasPlugin for now but would not recommend closing this topic except someone confirms it is fixed and it is only a problem on my system.

-- EnrikGuenter - 11 Nov 2010

Still doesn't work for us, too - we have AliasPlugin 3.03 and Foswiki 1.1.2

-- KerstinPuschke - 11 Nov 2010

I don't use AliasPlugin myself, but having read the headline for it and some of the code, I'm pretty confident that the problem lies with that plugin, and not with the ATP which does nothing very clever.

-- CrawfordCurrie - 28 Jan 2011

'No action required' might be correct for the ActionTrackerPlugin, but the problem remains. Reopened, AliasPlugin added to 'affected component'.

-- KerstinPuschke - 31 Jan 2011

Took ATP out of the "affected components" list, as I'm pretty much certain it's not ATP's fault, and other plugins will be affected (though TBH I haven't tested with AliasPlugin due to lack of time)

-- CrawfordCurrie - 19 Apr 2011

I note that in Support.Question774, ValentinKozlov suggests a fix to AliasPlugin. Perhaps that is a clue?

-- FilSalustri - 21 Jun 2011

Workaround

1. Set the {PluginsOrder} in the configuration so that the AliasPlugin is listed before the ActionTrackerPlugin.

-- GjFulk - 09 Dec 2013

That's probably the only possible solution: both plugins parse the topic text by themselves, that is the normal TML parser isn't involved which would normally resolve things in a more natural way.

So the only other way to fix such an issue is to do exactly this: tinker with {PluginsOrder}.

May I consider this issue as resolve?

-- MichaelDaum - 27 Apr 2014

Commenting is disabled while not logged in