Juhan

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.)

The plugin now supports also php 8.x. Our best thanks to developer!

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

I have to correct again myself (or to add), that the testing was done to find out best free Multilingual plugin (or free version of any) in terms of functionality, which do create permanent translations (excludung the plugins that do only “live” or “machine” translation with help of Google Translator etc.) And there were two winners for me: Polylang and nLingual, >600 000 downloads and >60 respectively. I did not ask any help from Polylang, but the kind developer of nLingual, he answerd me very-very quickly!

Thank You for partaking in my thoughts! My best thanks to our kind developer!

“…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, 6 months ago by Juhan.

Plugin needs to be downgraded first (for example with WP Rollback); then can be deleted.

Thank You!

Thank You very much for help!

Still I am not sure where to put in this code. Yet anyway I am contented with this plugin. Unfortunately my new backup site with WP cancelled working (for some other reason). Otherwise I could have made a rollback and test WP Menu Icons with original WP 4.9.

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.

I cleared the log file from the server. Then I disabled all other plugins and then activated the faulty one WP Menu Icons 3.0.1 (at least for ClassicPress 1.5.2, a fork from WP 4.9.8). And the log I have copied into a file that I will include as shared link.

The site is in a subfolder /s2; it is a back-up site. Now I switched off again this plugin. (Also front-end gave a white screen.) I hope You can get the needed info. It has been a rule of thumb that the plugins that work with WP 4.9.x also work with CP, but of course there could be exceptions.

Nevertheless I would use this free plugin with CP: simply it is the best for menu icons.

https://drive.google.com/file/d/1WM3zgWaEqjUvq3hkLuHpe6lMNnBkX-m8/view?usp=sharing

You can try to do rollback to an earlier version; and then delete the plugin.

It helped to delete, when I did at first rollback to an earlier version. The plugin itself did work as described.

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

Thank You for answering, in connection with one of my favourit WP plugin!
Really it works well, both the newest version 2.7.7, and also all the other recent versions work well. The small issue is just that this plugin officially needs WP 5.0 or later, so with ClassicPress it does not allow directly install from WP Plugins directory as “Ad plugin”; (and of the WP 4.9x I no not know whether it does allow.)
Yet, as I recently found, the latest version could be downloaded with the download link from www.ads-software.com plugin page: https://www.ads-software.com/plugins/admin-menu-tree-page-view/
And I think it can be used in real life also as latest version with CP/WP 4.9.x, or getting the version which is officially suported, with plugin WP Rollback.
I now understand, that the previous versions must be somewhere in WP servers. Just for unknown reason for me, some plugins who do offer rollback do offer also previous versions as a link from the section “Advanced”, but Your plugin does not.
I am not familiar with code; I suppose You have some reason to determine that the latest versions of Admin Menu Page Tree View do not support WP 4.9x (the last one officially supported probably was v. 2.7.1).
That the ClassicPress does not allow directly install versions not supported officially by WP 4.9x, this of course is a matter of developers of CP.

I think, I had opened this ticket, hoping that such a wonderful plugin could be more easily obtained also by these who use ClassicPress, or WP older than v. 5.0. I hope You got some useful information to continue the developing.
Maybe one more thing: When one has many pages, the tiny font of this plugin is very useful. With only some pages one probably would like to use bigger font. I got a solution for myself changing the minimum font size in one browser.
I do not know, how easy could be for You to offer changable font size with this plugin?

To add something interesting, I have 2 installs of CP v 1.4.3 and 2 of WP 6.0.2. Three of them use an older MySQL, apparently v. 5.6x. And only one of the WP installs uses the database Maria DB v.10.3. I could not find any other possible reasons that with latter this plugin uses about 3-4 times less server time and does 9 queries per page, as with the other three does 18 queries (metred with “Query Monitor”) — if I did use the right terms here. And it seems it does not depend of the version of Your plugin.

Juhan,
Tartu, Estonia

• This reply was modified 2 years, 2 months ago by Juhan.

Not tried yet with this plugin, but with many other plugins it has been helpful to use translator plugin, for example Loco Translate. If the right instance of text ## More Words could be find with translator, then it can be changed (or removed).