WowAce

If postal is on, community invite is not working. i need to turn postal off to do.

here is error code

error 1

7x FrameXML\AutoComplete.lua:404: Usage: strlenutf8(string)
[string "=[C]"]: in function `strlenutf8'
[string "@FrameXML\AutoComplete.lua"]:404: in function <FrameXML\AutoComplete.lua:403>

Locals:

error 2

1x [ADDON_ACTION_FORBIDDEN] addon 'Postal' calling protected function 'SendCharacterInvitation()'.
[string "@!BugGrabber\BugGrabber.lua"]:519: in function <!BugGrabber\BugGrabber.lua:519>
[string "=[C]"]: in function `SendCharacterInvitation'
[string "@FrameXML\StaticPopup.lua"]:4156: in function <FrameXML\StaticPopup.lua:4142>
[string "@FrameXML\StaticPopup.lua"]:4174: in function `OnAccept'
[string "@FrameXML\StaticPopup.lua"]:5077: in function `StaticPopup_OnClick'
[string "*:OnClick"]:1: in function <[string "*:OnClick"]:1>

This was definitely an interesting issue to track down.  The postal feature disable Blizzard's name auto-completion popup used a pre-hook on the Blizzard function AutoComplete_Update which works fine in the SendMailNameEditBox as postal was originally designed.  However, when Blizzard added the communities feature it decided to re-use the function AutoComplete_Update in secure code.  Secure code does not allow pre-hooks.  Post-hooks are allowed in secure code but would not be able to perform the feature postal had since a post-hook would run after the Blizzard autocomplete drop down had already been displayed.  There is really no way to fix this feature of postal give the Blizzard code change.  The two options are to 1) leave the postal feature as is which breaks community invites and possible future cases where Blizzard decides to re-use this code function in a secure way or 2) disable the postal feature and remove the pre-hook.  I have chosen option 2 and this change will be in fixed in release v3.6.4 (Currently posted as latest alpha release).

I was able to replace the pre-hook method with a post-hook method.  The functionality is different in that the original method kept the blizz autocomplete from occurring by disabling the function call.  As mentioned above this is no longer possible due to the re-use of this function in secure code.  When the post hook code fires it hides the drop down.  So autocomplete drop down is displayed and then hidden which results in the same end user result.  Fixed in current alpha and will be in v3.6.5 release.