Hello, with the latest version of WQT, by default when I open the map (by pressing M on my keyboard), it opens Kul'Tiras' map instead of the one of the zone I'm on.

I'm having the issue in Draenor, that's for sure, and maybe in other zones as well, I can't remember if I tested other area or not.

Opening the map while in Stormwind or in Bounty Bay leads to the same issue.
Dalaran (Legion) too.
Dalaran (WotLK) also.
Boralus too, instead of opening Boralus map, I still get Kul'Tiras.

Besides, it opens Kul'Tiras, and not one of the 3 sub zones.

Most likely you have all disabled reporting of errors. WQT keeps crashing on load in my game, and after that it behaves as you say, wrong map keeps opening. Unfortunately WQT is just too buggy at this time, I would suggest disabling it until it is fixed properly for 9.0.1.

Found a remediation and possible fix - comment out line 914 of WorldQuestTracker.lua:
--WorldMapFrame:SetMapID (WorldQuestTracker.MapData.ZoneIDs.KULTIRAS)

This seems to be related to a non-functioning tutorial, which had previously been set to a different popup ID, but when resetting my variables, was reset back to 1. After changing this line, I'm no longer forced to the Kul Tiras map.

Most likely you have all disabled reporting of errors. WQT keeps crashing on load in my game, and after that it behaves as you say, wrong map keeps opening. Unfortunately WQT is just too buggy at this time, I would suggest disabling it until it is fixed properly for 9.0.1.

Kind of dismissive, don't you think? This is an error, we're reporting it. There's no LUA error reported by BugSack, but the functionality is obviously broken. This should be fixed, not ignored or disabled.

Most likely you have all disabled reporting of errors. WQT keeps crashing on load in my game, and after that it behaves as you say, wrong map keeps opening. Unfortunately WQT is just too buggy at this time, I would suggest disabling it until it is fixed properly for 9.0.1.

Kind of dismissive, don't you think? This is an error, we're reporting it. There's no LUA error reported by BugSack, but the functionality is obviously broken. This should be fixed, not ignored or disabled.

For me, before the Saturday update, WQT crashed with an error on logging in/reloading the UI and completely broke the map and quest log. I had no choice but to disable the addon.