Your comments

Many thanks, now results are displayed!

Nevertheless, something is weird:

=> when you click on a point to see detailed info (of a certain date) it seems that you get *more* info than only for this date (it seems that a few following dats are including).

For instance, when you click on

  • votes for august 22, 2017 (displaying a number N of votes) => the detailed info show more than N lines. But, you can see the associated date and thus the reader is able to ignore the extra lines
  • comments for this same date (displaying a number C of comments) => same idea, you get more than C lines but you have the associated date to ignore the following dats

But it's all the more annoying for other counts like visits or pagesviews: since you also detail far more lines than the ploted value... but there is no precise timestamp of date, so the reader can't filter and ignore extra lines to focus on the ones really detailing the clicked point.

Am I missing something?

OK, I see your last action managed to validate a bit more to get 100%

There remain now only 3 strings with "Orange arrow" status (representing my corrections):

Hope you'll find.


OK, I understand from your explanation that there is a difference between the orange counter named "Needs review" (Upper right) and the number of strings with the orange arrow icon.

But what do you mean by "Translated" section (you just mean that such strings count as translated?)

Then, remains my last question: how to get validated those strings (with orange arrow icons), that most of them are corrections of my own previous translations but that I corrected?

Hello Norman,

Otherwise, is there a smart solution to enable users [...] or be reminded if wanted without voting for it?

If you're speaking hear of a solution for a user to enable the remind notifications without introducing any vote, there is a solution :

=> the button "Follow" just next to the first post is there for this purpose (it becomes a green "Following" if the user click it).


1) Thanks for adding these translation. By the way, I don't know where does the translation of "Caption" into "Légende2" is defined... But the digit '2' at the end should be removed :-)

2) About image resize: oh yes, I did not realize there was an anchor at bottom right corner only, to change the size.

Yes it works... The text field showing current size values of an image was also useful when you wanted fine tuning of identical size between several images. Maybe both possibilities would be welcome?

Nevertheless, it works, that's what is important.


Yes, that's may be true indeed.

Your 2 forums are currently named "General" and "Russian", maybe they would be even more clear on that language possibility with "English" and "Russian": this way a user writing in another language would clearly miss something ;-)

Nevertheless the idea to have to possibility to choose and test any language for the interface would be visibly useful in cases like the initial author (another solution could be a "showroom" userecho forum, only created to enable all languages without any content, but not sure users would find it... and not sure it would be as useful as a genuine userecho forum for a possible customer to make an idea of the localized service).


This question make me think that may take benefit of allowing all languages (and not only EN/RU) for the user interface:

=> this would show the "decorations" of a userecho web site for any new user and have an idea of what would be possible for a community in his language?

Any conclusion?

Considering that this variability in forcing uppercase still occurs regularly:

  • most time the username is displayed with first letter corrected to uppercase
  • but for instance, in notifications e-mails this is never the case (in the text "post by xxx")

=> I guess the most "simple" and "user friendly" would be to keep the name as entered by the user, with no change at display time

(one more reason is that sometimes users in forum choose "aesthetic" uppercase for their pseudo).

Best regards.

I don't know if the new editor is in production.

But I wanted to tell that, strangely, there is a workaround to avoid the bug in Safari (macOS):

  1. you click on "Insert link" as explained in the first message => you get the bug (an empty field)
  2. you redo the same action => the second time the field contains the needed text

Really strange, but perfectly reproducile!

Yes, that was clear:

that's why I suggested that you, as admin of UserEcho (main support site), could allow this voting for closed topics on your own site ;-)