New version for 2.3?

[DevTeam] [Zeke]: I love that I get emailed when someone reports spam on the boards, but I can't do anything about it.
[DevTeam] [Nachonut]: lol i got you
[DevTeam] [Astaldo]: How about "hide email address from public checked" and it's still visible in all my posts...
[DevTeam] [Astaldo]: I'd delete my account on this site, but by the time I realized the problem half the spambots on the planet had it already
[Developer] [Pazza]: Astaldo if you log out and view your profile with a refresh you'll see that your email is hidden.
[Developer] [Pazza]: Your user level on the forums permit you to see emails even though they are marked hidden.
[DevTeam] [Astaldo]: Ah.. thanks for the clarification and apologies for "crying wolf" in that case :
[DevTeam] [Kaidenn]: PAZZA! i miss you.
[DevTeam] [Nachonut]: Lol, it's funny how it takes spam message reports to get me to come back
[DevTeam] [sylvanaar]: Check out the beta tester forum. Need alpha testers and feedback so I can come up with a maintenance plan.
[Developer] [Pazza]: loaded some new spam prevention modules... lets see if this stops the bastards.
[DevTeam] [Maziel]: Thought I'd check in and say Howdy Doody from Australia
[DevTeam] [Maziel]: Yeah the spam from shoes salesmen was becoming insane
[Guest] [Delakando]: What ever happened to the ability to track friend's location by wim? Other then just showing their general zone location.
Zeke pokes his head around the corner.
[DevTeam] [Zeke]: Anybody home?
[Guest] [Theillur]: I would like to know if it is just me.
[Guest] [Theillur]: http://www.wimaddon.com/forums/index.php/topic,1796.0.html
[Guest] [Nev]: I'm here
[Guest] [Nev]: I don't think anyone else is though
[Guest] [tomasio]: great site [url=http://freeonlinemusicvideos.net].[/url] [url=http://freepeopleclothing.org].[/url]
[Guest] [Theillur]: Nev it is not working for Zeke as well.
[DevTeam] [lothaer]: im here
[DevTeam] [lothaer]: ...
lothaer yawns sleepily.
[DevTeam] [lothaer]: sooooooooooooooooo
[Guest] [j3ff]: Hello. It is very quiet. I would love a response to my thread directly below your "Been very quiet" thread!
[DevTeam] [lothaer]: Check out my new post in the Skins forum
[DevTeam] [lothaer]: Posted a new download in the skins forum check it out
[DevTeam] [lothaer]: Zeke, Maziel, Pazza, Nachonut, sylvanaar, Kaidenn, Astaldo where are you?
[DevTeam] [lothaer]: It would be a real shame if WIM was left to die.
[DevTeam] [lothaer]: i think these forums are dead, Sylvanaar dosnt post on them as he only bug fixes when possible. WIMs future isnt very bright
[Guest] [justgiz]: Yea, its rather sad.
[Guest] [silvercola]: I wish it had skype
[DevTeam] [lothaer]: noy possible for a addon to do.
[DevTeam] [lothaer]: ...........
[Guest] [elzershark]: where is the download file?
lothaer beckons everyone over to you.
[DevTeam] [lothaer]: has anyone been able to take WIM to the beta yet?
[DevTeam] [lothaer]: PTR*
[DevTeam] [Maziel]: *sticks head up and looks around*
lothaer cries.
[DevTeam] [lothaer]: who the hell flagged my post as spam?
[Guest] [primalforce]: Hey guys
[DevTeam] [lothaer]: hello Primalforce.
[DevTeam] [lothaer]: PAZZA COME BACK!!!
[DevTeam] [Nachonut]: Ahhh memories
[Guest] [Ignis]: wtb update
[DevTeam] [lothaer]: soooo.....
Pazza starts to complain... Kinda reminds you of Sloans dont it?

[Cacheelma]

Unless I've missed something, there doesn't seem to be any new version of WIM for WoW 2.3? Are you planning on releasing it soon? Current version of WIM causes so many taint-block error that I have to disable it from my addon list.

Please help. Ty.

[Ailani]

I too am having major issues which caused me to disable it from my addon list.  As a guild leader, i am experiencing issues with Rank Titles defaulting to the "Guild Leader" title when changing persmiisions within the Rank Titles when WIM is enaabled.   I am told WIM is corrupting the blizz UI.  When i disable WIM I don't experience this issue.

I hope a new version is released soon...as I LOVE this addon!!

[shashilx]

Please make version that will work with patch 2.3 
I love this addon!!! 

[Dr. Watson]

Umm, I'm not really particularly sure what you people are referring to when you say "It has errors" or "doesn't work", because I'm using this same addon, version and all, and I'm getting little or no errors. Actually the only problem is the misaligned close button and some texture problems. The catastrophic meltdown errors that you're talking about must be from some other addon.

Good job on this addon. It's number 1 on my list......... and it's quite a long one 

[Cacheelma]

While I agree that telling people "they don't know what they're talking about" can end the conversation rather fast, it's not a healthy thing to do to people who're at least trying to help improve your beloved addon.

Agree?

I think we're knowledgable enough to either try using JUST WIM and see if the problem still exists (as in the first reply) or use the "/console taintlog 1" command to log the taint & action blocked problems that occur when you're in combat (I did). Granted, I see several addons that cause the "action blocked" line to appear, and WIM is one of them.

I can reproduce the log again and post it here if some people still have a doubt. The reason why I didn't post it earlier is because I'm not sure whether someone has already discovered the problems and the fix is underway. That's basically what I was asking in my OP, too.

[Dr. Watson]

I didn't mean to come off as a prick Cacheelma. I was just stating that you may need to be a bit more thorough with your explanation. And actually if you would ming posting your Taint Log on here, I'd like compare mine to yours. I could in fact be the one mistaken *GASP* 

[Maziel]

I too am using the current version of WIM and seem to be getting little to no real dramas. I'm sure there are a few problems that do need to be addressed. I had an instance where people whom I clicked 'ignore' on the WIM window still seemed to be able to message me until I disabled WIM for that day. Unsure if it is reproduceable at this point.

I know Pazza is pulling his hair out right now thanks to Patch 2.3; trying his hardest to figure out the texture issues. Rest assured he is working on things, he wouldn't abandon WIM. On the same token, there's almost no reason for him to release something if he hasn't been able to overcome any of the latest problems if you know what I mean.

For those that do have taintlogs, please please please post them so that Pazza can look into the problem. It'll be like a road map, a point of origin for him to look at and be able to start his investigations on them.

For now, we must all wait. Not even the Beta Testers have anything yet to test. If the problems are too frequent for now, grab your taint log report and post them here in one thread to make it easier for Pazza and disable WIM for the time being. Definately don't think Pazza has given up though. =)

If anyone out there in the community has anything to add that can fix any of the problems they are experiencing within the CURRENT release of WIM, please please please post them here to help out poor Pazza. I know there are some brilliant minds out there in this community that can do lua coding and more; so feel free to offer your brain to the collective table here. Any thing that you have been able to tweak / fix by self modding WIM, please post and explain what you've done as it may be the help Pazza needs to get an update to WIM complete. =)

Thank you all for your patience. I'm sure Pazza is sorry for the delay, but as you can all understand, he too is only human and Blizzard has stumped him this time. ='(

[Cacheelma]

Here's my taintlog. In order for the taint (and "action blocked") problems of WIM to appear, you need to open WIM's whisper window at least once (and then you can close it), before entering combat. No need to actually send a message.

Hope this help.

[Maziel]

Thanks Cacheelma. I pray this and any others people attach can help Pazza out so all of us can have a fully working untainted WIM again.

[Edit]
I believe these are the only taints within your log (just went through and removed the repeated ones to attempt to make it easier for Pazza)

• Global variable classFileName tainted by WIM - Interface\FrameXML\FriendsFrame.lua:340 WhoList_Update()
• Global variable PETACTIONBAR_YPOS tainted by WIM - setglobal()
• Global variable CONTAINER_OFFSET_Y tainted by WIM - setglobal()
• Execution tainted by WIM while reading classFileName - Interface\FrameXML\FriendsFrame.lua:343 WhoList_Update()
• Execution tainted by WIM while reading ChatFrame_MessageEventHandler - Interface\FrameXML\ChatFrame.lua:2052 ChatFrame_OnEvent()
• Execution tainted by WIM while reading PETACTIONBAR_YPOS - getglobal()
• Execution tainted by WIM while reading CONTAINER_OFFSET_X - getglobal()
• Execution tainted by WIM while reading CONTAINER_OFFSET_Y - Interface\FrameXML\ContainerFrame.lua:521 updateContainerFrameAnchors()
• An action was blocked in combat because of taint from WIM - VoiceChatTalkers:Hide()
• An action was blocked in combat because of taint from WIM - VoiceChatTalkers:SetPoint()
• An action was blocked in combat because of taint from WIM - MultiBarRight:SetPoint()
• An action was blocked in combat because of taint from WIM - MultiBarBottomLeft:SetPoint()
• An action was blocked in combat because of taint from WIM - ShapeshiftBarFrame:SetPoint()
• An action was blocked in combat because of taint from WIM - PossessBarFrame:SetPoint()

[Erudan]

Here's my taintlog. In order for the taint (and "action blocked") problems of WIM to appear, you need to open WIM's whisper window at least once (and then you can close it), before entering combat. No need to actually send a message.

Hope this help.

From the looks of the taint log,  a lot of the taint seems to be in relation to the UIPanels.  This section is having a massive rewrite in 2.3.2.  Acording to the American UI forums.

http://forums.worldofwarcraft.com/thread.html?topicId=879058320&sid=1&pageNo=18

Might be wise to wait and see.

[Maziel]

So should Pazza wait until 2.3.2 to see if these errors fix themselves?

[Pazza]

Hopefully they release something quickly cause it's irritating me.

[shashilx]

It's soooo cool that ver. 2.3.15 worked with 2.3.0, 2.3.2 but now we have patch 2.3.3 and WoW now said that WIM is outdated.
When new version for 2.3.3 will be released?

[Zeke]

The outdated notice just means the TOC says it's for a version older than the current one. WIM is still perfectly compatible and functions as it did in 2.3.2. It's a simple fix to make it say that it's up to date but honestly it's not worth releasing a new version of WIM just for that.