Shoutbox

I am using WLM 2009 (Build 14.0.8117.416) + Messenger Plus 5.00.0.702 .

For the Chat Logging, I am using "Separate the logs of different Messenger accounts", "Organize in: One folder per contact", Save as: HTML Files"

When a new incoming msg pop up a new log html will be generated, it won't continue in the same log of the month. But it do continue saving under the same html until I close the chatting window. In the each contact's log saving folder now I have Feb , Feb (2), Feb (3), Feb (4), ....

I wonder how to solve this problem in order for it write the log in the same html file of the month as in the past.

Please advice with thanks!

You need to give us time to reply.

This certainly appears to be a bug. It should not duplicate the month folders.

quote:

---

Originally posted by matty
You need to give us time to reply.

This certainly appears to be a bug. It should not duplicate the month folders.

---

thx
there should be Feb.html, Feb (2).html, Feb (3).html, ......

It could be some kind of issue with file permissions. Where do you save your logs (the exact path)? Do you have admin privileges on the Windows account you are using? Are you saving logs to the same location from different Windows accounts?

quote:

---

Originally posted by Menthix
It could be some kind of issue with file permissions. Where do you save your logs (the exact path)? Do you have admin privileges on the Windows account you are using? Are you saving logs to the same location from different Windows accounts?

---

I saved the log in D: and I have the administrator right to save and write files. I have the similar settings using on my Netbook with no error. I wonder why this happened on my desktop.

i have tried to reinstall both WLM and MsgPlus. But the problem still exists.

What if you change the logs folder to something else?

In the Plus! settings: Logs -> Chat Logging -> Store log in -> Press the '...' button. Make a new folder and tell Plus! to save logs there. Do not copy your old logs to this new folder (yet). See if this helps, I still think it is some kind of file permissions issue.