PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Gravity Forms & Multi-Site

  1. Hey guys,
    I've been experimenting with Gravity Forms on a WPMU install and now on the new WP 3.0 with multi-site.

    I've got a dev license, but I'm actually thinking about keeping it to where users on my site would need to purchase an individual license (let's say I get up to 2 or 3,000 members, this could be a good thing for all of us), but what I'm actually worried about is the "uninstall gravity forms" part of the settings page. Is there any way to remove that feature for all but site admin?

    Obviously, if the plugin works with the mu-plugins folder then I imagine this kind of setting could be hidden from all but the "super admin".

    My other thought was to just remove the "settings" sub-menu option altogether and hardcode the dev license and reCAPTCHA keys to the plugin, but I'm not sure if that's considered "best practice" or even kosher for that matter. I realize too that I'd have to recode that portion on each upgrade which is also not my idea of a good time. Figured I'd go to you guys and see what you think. Awesome plugin. Wanting my users to love it as I do.

    -maosnjames

    Posted 10 years ago on Friday April 30, 2010 | Permalink
  2. You can modify the plugin all you want, just keep in mind you will need to track of your changes and then re-apply them and manually upgrade. But as far as customizing things to meet your installation, that is perfectly fine.

    Posted 10 years ago on Saturday May 1, 2010 | Permalink
  3. I don't know if it is the best way to work, but I activate plugins across the whole site for those I want users to have access to, and then do not make the plugins tab available to them. That way, you can just have GF in your plugins folder and activate it as normal, so other users cannot access it.

    Posted 10 years ago on Saturday May 1, 2010 | Permalink
  4. tdiaz1
    Member

    How's the 3.0 stuff working otherwise, I have not braved 3.0 at all yet. Been waiting for at least Beta 2. Though the current project status says we should have RC with possible release on 15-May, but I don't see that happening looking at all the open tickets.

    Posted 10 years ago on Sunday May 9, 2010 | Permalink
  5. We have a few 3.0 issues we will be addressing in a release next week. They are minor issues... although the biggest one corrects an issue with automatic updates. They change some hooks on the plugin page in 3.0 and deprecated a hook we were using to do automatic updates.

    Posted 10 years ago on Sunday May 9, 2010 | Permalink