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

Undefined index: skin_update_failed_error #240

Closed
parhumm opened this issue Dec 10, 2014 · 5 comments
Closed

Undefined index: skin_update_failed_error #240

parhumm opened this issue Dec 10, 2014 · 5 comments

Comments

@parhumm
Copy link

parhumm commented Dec 10, 2014

I'm seeing this error when select all plugins install(all plugins not one by one):

Notice: Undefined index: skin_update_failed_error in class-tgm-plugin-activation.php on line 2110
@Dedalos
Copy link

Dedalos commented Dec 22, 2014

me too, here the same, the same line (2110´)

jrfnl added a commit to jrfnl/TGM-Plugin-Activation that referenced this issue Jan 23, 2015
Two text strings were only available on default (not automatic) installation.
This fix makes sure they are always available with the installation context.
jrfnl added a commit to jrfnl/TGM-Plugin-Activation that referenced this issue Jan 23, 2015
Two text strings were only available on default (not automatic) installation.
This fix makes sure they are always available with the installation context.

(cherry picked from commit f385bb8)
@jrfnl
Copy link
Contributor

jrfnl commented Jan 23, 2015

This should be fixed by PR #260

jrfnl added a commit to jrfnl/TGM-Plugin-Activation that referenced this issue Jan 23, 2015
Two text strings were only available on default (not automatic) installation.
This fix makes sure they are always available with the installation context.

(cherry picked from commit f385bb8)

Conflicts:
	class-tgm-plugin-activation.php
GaryJones added a commit that referenced this issue Feb 5, 2015
@parhumm
Copy link
Author

parhumm commented Apr 20, 2015

@jrfnl Sorry, what can I do now?

@jrfnl
Copy link
Contributor

jrfnl commented Apr 20, 2015

@parhumm Either apply the changes from #260 yourself or switch to the develop branch in which the changes have been merged.

@parhumm
Copy link
Author

parhumm commented Apr 21, 2015

@jrfnl Thanks, it was solve my problem.

@parhumm parhumm closed this as completed Apr 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants