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

Plugins are silently ignored and that costs users a lot of time #442

Open
errordeveloper opened this issue May 5, 2017 · 2 comments
Open

Plugins are silently ignored and that costs users a lot of time #442

errordeveloper opened this issue May 5, 2017 · 2 comments

Comments

@errordeveloper
Copy link

@errordeveloper errordeveloper commented May 5, 2017

I and many others spent hours debugging they plugins when running locally, please see jekyll/jekyll#5265 (comment).

This is a UX problem, it should be easily fixable with big fat warning!

@benbalter
Copy link
Contributor

@benbalter benbalter commented May 5, 2017

We could provide warning-level build feedback e.g. "Notice: Custom plugins are disabled when previewing locally", but I think the better, more descriptive solution would be for Jekyll to warn when a plugin is requested but ignored.

@Giszmo
Copy link

@Giszmo Giszmo commented Apr 18, 2020

If I forked a project that used the github-pages gem for github deployment but I don't want to github-deploy, how do I deactivate this "feature" of blocking plugins that are forbidden on a platform I'm not using?

I would want bundle exec jekyll serve --trace to print a big fat warning:

"There is files in the _plugins/ folder. Are you trying to use plugins? GitHub only allows a short list of plugins. If you want to override this limitation for local builds, do this little trick: ..."

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

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.