new forum front-end and mobile browser

    May 13 2014 | 9:54 am
    While the the new forum front-end looks and works great on a regular browser, it's unfortunately very difficult to read on my mobile browser. (see screenshot). Is that due to my ancient phone or are others seeing the same?

    • May 13 2014 | 4:13 pm
      Hi Jan,
      You might have caught us in the middle of the update for this. But to be sure, can you let me know what device you're using and browser?
      If you prefer, you can also send me an email at
    • May 13 2014 | 9:02 pm
      @ Ginger: does this update affect search functionality? Since yesterday I get only the header with "Search results", nothing else, no results.
    • May 13 2014 | 9:41 pm
      Hi Thinksamuel, yes, the search page was down for a little bit, but it should be up and running now!
    • May 14 2014 | 11:04 am
      Dear Ginger,
      I cleared all caches and reloaded scripts to be sure to have the latest css files loaded. The site still looks the same. My mobile phone is a Samsung Galaxy ACE GT-S5830 (first version of the Galaxy ACE). It's running Android 2.3 (yeah i know it's very old ;) ). I am using the Android browser (not chrome) as well as Opera Mini. That pages sometimes don't render correctly on Opera happens also with other sites - that's due to the data-compression/server-side rendering Opera uses. But in this case the screens look the same on both browsers.
      Best Jan
    • May 14 2014 | 11:18 am
      Hi Ginger,
      this is just for informational purpose: The forum site now throws a JavaScript error when being logged in and viewing a thread:
       Uncaught ReferenceError: _kmq is not defined (index):77
      (anonymous function)
      the error refers to this inline-script:
          _kmq.push(['identify', '']);
                1,             // This custom var is set to slot #1.  Required parameter.
                'Login Status',   // The name of the custom variable.  Required parameter.
                'Logged In',      // Sets the value of "User Type" to "Member" or "Visitor" depending on status.  Required parameter.
                 2             // Sets the scope to session-level.  Optional parameter.
          _gaq.push(['_trackEvent', 'Login Status', 'Logged In', '']);
      it's this line that breaks the code :
      _kmq.push(['identify', '']);
      I haven't noticed any direct breaking of functionality so far on chrome, but my guess is that older Internet Explorers might be affected by that as they usually stop executing scrips on errors....
    • May 14 2014 | 11:39 am
      I've noticed some display issues with the top menu bar on Chrome on Windows. Explorer is fine...
    • May 14 2014 | 8:25 pm
      Thanks for the heads-up, Jan. I've cleaned up that code.
      Lee, can you specify what you actually see when you say "display issues"? A screenshot would be great as well, so I can look into it further.
    • May 15 2014 | 6:05 pm
      wow, as of today the support for safari 4 is gone totally?
      the ajax menu (which does not display since 3 weeks) now fills the whole site and you can no longer scroll down to the forum entries. :)
      the scrollbar scrolls the page only as far as seen in the picture - when it reached that position, it starts to scroll only the content of the subframe (where you can see a bit of a forum post)
    • May 15 2014 | 6:08 pm
      Hi dudes, just letting you know that I'm working on this right now. Thanks for all the feedback and help!
    • May 17 2014 | 8:56 am
      Hi Ginger,
      sorry for making another remark ... I know you are still working on the updates. I noticed that when I view the threads I am inscribed to (in the profile section) they seem to be ordered (my?) last reply-date ascending. So the newest ones are at the bottom. The list under the authored-tab places the newest ones at the top (which I think is the better way ;) ).
    • May 22 2014 | 4:35 pm
      Hey @Jan. No worries. We all use the site, so any suggestions and feedback are welcome. You're right about the topics/replies being in reverse order on the profiles section. I've updated this to start at the most recent ones now.
    • Jun 24 2015 | 12:44 am
      I find the new forum hard to use on my iPhone , I can see three threads at once. No dates, or authors. On my iPad i can see nine and no date info. Most of the screen is empty white space. Native instruments forum in comparison I can see twenty threads at once with author and date info. It just looks way too big and minimal to me, even on my desktop, there is not much actual text on the screen...just raised how old this thread is... And I can't delete my post!
    • Jun 24 2015 | 10:07 am
      I see a bit strange behaviour on my iPad (iOS 8) - actually nearly everything is fine, but for longer threads there is no button for switching to older posts... or maybe I overlooked something?
    • Jun 25 2015 | 5:33 pm
      Hi friends. It's an old thread, but I'm happy to see what we can do to help with mobile versions. We've been focused on the desktop version for a while, so input is always welcome.
      Yaniki, can you send over a screenshot of what you see?
    • Jun 25 2015 | 5:56 pm
      The first pic is what this thread looks like on my iPad mini ios8. I can see three posts. The text is too large and there is alotof empty space. The secnd pic is the thread list - there is no date or post count on the threads. Most other forums I use have about twice as much information on the screen, it just feels like I'm looking through a tiny window at the text, too much scrolling! The third pic is the thread list on iOS 7 on an iPhone 4s. I can see three threads , and no info about post count or dates....
    • Jun 25 2015 | 7:16 pm
      Since ya'll were discussing the mobile view, I figured it would be worth mentioning that the ghostery browser for android crashes without fail when I go to the forums. It looks great, and might let me scroll down a hair, but always crashes. Tested it on a nook hd & samsung galaxy. Since the chrome browser works, it could be on their end, but I thought I would mention it.