I can't recall many issues with the read/unread icons, but I have had users state such issues persist, hence why I tried db tracking several times.

Yes, thats the reaon I am in doubt too. Some users complain that the last read is not working, not even using the same browser on the same machine. They say that going to the last unread moves them to the first post. This does not happen for all threads, but for some.But if JP says that it is not working for multiple pages, well, then... I guess it is chosing between two options that are both not perfect.

Yes, thats the reaon I am in doubt too. Some users complain that the last read is not working, not even using the same browser on the same machine. They say that going to the last unread moves them to the first post. This does not happen for all threads, but for some.

Exactly what happens on my forum.

Originally Posted by: de broekies

But if JP says that it is not working for multiple pages, well, then... I guess it is chosing between two options that are both not perfect.

I can confirm this: it never works with multi-page threads with the database option. I will try for the cookie option in the next few days, even if it will not work by design with multiple client devices, of course.

This bug should really be addressed ASAP, it is a highly appreciated feature.

I also installed the RTW 2.1. But it seems a debug build.Do we get a release build soon or does everyone needs to build the release mode themselfs? I prefer to download the release build instead of installing Visual Studio Express for Web.(I don't know if there is a lot of #if DEBUG which slows down the process, but for me as an admin the sql performance list at the bottom is not pleasant)

I believe that including debug build into binary distribution is nothing else than a mistake. Unless a sounding reason for doing so is specified in big red letters near the download link, at least.Considering strange errors I got using that distribution I personally suppose that there could also be some mix of the versions of the binaries in it.However, I do not think that changing to release build may affect SQL server performance, unless different queries are used for debug and release code, which is highly unlikely.

I believe that including debug build into binary distribution is nothing else than a mistake. Unless a sounding reason for doing so is specified in big red letters near the download link, at least.Considering strange errors I got using that distribution I personally suppose that there could also be some mix of the versions of the binaries in it.However, I do not think that changing to release build may affect SQL server performance, unless different queries are used for debug and release code, which is highly unlikely.

I am sure it was just a mistake and a thing that can happen. I have no problems with that. But when it is reported, I think it should be fixed and Jaben has done that.

Yes, I also had strange errors with the newton json assembly not being the right version. I didn't have this with V2.0.0. I build YAF in release mode, but this error still pops up. Strange thing is:When I update the binaries of the web application on the server (any binairy like YAF or my own) the webapplication crashes due to wrong Newton JSON assembly version and when I touch the web.config (forcing to reload the web application) it runs. Isn't that weird?

Anyways, I have the feeling that the release build is faster. So, I assume there is some #if DEBUG that slows down the process. And yes, I don't assume it is in the queries, but with other stuff.