Viewing 8 replies - 16 through 23 (of 23 total)
  • I wonder where the idea that YD Network Wide Options won’t support sites of more than 40 blogs comes from? This is just plain false: the plugin has been developed for a site of more than 100 blogs in the first place. It will support an unlimited amount of blogs if system performance and memory allow fast-enough option replication.

    It is also false that global settings will automatically override individual blog settings: this is an option in the plugin settings (it can either overwrite existing settings, or leave them be).

    Please check out a plugin’s actual features before giving biased advice. Contacting the plugin author might be a starting point. YD Network Wide Options is a completely free plugin and although maybe not perfect for every use, it is absolutely free software, which is sometimes troubling for other individuals promoting commercial solutions. Please consider checking out the free alternative first, and if some feature is missing, donating is a great way to improve the software so that everyone in the community can benefit from the improvement.

    (a bit tired of reading false reviews of my work)

    Sorry, I wasn’t meaning to promote one plugin over the other. Truth is that I use both on my site, each for different reasons. I’ve found both plugins to work wonderfully, though I can’t comment on sites with larger numbers of child sites (I have <20 at the moment).

    As far as I know, it was on the readme of the first rendition?

    My apologies if that is not the case.

    @ydubois – from your change log:

    Bugfix: memory leak when replicating to a large number of blogs
    Bugfix: possible unwanted recursion when updating an option
    Improved settings page design
    Debug messages for diagnosing memory problems

    There are 12,600+ plugins in extend. Expecting that the volunteers who provide support here to keep up to date on all of those plugins is unreasonable. At one point your plugin had issues with a larger number of sites (per the changelog above).

    @ron: Yeah sure, at one time the Earth did not even exist, too 😀

    The point is, a “bugfix” statement in open source code means just that: it has been fixed… a very long time ago. Not to mention that the memory leak that existed when changing a lot of options came from the WP core function and not the plugin itself, so any extension following the same path would have had to get around the same wall.

    I don’t get your point about volunteers. I’m a volunteer too, and easily reachable. Volunteers can refrain from stating judgements about third-party plugins they did not even try out. I have no idea whatsoever on what other solutions around are worth, because I did not try them, especially the commercial ones. I guess they are just great and I respect the people that developed them. But not knowing them, I just avoid giving any kind of judgement. Users of WP-hosted extensions can give stars to rate the actual usefulness of a plugin, they should know because they’re actually using it. 100% of the users of this plugin have given it 5 stars. I guess that means in someway it works OK for them.

    @andrea: I don’t mind, Ron is right it’s hard to keep up-to-date on so many subjects. I would never even have hit on this forum thread if a potential user did not come forward on my developer’s blog and ask if the plugin worked at all. So here is the opportunity for me to state that yes, it works pretty well on a few productions environments that I know about, and the latest version is even cooler because it can also replicate custom table data in addition to any WP option. (meaning some of the plugin settings that could not be replicated up to now are now available: for example, I have WPML auto-installing network-wide on a site.)

    And to make it short: it’s free, so the best way to know if it’ll work for you is to just try it out!

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    And to make it short: it’s free, so the best way to know if it’ll work for you is to just try it out!

    Also to tag posts so the plugin author gets alerted 😉 And report any issues you may have. If they don’t know, they can’t fix it 🙂

    Nearly everyone here is a volunteer. If we all shied away from personal comments when helping, fu**all would get done. Andrea apologized, ydubois accepted, now we know if works. Yay! 🙂

    Back to the topic at hand now. Everyone good with plugin managers or do we still need help there?

    @ydubois – My point about volunteers is that you are expecting the volunteers here to contact you and/or test your plugin prior to responding to threads. Expecting the folks here to keep the contact info and/or test 12,600+ plugins is an unreasonable expectation.

    You could assist the folks here by subscribing to the feed of your plugins forum posts which you can find here – http://wordpress.org/tags/multisite-plugin-manager. Once you are subscribed you can then respond to the thread with what you deem to be accurate/current information.

    @ron:
    I already subscribed to all forum tags directly pertaining to my own plugins. “Multisite Plugin Manager” isn’t the name of one of my plugins. So as Ipstenu advised, this thread should have been tagged with the name of the discussed plugins (which is not easy to do!). There is no way for me to guess where one of my plugins is going to be discussed. Anyway, I am rather glad that people speak of my work, so I won’t complain. And I’m adding the tag now.

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘Best Plugin to manage Plugins?’ is closed to new replies.