From some posts here it seems that others can see their own profile page. I can see anybody’s but my own.
I get “500 - Server error” in any browser. Even on tablet.
I very much like LingQ 2.0 features for the first blink anyway!
What happened to the quick lingQ function?
I do a lot of reading, so I have long imported lessons that I want to run through quickly and mine them for new or newly learned words. Now it’s much slower to run through a piece of text, it seems to only work going sequentially forward through either yellow or blue lingqs at one time.
On the plus side I have now found my home page with all my stats.
Helen, I was a heavy QuickLingQer. I find that things go much more quickly in the new version. I just focus on the right hand information pane and click through the blue words. Occasionally I look at the text if I want some context but mostly I just stay focused on the right hand side,. When I am done I can either go on to my iPad or else go through the lesson again, reading, and looking at my saved LingQs in detail, looking at examples, and tagging as I go. I think that one you get used to it, it will be faster than using the mouse in QuickLingQs and also easier on the elbow tendons.
@skyblueteapot If you click the new words box (at the top of the right panel when you are reading a lesson) you can get a list of the new words in that lesson. This may actually be faster than the previous way since you can see more at a time. Also, with the lingqs box you can essentially do a quicklingq with only Lingqs, which is helpful if you want to mine Lingqs.
We’re still working on improving the speed, but you should notice that pages are loading a lot more quickly now. 
It’s not possible to print vocabulary
You are definitely making progress. Good deal. The two biggest problems I mentioned,
- the sound playing facilities do not appear on the screen, so the lesson cannot be listened to while reading the text;
- the flaschcard interface does not work at all–no popups or anything else.
seem to be solved, at least at first glance. Also, the “500 - Server not found error” (unreported) that was happening for a short while with the yellow-highlighted words but not the blue-, has not occurred recently.
Well done. I’ll try the site more tomorrow.
I am still testing LingQ on my iPad, and I admit I still feel quite frustrated. I always need to open the LingQ window to make new lingqs, as there are no existing lingqs for Polish in Italian, and very often, no matter where I click, something else is selected (e.g. I click on the hint bar and the examples or vocabulary tab is selected inatead). Sometimes I manage to click on the LingQ status buttons or on the arrow to move to the next word to lingq, but one sexond later it will not work.
Right now I am unable to scroll down the Pons dictionary page within the lingq window.
So, there are still some things to fix before we can use LingQ on iPads smoothly.
Anyway, you are doing a good job!
Thanks for letting us know mikebond. We will focus on the functionality on the main site for now but will look at improving the experience on mobile devices as well. Your patience is appreciated .
Of course, Steve, I do understant that mobile compatibility is not your priority now.
:Steve: "I just focus on the right hand information pane "
I’ve been trying that and it is quicker with the mouse than the shortcut keys. In particular the mouse allows “type ahead”, although the “known” / “non-word” boxes move about depending on how many user-created hints there are, so if you are blithely clicking you may end up clicking the wrong one.
It would be helpful if there were a “skip this word” option to click on the right hand information pane. It seems I have to return to the keyboard to click the right arrow to skip a word. (I often skip over words if I don’t know them, yet they clearly aren’t the dictionary form of the word, just to keep my number of created lingqs low).
I think I’ll go back to the explanatory video to see how I am supposed to be creating lingQs. What was the URL again?
@kcb: “with the lingqs box you can essentially do a quicklingq with only Lingqs”
Tried that. Why does the “edit lingq” dialogue box no longer show the status of these yellow lingqs? Whenever I edit a linq I usually bump its status up a notch.
Next grumble:
When I’m working through a list of lingqs in a lesson, either the blue lingqs or the yellow lingqs, if for some reason I want to go back to the last lingq (because I realise I just made a mistake), when I click on the “previous lingq” back arrow the focus of the main lesson pane immediately jumps right up to the top of the lesson and loses my place. It makes the right hand pane jump upwards too, and if I’m not expecting it I then click on the wrong part of the right hand pane.
Also, when I’m working through the yellow or blue lingqs using the right hand pane, as Steve recommends, when I come to a lingq I want to skip I have to use the right arrow key on my keyboard. This moves the cursor to a different place on the lesson pane. When I click back on the right pane, the cursor jumps again. It’s very confusing as I like to keep track of my position in the lesson at the same time as creating or editing lingqs.
Another minor issue: when I move to the last blue word, it automatically turns yellow and is considered as a LingQ before I can write anything. Then, the lesson information window appears and I have to click again on the yellow word to edit it and save my hint. It’s not a serious problem, but it’s a bit annoying. I hope it won’t take long to fix it.
OK, I think I’m starting to get the hang of this. A number of operations which I used to do in parallel now need to be done in sequence. It is now better to edit / review lingqs connected to a lesson separately from creating new ones or marking new words as known, and you can do this, as before, by going to the vocabulary.page via the “edit lingqs” button associated with each lesson.
I think I have to give up on leaving words to be marked as “known” in a later lesson. It seems that with each blue word you encounter you need to make up your mind whether to create a new lingq, ignore it (flag it as a non-word) or leave it until the end of a lesson to be marked as “known” when you hit the “mark all blue words as known” button. This is much quicker if you are prepared to accept that all non-dictionary forms of words will become “known” eventually, so you’re just saving yourself a future job.
One thing I still haven’t worked out is: at what point in the process do you go through a lesson and find words which should be blue, and flag them as “unknown”? It seems that this needs to be done as a separate task, not just as and when you find them while you are creating or editing lingqs.
Switching among blue words with keyboard arrows goes crazy sometimes. For example, it can switch me from #1 to #2, from #2 to #3 etc, and then, after some moment, from #8 to #11, from 11 to 40, from 40 to 9… Going back, it switches from 9 to 40, from 40 to 11… That’s happened with long imported lessons. I wonder if anyone from testers got a try to import really long text?
By the way, when I click “New words” button at the widget, it shows me all the blue words in alphabetical order? Why not to use the order from text (or at least give me an option)?
The good news - saving imported text is really faster now. It is so fast, that even with regular “500 server internal error” and reloading and two pop-ups from Safari the process of saving of a just created imported lesson is faster than it was at old LingQ.