marikamitsos

I totally agree with you. Better to take one step at a time. Really looking forward to the new release.

Hello @adiant
I downloaded and installed v4.0. My errors log did not register any issues. So I guess that is out of the way. Great !!!
I find very clever the dropdown and the inhereted properties. That’s brilliant. I have to admit though that I found the new design quite overwhelming. I wonder whether you could consider the following points to possibly improve the ergonomics:

Places:

1. The settings are gone from the network dashboard where they used to very conveniently reside (…/wp-admin/network/plugins.php?page=jr_rnap_network_settings). Why? After all it is a network plugin only visible by super admins (or maybe -using a hook- by just one of them).
2. When on my site (…/MYsite/wp-admin/plugins.php?plugin_status=active), where I have just 2 active plugins I also see all info of our 76 inactive plugins
3. On the “othersite” (…/OTHERsite/wp-admin/plugins.php?plugin_status=active), the “otheruser”, who is NOT a super admin, canNOT by default see the must use plugins. But now, all info, even for the mu-plugins and the drop-in plugins are presented by this plugin.

Content:

1. The settings under their own url were quite compact. We could see -almost- all of them on a single screen.
2. I believe there is a sufficient amount of info in the plugins screen (…/wp-admin/network/plugins.php OR …/OTHERsite/wp-admin/plugins.php). The objective of this plugin could be focused on its very special functions without creating an overkill. Another improvement on real estate could be to only show the php file name along with the name of the plugin instead of the whole path . Meaning: Catch IDs (catch-ids.php)

A super admin will most likely set the choices once and… again when a new plugin is installed. Once in a blue moon.
Finally, if I may suggest 2 options of a possible page layout of the plugin’s settings page. The first one being in the default alphabetical order and the second giving priority to the activated plugins.
To further support my suggestion I attach an image of a though I had about the layout of the plugin’s network settings (2 versions).

Let me know what you think.

I downloaded the file. You can delete it. We’ll talk soon.

Thank you @adiant Sure thing. I will be happy to test it and help out. Since it is summer though, I will spend much less time on my mac. But please, do let me download it as soon as you are ready. This will also clear ground for any possible future enhancements.

Thank you for the reply.

The installation is a basic multisite one. Even the theme used is twenty …something.
Since it is a test site we will not go through the pain of back and forth emailing till it is solved,=. After all it has to do with your PRO version. Sorry
The important thing here is that you have been made aware of a very annoying issue. It would be nice you were to fix it.
As for us for the time being, we moved on to another non-problematic solution

Hi @amirzia and thank you for your answer.

We really appreciate all your efforts?on updates and improvements. Support though is a different department.

Open-source software has free users (not to be confused with freeloaders). Successful business models built on open-source software create potential customers by tending free users, assuring them of the support they will be receiving as future customers.
Answering questions like this or this or this may seem outdated. Still. Resolving these or older ones even now, builds up a bank of knowledge and confidence.

My multisite is still on PHP 7.4 (safe for older plugins). Probably, that is why I didn’t have that message.

Code is evolving all the time. Still. You are a coder of proven competence. I am sure it is something you can handle. Even if it will take some time. Looking forward with anticipation to the new version

Thank you for the new?Version 3.2 release. No deprecated warnings whatsoever.

Still. There is a new warning for each Must-Use plugin thrown on activation and every time there is a change (de/activation) on any plugin on any site.

PHP Warning: file_get_contents(.../wp-content/plugins/...): failed to open stream: No such file or directory in .../wp-includes/functions.php on line 6864

I guess the plugin is now looking for must-use plugins in the wrong place.

Could you give it one more try?

Thank you @codexonics for your time spent.

I understand the PRO version has a bunch of options missing from the free version. We will definitely consider it.

Thank you for the quick reply. I guess every single migrate will demand an individual approach.

Couple last things before we mark this as resolved.

1. Is there a way to exclude/filter certain plugin/theme folders from the package and include the rest?
2. Also is there a way to only back-up/restore the DB and uploads of the target multisite including the main site (just in case something goes wrong during migrating a single site)?
3. Will .../uploads/prime-mover-export-files/2, .../uploads/prime-mover-export-files/2 etc be excluded by default during -if any- full back-up? After all they hold every sub-site’s package and can unnecessarily bloat the full back-up package.

Thank you @jamiebergen

Thank you for the reply.

Great work ??

@jamiebergen Thank you for your reply.

It is now clear to me about one user.

How can I hide them from more than one users? (I use it on a site and I am administrator 3)

Could this be the solution?

function pnp_hide_notes( $hide_notes ) {

    $hide_notes = TRUE;
    $user_id = get_current_user_id();
      if ( 3 === $user_id ) {
           $hide_notes = FALSE;
           }
    return $hide_notes;

}
add_filter( 'plugin-notes-plus_hide_notes', 'pnp_hide_notes' );

We have created a role that can see the plugins page but not edit them (de/activate, delete/install). How can we hide the notes from that role?

Thank you @dartiss

Looking forward to it.

Thank you.

Please keep in mind that there are -at least to my knowledge- 3 deprecated messages:

Function screen_icon is deprecated since version 3.8.0 with no alternative available. in .../wp-includes/functions.php on line 6078
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available. in .../wp-includes/functions.php on line 6078
Function wp_get_sites is deprecated since version 4.6.0! Use get_sites() instead. in .../wp-includes/functions.php on line 6078

• This reply was modified 4 months, 1 week ago by marikamitsos.