Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Develop] Fix: multisite admin menu and notices #247

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

jrfnl
Copy link
Contributor

@jrfnl jrfnl commented Jan 13, 2015

As on multisite by default plugins can only be installed from the network admin, it makes more sense showing the TGM page in the network admin and not in the site admin.

On that same note, the admin notices should be shown on the network admin too.

Related issues: #228, #239

As on multisite by default plugins can only be installed from the network admin, it makes more sense showing the TGM page in the network admin and not in the site admin.

On that same note, the admin notices should be shown on the network admin too.

Related TGMPA#228, TGMPA#239
@thomasgriffin
Copy link
Contributor

Would you mind creating this pull request against the master branch? I've not done anything with the develop branch in a while. Indeed, I need to actually remove it as it doesn't quite make sense for this repo.

@jrfnl jrfnl changed the title Fix: multisite admin menu and notices [Develop] Fix: multisite admin menu and notices Jan 13, 2015
As the notices are now only shown on network admin for multisite, thickbox does not need to be loaded on single sites in a multi-site context.
@jrfnl
Copy link
Contributor Author

jrfnl commented Jan 17, 2015

Not ready for merge yet - please see note in the sister-PR: #252 (comment)

@GaryJones
Copy link
Member

Since the sister-PR branch has been deleted, is this PR closeable for now?

@jrfnl
Copy link
Contributor Author

jrfnl commented Apr 23, 2015

Sister-PR branch has been deleted as it was against master and this should be dealt with in dev first. This issue will be tackled in v3.0. I suggest we keep it open until the issue/PR for v3 has been posted and reference this PR in that issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants