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

Issue #231: Added notifications when plugins are force activated #232

Closed
wants to merge 0 commits into from

Conversation

creativecoder
Copy link

I've added this with the goal of providing feedback to users that indicates why plugins are being automatically reactivated.

Implemented by adding a new method, for possibly extending this to work on forced deactivation, at some point in the future.

@creativecoder creativecoder changed the title Issue #231: Added notifications when plugins are forced activated Issue #231: Added notifications when plugins are force activated Oct 15, 2014
@jrfnl jrfnl mentioned this pull request May 6, 2015
27 tasks
@jrfnl
Copy link
Contributor

jrfnl commented Jan 5, 2016

@creativecoder Hi Grant, sorry for not responding to this PR earlier. A lot has changed in TGMPA since you made this PR, but I kind of like the idea and would be open to adding this for the next release.

Would you be willing to submit a new PR against the current develop branch ?

@creativecoder
Copy link
Author

Yes, I can rebase and submit a new pull request--I'll try to get to that later this week. Thanks, Grant

@jrfnl
Copy link
Contributor

jrfnl commented Jan 11, 2016

@creativecoder Awesome! Thank you. I look forward to it.

@jrfnl
Copy link
Contributor

jrfnl commented Apr 10, 2016

Hi @creativecoder Just wondering if you've had a chance to look at this.

@creativecoder
Copy link
Author

@jrfnl I've submitted an updated pull request here: #569

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

Successfully merging this pull request may close these issues.

2 participants