Book pages on basic mobile site are broken

Using the basic mobile site, I can view a list of the titles in my (or someone else's) catalogue, but selecting the link to an individual title gives the error "Problem with the concurrent query manager". Example: http://www.librarything.com/m/book.php?v=konallis&b=64093676. This has been the case for quite some time.

I know the basic mobile site isn't a development priority, but it's useful to those of us whose phones aren't supported by the LibraryThing app.

Sorry, we're not planning on making any changes or improvements to the old LT mobile site anytime soon. I suspect developers would release an LT app for other devices before anything happens here. Sorry for the trouble.

(Closing as instructed.)

>2 kristilabrie: You realize how absolutely ridiculous that is, right? Forcing people to actually download & install & use an app for a single solitary site, rather than *gasp* actually making a site mobile-friendly? Add to the fact that alexa just got a freaking LT thing, but oh no, not mobile. I am... just boggled by this.

Thanks for the reply, Kristi. I have a BlackBerry. I've already been told that no development for BlackBerry devices will take place because 'they are a dead end'. Is there really no possibility of fixing a simple, OS-agnostic mobile site?

>4 konallis: I can't say with certainty that there's no possibility, but it's not high on our list of priorities at this point, I'm sorry to say.

>3 .Monkey.:

Making LT mobile friendly on every page is a long-term goal. It is not a small thing and, we feel, that the app is useful in ways no website could be--namely that it allows barcode scanning and cover-taking.

>6 timspalding: I mean having an app is fine, especially since, in this case, it can speed up adding (for some folks). But general mobile-friendly is still a huge deal, especially when there's tons of folks who don't have phones that can get the app or don't have the space on their phones for the app or just plain old don't want yet another app.

I think the best short-term approach is to just turn off the sad and broken /m site. Anyone with a smartphone can use the full site on their mobile - it's annoying and inconvenient but at least it's functional, while the /m site is annoying, inconvenient, and non-functional. So the /m site is only necessary for people without smartphones, and while they're still around it's an increasingly small chunk of the population, and not necessarily one to dedicate specific development time to. Better to make the real site mobile/friendly, which helps people with fringe OSes on their phones (Blackberry, Windows phones) and those who don't want the app for one reason or another.