Thank You for explaining! (Yet to add something, I use these attributes also to explain something for screen reader users; there is no space to do it except on special page.)

First, dear Doug, our kind developer, thank You for explanation!

The first part of this turned out to be easier than I could have imagined. The second part, admittedly, is beyond my average user level when it comes to WP. But I’m sure this explanation will be helpful for someone else!

To give You some ideas for future, if I would point out a tiny drawback compared to Polylang (the second “winner” in my long tests), I couldn’t avoid the synchronizing the visibility of page title, except offering the synchronizing of other more important functions: if I hide the page title in one language, it will be hidden in other languages as well, both when in my theme settings (Weaver Xtreme), or with special title-hiding plugins. Another small shortcoming (not for me personally) is that with nLingual I couldn’t put the Language changer in the Widget. And also some users may “miss behind” flags for languages (again, I personally do not miss these).

Anyway nLingual has become my favourite now, after long testing in real-life situations (where I also managed to “fool” the multilingual plugins, using multiple slightly different “self-made” locales — I need these because I use several translations of WordPress (ClassicPress) in my mother tonge Estonian.

With best thanks, and hopes that You continue, having understood how good work You have done, without big developer-teams (and marketing-teams as well, however it could be worth of these…)

Juhan, Estonia

Sincerely,

Juhan, Estonia

“…this amazing but almost forgotten plugin” — I mean it seems to be forgotten by users: for some reason I do not understand, one can read that nLingual has “more than 60” downloads, as Polylang has “more than 600 000” downloads.

Also I have to add that our kind developer has showed me in Support (and of course, for everybody) how easy it is to translate Tagline and/or Title of a website with nLingual (and possibly if one has more skills, also any custom area).

“It was in my WP install littlebit slower than Polylang or Bogo.” — Actually it was in some tests a bit quicker than Polylang, especially were both were used with ClassicPress (v1.5.3). The winner could be Bogo, if there were only one language. But with several ones (as in real-life situation) there would be hard to point out “a winner”.

Despite the low popularity, after about a month thorough testing several multilingual plugins, nLingual was one of the winners. If not better, then equal with Polylang (and also Bogo, which unfortunately does not allow to repair pages nor change the language, but has some other minor good characteristics.)

• This reply was modified 1 year, 1 month ago by Juhan.

Thank You!

There is apparently also an aditional delay getting my responses: I am currently in a certain list, and all my responses need to be manually moderated — once I did a post into wrong section.

Ciprian, I am touched by your effort to consider my personal opinion! I think the lowering of the required version encourages also the ~ 7 % of WP 4.9x users (several millions), as also the users of ClassicPress (several thousands?) to find, and also use everyday this useful plugin.
I hope (yet who can speak of others not knowing them!) that most users do not have hundreds of pages. And who has — then even the smallest font probably could not save them. I myself use sometimes also one-two other plugin with this type of functionality — it depends of the task I need to complete (reordering of many pages for example). To accommodate all (titles of) pages on one screen it is good to to have plugin small font. To change the parent-child relation the bigger font is more convenient. One could not hope to get all the best together!

Probably it could be also useful for You to know about the “market”, I put here the 4 more I know (not included some huge plugins that rebuild totally the admin interface as I also do not have tested those).

* Swifty Page Manager
Has special page with page tree, and uses big font, unfortunately with quite low font/background contrast rate).
Creates consistent row with posts and/or pages tree only in page/post editing screen, and it takes quite a lot of space consistently without toggle/hide possibility.

* Nested Pages
Has special page. This plugin sometimes does not like some others (also Your plugin) to have activated simultanously, then some functionality could break (the reordering).

* CMS Tree Page View
Creates pages and/or posts tree on dashboard and on special page.

As You probably know before: no one of the latter can toggle (show and hide) the pages column. Namely, t h i s is the unique good quality of the Admin Tree Page View.

With best thanks,
Juhan, Estonia