-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Please upgrade TGMPA to latest version #6
Comments
Closing as clearly there is no interest in fixing this. |
This was update long ago. |
@stueynet Glad to hear it. In that case, all the more reason for closing the issue. |
Oh and just FYI: in the mean time TGMPA 2.6.x has come out, so you may want to upgrade again ;-) |
This is great. Will look at integrating it right now. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
We noticed you are using the TGM Plugin Activation library in your plugin.
You are using an old version. The latest version (2.5.2) fixes some - published - security issues as well as offering tons of bug fixes and new features.
We would like to urge you to upgrade to the latest version of TGMPA.
Download the latest version | View the changelog
When you upgrade, you may also want to adjust the config you use as some settings were deprecated in v2.4.0 and new ones introduced in v2.5.2.
More information on the current settings
Most notable changes:
is_callable
setting to the plugins array for plugins which offer both a free and a premium version - see https://github.com/TGMPA/TGM-Plugin-Activation/blob/2.5.2/example.php#L85-L95'parent_menu_slug'
and'parent_url_slug'
config options were removed in 2.4.0. Similar functionality was re-introduced in 2.5.2 with the'parent_slug'
and'capability'
config options.The up-to-date example file can be found here: https://github.com/TGMPA/TGM-Plugin-Activation/blob/2.5.2/example.php
If you would like to stay informed of new updates and developments, please follow the TGMPA account on Twitter.
Kind regards,
The TGMPA team
The text was updated successfully, but these errors were encountered: