Talk:Potlatch 2/Blockers

Public Transport Routes

In public transport routes the order of the route elements matters. Thus, the sort arrows in the members section should be altogether disabled for these relations - htting any of this buttons would mess up the relation.

No, this does not affect the order of the relation. The arrows (like pretty much every table view in every app in the world :) ) only affect the view order - i.e. the order in which they're shown on-screen. They do not change the actual ordering of the relation members. --Richard 09:12, 13 July 2010 (UTC)

Behaviour if user has stopped any new windows/tabs opening

When I try to save any changes, a box pops up with a link to authorise via OAuth. This link opens in the same tab/window for me -- I presume it's supposed to open in a new window. And after following the link and authorising, it doesn't seem to have taken. (Presumably the new instance of P2 generates a new token.) The same window/tab thing may be due to my restrictive browser settings that prevent any new windows/tabs opening. This may be an edge case, but but it does seem to be preventing me from using P2. -- Rjw62 15:05, 13 October 2010 (BST)

Added after more investigation: I'm using Firefox 3.6.10 on Linux, with the about:config pref browser.link.open_newwindow set to 1. Changing that pref back to the default value of 3 allows the authorisation process to work fine. I can then change the pref back to 1, and things continue to work (ie the authorisation is remembered). So it's just the authorisation step that needs a work-around for people who divert new window calls to the current window. -- Rjw62 16:48, 13 October 2010 (BST)

I'm not really sure what we can do about this - we need to open a link, and it needs to not be in the current window, that's why it requests a new window - but you're blocking that. I don't think it's something that we can detect via javascript to warn you about? Also, if the onbeforeunload javascript event doesn't fire either, then I'm stumped Gravitystorm 16:42, 21 October 2010 (BST)

This is an extreme edge case. Users who are able to configure their browser in this way are also able to diagnose and fix the problem themselves. --Richard 23:39, 26 November 2010 (UTC)