After upgrading to 4.7 should I deactivate this plugin?

  • I cannot find anywhere this information, at this moment I am on 4.7 AND the plugin is still running meaning the upgrade process did not care about it in any way.

    My REST code is working well but is it safe to delete this plugin and stay only on core API?

    I also coded my own enpoints into a custom plugin.

Viewing 5 replies - 1 through 5 (of 5 total)

  • I’m also wondering if this plugin should be ran on 4.7. Or if it should be deactivated.

    Thread Starter Richard Vencu

    (@rvencu)

    I deleted the plugin and all my REST functionality is still working, including the custom extensions.

    I can confirm that this can be deactivated and rest api still works. Although annoyingly, some rest api plugins are badgering me with TGMPA to activate this plugin…

    some rest api plugins are badgering me with TGMPA to activate this plugin…

    Pro-tip you can pass on to the devs of the plugins badgering you: they can probably use the is_callable parameter in the TGMPA plugin array to prevent badgering users about this if the REST API is already in place (as long as the core implementation and the plugin implementation have at least one function or method of the same name)
    https://tgmpluginactivation.com/configuration/

    Good idea @jrf – I will do soon, but as have 4 rest-api related plugins installed I’ll have to do a bit of trial and error to spot which one displaying notice.

    Unfortunately there is no way else of identifying. Ta

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘After upgrading to 4.7 should I deactivate this plugin?’ is closed to new replies.