v4.4
Updated Edit Box Chat History
-Extended the Edit Box History feature. It will now store up to 40 previous history chat history lines. This persists with each login on a per character basis. This means if you logout and login again your history has been saved and loaded. You can access it immediately by using the UP and DOWN arrow keys.
-You can now use the UP and DOWN arrow keys on the EditBox to go forward and back in the history without using the ALT key.
-Updated the order in which the history is saved and processed.
-Added a few error checks just in case the EditBox is not available on the first chat window.

v4.3
Fixed a bug where chat frames would sometimes stay unlocked.
-FIXED: Forcing all chat frames to be locked after they are restored.
-FIXED: An issue where sometimes the chat index isn't passed correctly. (Thanks Blizzard :P)

v4.2
- New feature and small fix
-Fixed an issue where toggling social buttons would cause an error. (Thanks to ussandil @ wowinterface.com)
-Added a new slash command 'shadow' to toggle font shadows in the the chat windows.
- Small fix for Chat Windows reverting back to defaults when alt-tabbing or changing the UI

v4.1
Small fix for Chat Windows reverting back to defaults when alt-tabbing or changing the UI Scale.
TOC Update Legion 7.1

v4.0
- Small fix for chat frame position saving and restoring. Now also saves all the chatframe settings.
- BNSetMatureLanguageFilter was removed by Blizzard

v3.9
-Toc Update for 6.0

v3.8
-Updated TOC for patch 5.2
-Added a small fix for when Battle.net goes down.

v3.7
-Fixed a stupid bug where blizzard has now prevented ChatFrame1 from moving independently. They must have added this in a hotfix.
-Because of the above fix, the issue with the 'ChatFrame1' is not movable has been fixed.

v3.5
-Fix for an error that would occur if the chatframes were locked and the addon would try to move them.

v3.4
-Updated for Mists of Panderia patch 5.01

v3.3
-Small fix for scrolling
-layout saved first before restored

v3.2
-Another darn fix for positioning... fixed for real now.

v3.1
-Oops small bugfix for saving layout.

v3.0
-Added chat numbers to shortnames if enabled.
-Fixed some serious issues with text going missing on player login.
-Changed the way that chatframes are saved and restored on the screen.
-Fixed a slight bug with the amount of lines in the chatframes.
-Changed the way some settings are applied.

v2.8
-Toc update for patch 4.3

v2.7
-Updated for Firelands.
-YES I'm back to playing WOW, expect updates to all my addons.

v2.6:
-Updated TOC for patch 4.1

v2.5
-This will fix the mysterious floating chat frames for the combat log.
-This will address those chat frames that are docked.
-Enhanced the way the chatframes are saved and restored.

v2.4
-Chat frames will now remember the position you placed them and position correctly on login or reload.

v2.3
-You can now move the chat window to the edges of the screen

Version 2.2:
-Added a slash command to move the editbox to the top or bottom.
-Added a slash command to hide the chat tabs. (They will still show when you mouse over the chat.)
-Fixed an issue where the editbox would prevent you from clicking the chat tabs when it was displayed at the top.

Version 2.1:
-Small update to make the channel short names ignore processing the combatlog.
-Note: I highly recommend updating to this version.

Version 2.0:
-Major changes to the layout of the code
-Added the removal of guild gold loot messages. It will be changed to the default ones.
-Changed the color of the URL links to be a much brighter moss green.
-Changed the way in which the primary code loads up.
-Added slash commands
-Added an option to hide scroll bars
-Added an option to hide social buttons
-Added a confirmation box when changes are done as a ReloadUI is required.
-Added support for short channel names
-Modified the code slightly

Version 1.7:
-Had to add support for SPECIAL channels, since blizzard loves to make everything separate into different channels.
-Added support for Battleground Leader
-Added support for Battle.Net Conversation
-Added support for Battle.Net Whisper
-Added support for Party Leader
-Added support for Raid Leader
-Added support for Raid Warning
-Enhanced the URL parsing a bit more to make sure it supports a whole heap of different URLs.

Version 1.6:
-Had to modified the way that URL's were being hooked.
-Fixed the popup issue ;)
-Had to remove maxlines as it was causing issues.
-Fixed an issue where sometimes the addon would conflict with other chat addons and prevent certain text from appear. Such as Boss Yells and NPC Say speech.
-Changed the way that URL's are parsed. Should no longer affect regular chat text including that of NPC's.

Version 1.5:
-Added a guild invite function to the chat playername right click menu
-Added a who function to the chat playername right click menu

Version 1.4:
-Fixed the class coloring for all the global channels.
-Added a Copy Name option to the right-click menu that appears when you right-click a player name in the chatframe. This will be useful for those times a player name may contain special characters in the name not native to your keyboard.

Version 1.2:
-Apparently global channels were not being affected. This has been fixed in version 1.2

Version 1.1:
-A slight fix for the class colors sometimes not working.

So after reading your reply I went and did what I should have done in the first place. I cleaned out my saved variable files and got rid of the saved variables from the last chat addon I tried. This one seems to be working perfectly now. Sorry for jumping the gun and not trying that first--I really do know better.

That's great to hear! I had reviewed the code and I couldn't for the love of me see how this problem could occurred. The slash commands are initiated on player login. So unless there was another conflict with an addon it shouldn't have happened.

I have been using CleanChat for a long time, and I really depend on it and it does just what I want for my chat frames even though it hasn't been updated since July, 2010.

There are a couple of things that don't work perfectly (never have), but nothing terribly objectionable (I'll get to those in a moment), but I thought I should try a similar AddOn that is more up to date: XanChat!! Here are my first impressions.
They are nearly identical in the end result, except that XanChat has options that can be toggled on/off, whereas CleanChat has no options; it just does what it does. I'm fine with that, and when I tested XanChat I toggled everything to end up how I liked it, and it now looks almost just like CleanChat does. Here are the differences I can see:
1) Memory: CleanChat uses less than 1.5 kB, XanChat about 60 to 75 kB
2) Combat Log fading glitch: CleanChat completely fades every part of the frame, although it doesn't fade immediately on logging but is completely visibly until the cursor hovers over the frame, then it fades completely. Additionally, after RELOADUI the Header Bar (My Actions/What happened to me) and the tab both won't fade completely but remain slightly visible: I estimate about 20%. XanChat never completely fades those parts of the Combat Log frame, whether on initial log or after RELOADUI.

You can see that since I don't need or want the toggle features (although I wouldn't mind having the options there just in case), and because of the memory difference, for now I will continue to use CleanChat even though it hasn't been updated for so long, as long as it continues to work as it always has.

@Xruptor: I'm not trying to condemn your AddOn, or convince anyone that one AddOn is better than the other in any way. I simply want to show you what I found in comparing the two, and give you my opinion regarding what I prefer in this type of modification. If you find something of worth in these comments, great! If not, then nothing gained, nothing lost. I just hope CleanChat continues to work as it has, since I can't see any indication that the author is doing anything with it. But if it does break, maybe yours will still be around for me to fall back on.
And thank you so much for your efforts & dedication in creating and maintaining your series of AddOns; I tried maintaining an AddOn for a while, learning LUA scripting as needed, but I simply wasn't able to dedicate the time & effort to continue to learn what was required to keep it going after a couple of patches broke too many things.
Pardon my long wind; buhbye!

I have been using CleanChat for a long time, and I really depend on it and it does just what I want for my chat frames even though it hasn't been updated since July, 2010.

There are a couple of things that don't work perfectly (never have), but nothing terribly objectionable (I'll get to those in a moment), but I thought I should try a similar AddOn that is more up to date: XanChat!! Here are my first impressions.
They are nearly identical in the end result, except that XanChat has options that can be toggled on/off, whereas CleanChat has no options; it just does what it does. I'm fine with that, and when I tested XanChat I toggled everything to end up how I liked it, and it now looks almost just like CleanChat does. Here are the differences I can see:
1) Memory: CleanChat uses less than 1.5 kB, XanChat about 60 to 75 kB
2) Combat Log fading glitch: CleanChat completely fades every part of the frame, although it doesn't fade immediately on logging but is completely visibly until the cursor hovers over the frame, then it fades completely. Additionally, after RELOADUI the Header Bar (My Actions/What happened to me) and the tab both won't fade completely but remain slightly visible: I estimate about 20%. XanChat never completely fades those parts of the Combat Log frame, whether on initial log or after RELOADUI.

You can see that since I don't need or want the toggle features (although I wouldn't mind having the options there just in case), and because of the memory difference, for now I will continue to use CleanChat even though it hasn't been updated for so long, as long as it continues to work as it always has.

@Xruptor: I'm not trying to condemn your AddOn, or convince anyone that one AddOn is better than the other in any way. I simply want to show you what I found in comparing the two, and give you my opinion regarding what I prefer in this type of modification. If you find something of worth in these comments, great! If not, then nothing gained, nothing lost. I just hope CleanChat continues to work as it has, since I can't see any indication that the author is doing anything with it. But if it does break, maybe yours will still be around for me to fall back on.
And thank you so much for your efforts & dedication in creating and maintaining your series of AddOns; I tried maintaining an AddOn for a while, learning LUA scripting as needed, but I simply wasn't able to dedicate the time & effort to continue to learn what was required to keep it going after a couple of patches broke too many things.
Pardon my long wind; buhbye!

There are plenty of differences between xanChat and CleanChat. Those options your referring to and the additional features that xanChat provides over xanChat add to the overall memory use of the addon. More features and user interaction usually mean more memory. Otherwise I'd just hard-code all the options in the addon itself. CleanChat is as bare-bones as you can get. I at least try to give the users flexibility by providing slash commands and a few other features. Additional variables in a DB have to be stored for these slash command toggles.

Chat Channel name modifications as well as an assortment of other features also increase memory usage.

In this day of age where we have GIGS and GIGS of memory. 75kb is nothing.. it's so miniscule that I'm not entirely sure why it's such a big deal for you. It could be worse it could be several megabytes. I'm glad you pointed it out, but I just don't see the reasoning really.

75kb is nothing.. it's so miniscule that I'm not entirely sure why it's such a big deal for you. It could be worse it could be several megabytes. I'm glad you pointed it out, but I just don't see the reasoning really.

I sent you a PM rather than take up more space here. I'm sorry if I seemed too critical.

That shouldn't occur. It sounds like the frames are locked to begin with. Did you unlock them first before trying to move them? xanChat doesn't unlock frames only locks them after they have been restored. This was done to prevent the exact error you listed above. None of my friends or guildmates have gotten the error you mention above. So it could be a conflict with another addon.

If you STILL get this error even after investigating it, I will look in to it. Please first make sure it's not something else though.

I appear to be having the same issue. I don't get an error message, but with Xanchat enabled and no other addons running, I'm unable to move the main chat frame after unlocking (I can detach the combat log tab, and that will move normally, or resize the chat frame, but the main "General" frame itself doesn't move at all). If I disable Xanchat, the whole frame becomes movable again as expected.

For those of you getting the error, I'm currently investigating it. I've been away on a vacation and should be able to take a look at the issue now. I'll see if I can put out a fix as quickly as possible.

v3.7
-Fixed a stupid bug where blizzard has now prevented ChatFrame1 from moving independently. They must have added this in a hotfix.
-Because of the above fix, the issue with the 'ChatFrame1' is not movable has been fixed.

First of all i would like to thank you for creating this addon. i have been wanting something like this for a very long time and i did not want to use a heavy addon like prat.

However i have a suggestion that will make this addon complete for me.
-Give us the option to be able to Copy stuff from our chat box.

Thanks

Folks have asked for this before I would really love to implement this really I do. However, blizzard in all their infinite wisdom made dealing with the ChatFrame a nightmare. In order to do what you ask, I literally have to store each line in an array (think of it like a list). As this array keeps getting filled more and more memory gets used. I need to have this list so I can retrieve a line the person wants to copy. Eventually the array would be enormous and this addon would take up way more memory than I would like. I made this addon to be extremely small and efficient. No fancy bells or whistles, if I keep adding things to it eventually it would end up like Prat.

Trust me if there was any other way to do it, I would. I would really like to have this added as well but the current system just isn't friendly enough to implement it.

There is an old addon that does exactly what I describe above. The only exception is that he forces it to store only 500 lines (though a user can modify it).