WowAce

Game version:
World of Warcraft: Mists of Pandaria Classic

PitBull version:
PitBull Unit Frames 4.0 v4.2.50

Source profile:
Exported as a full Profile from WoW Classic Anniversary using PitBull v4.2.50.

Problem:
I am unable to import a PitBull profile into MoP Classic.

The export string is accepted, and PitBull proceeds to the “Enter a new profile name” dialog. I can enter a profile name, but clicking Okay does not complete the import. With Lua errors enabled, clicking Okay produces the following error:

Message:
Interface/AddOns/PitBull4/Options/Share.lua:120: attempt to index field 'editBox' (a nil value)

Stack:
[C]: ?
[Interface/AddOns/PitBull4/Options/Share.lua]:120: in function 'OnAccept'
[Interface/AddOns/Blizzard_StaticPopup/StaticPopup.lua]:680: in function 'StaticPopup_OnClick'
[Interface/AddOns/Blizzard_StaticPopup_Game/GameDialog.lua]:46: in function <...face/AddOns/Blizzard_StaticPopup_Game/GameDialog.lua:44>

Steps to reproduce:
1. In WoW Classic Anniversary, export a complete PitBull profile using PitBull v4.2.50.
2. Open MoP Classic with PitBull v4.2.50 installed.
3. Open PitBull options.
4. Go to Share → Import.
5. Paste the exported profile string.
6. Start the import.
7. At “Enter a new profile name,” enter any nonblank profile name.
8. Click Okay.

Actual result:
The profile is not imported. Clicking Okay generates the Lua error above.

Expected result:
PitBull should read the entered profile name and complete the profile import.

Additional information:
The same failure occurs after trying several different profile names, including the original exported profile name.

The export string appears to be decoded successfully because PitBull reaches the profile-name confirmation dialog rather than reporting corrupt or incompatible import data.

The current source for the profile-import dialog uses:

local profile_name = self.editBox:GetText()

The MoP Classic StaticPopup dialog appears not to expose the edit box through self.editBox, causing self.editBox to be nil when OnAccept runs.

Screenshot of the full Lua error is available.