Since its founding in late 2008, 500Eboard has become the leading resource on the Internet for all things related to the Mercedes-Benz 500E and E500. In recent years, we have also expanded to include the 400E and E420 models, which are directly related to the 500E/E500.
We invite you to browse and take advantage of the information and resources here on the site. If you find helpful information, please register for full membership, and you'll find even more resources available. Feel free to ask questions, and make liberal use of the "Search" function to find answers.
We hope you will become an active contributor to the community!
I am not a computer guru, nor I make any claim that I am software inclined, but I find it much easier to navigate through it, at least for me, versus other site (that I prefer not to mention, where I used to be a regular). In my opinion is very well organized and the search function works great, not to mention the technical quality of the posts and discussions.
I immediately see a couple or reasons for its great success (not to say that there are not more): 1) There is only one cook in the kitchen (who knows what is doing) and 2) Chatter and politics are left at the door. Personally I am very pleased with the outcome and as a result I stick my nose daily to see what's being discussed. I am still learning how to use its full potential ...
The 1st thing I do when I wake up in the morning, is to make a 2 cup equivalent of my favorite coffee, then check what's the latest on 500eboard.com ... after which, on to the other MB "forum".
Confirmed that this is somewhat of a bug in the system. Mainly it is precipitated by threads where there are a lot of links or images, and the system is correct in specifying the "jump" to the newest, or first unread, post for that user.
What ends up happening is that the page loads and jumps to the correct post, and then a bunch of content and/or links load after that, throwing the display off and to another post it "bounces" to because of the content loading.
The developers are aware of this, and it's been a topic of active discussion. There is code that is supposed to prevent this issue, but it seems that in some circumstances it is not working consistently. They are following up and trying to solve it, but I'm being told that it may or may not be eventually solved/solveable.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.