WoW-Pro v2.1.6/0588ea0812f7d90e1e9f, USEnglish client/server, WoW 4.0.6 live. Whether using a saved variables from a prior revision or no prior saved variables, the current version consistently throws up an error at logon and fails to provide its stand-alone frame properly. Consequently, the mod cannot be used:

["message"] = "WoWPro-2.1.6\WoWPro_Broker.lua:28: attempt to index global 'text' (a nil value)\nWoWPro-2.1.6\WoWPro.lua:183: in function <Interface\AddOns\WoWPro\WoWPro.lua:99>\n(tail call): ?:\n: ?\n:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>\n(tail call): ?:\nAceAddon-3.0-10 (Ace3):543: in function EnableAddon'\nAceAddon-3.0-10 (Ace3):635: in function <Interface\\AddOns\\Ace3\\AceAddon-3.0\\AceAddon-3.0.lua:621>\n<in C code>: in functionLoadAddOn'\nInterface\FrameXML\UIParent.lua:244: in function UIParentLoadAddOn':\nInterface\\FrameXML\\UIParent.lua:267: in functionCombatLog_LoadUI':\nInterface\FrameXML\UIParent.lua:521: in function <Interface\FrameXML\UIParent.lua:494>
["type"] = "error",
["session"] = 1983,
["counter"] = 1,
}, -- [1000]

Using it in combination with the StatBlockCore LDB display v2.67 (http://www.wowace.com/addons/stat-block-core/). It has no problems with any other LDB mod and had no problems with prior builds of WoW-Pro.

Next test, reverted the WoWPro_Broker.lua file back to build 773df8b (last one before it was updated in b3da56a), while retaining all the other files from v2.1.6. That solves the problem; no further errors.

So the "fixes" added to WoWPro_Broker.lua in b3da56a instead break it. In testing here at least.

0a4a932

Oh, POO! I fixed this bug in my test area, but forgot to migrate it to the main repo.
Line 28 in WoWPro_Broker.lua should read:

local name,levels = GID:match("([A-Za-z]+)([0-9]+)")
The 'text' should be changed to 'GID'.

This bug only shows if you were playing in a renamed guide BTW.
Oh, and most excellent tracking down to the checkin #.