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

Add extra check if Clarkson_Core_Autoloader exists #111

Closed
JosAchterberg opened this Issue Apr 10, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@JosAchterberg
Copy link
Contributor

JosAchterberg commented Apr 10, 2018

Like Enfold

Sometimes it happends that when switching to theme that doesn't loads
Clarkson_Core via their composer.json but Clarkson Core is installed as
a mu-plugins without it's own vendor folder, then this would trigger
a fatal error. This makes switching themes to easily debug less error
prone.

@jmslbam jmslbam self-assigned this Apr 18, 2018

@jmslbam jmslbam added this to the 0.3.0 milestone Apr 18, 2018

jmslbam added a commit that referenced this issue Apr 18, 2018

Check if Clarkson _Core_Autoloader exists
Sometimes it happends that when switching to theme that doesn't loads
Clarkson_Core via their composer.json but Clarkson Core is installed as
a mu-plugins without it's own `vendor` folder, then this would trigger
a fatal error. This makes switching themes to easily debug less error
prone. Fixes #111
@jmslbam

This comment has been minimized.

Copy link
Contributor

jmslbam commented Jul 12, 2018

Sometimes it happends that when switching to theme that doesn't loads
Clarkson_Core via their composer.json but Clarkson Core is installed as
a mu-plugins without it's own vendor folder, then this would trigger
a fatal error. This makes switching themes to easily debug less error
prone.

@jmslbam jmslbam changed the title Add extra check if Clarkson_Core_Autoloader exists when a non-Clarkson Theme also has a vendor dir with autoload.php Add extra check if Clarkson_Core_Autoloader exists Jul 12, 2018

@jmslbam jmslbam closed this in #114 Jul 12, 2018

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