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

Liquid Renderer NIL CASE crash #220

Closed
mrkhdly opened this issue Sep 9, 2016 · 5 comments
Closed

Liquid Renderer NIL CASE crash #220

mrkhdly opened this issue Sep 9, 2016 · 5 comments

Comments

@mrkhdly
Copy link

mrkhdly commented Sep 9, 2016

Description:

When attempting to add a new file to a collection Jekyll Admin errors on save and output errors of Nill Class related to Liquid Renderer.

Tell us a bit about yourself:

  • Version of JekyllAdmin I'm using <HINT: use bundle show to check>: 0.1.1
  • Version of Jekyll I'm using <HINT: use bundle show to check>: 3.2.1
  • Operating System <e.g. OS X, Windows>: Ubuntu 14.04 x64
  • Browser <e.g, Safari, Chrome>: Chrome

Steps to reproduce:

Clicked on Collections Employee
Clicked on orange New Document button
Gave file name, title, content, and three new metadata fields (layout, photo, & name)
Clicked Save and error popped up in the bottom right "Unexpected Error: Could not Update Page"
Stack Trace

I expected the following:

No to error on me.

But got the following, instead:

JekyllAdmin errors/crashed but the new document was successfully created & keeps working.

Other details:

Nope.

@benbalter
Copy link
Contributor

@mrkhdly Can you describe the new file that's written to disk? Does it look as you'd expect?

@mrkhdly
Copy link
Author

mrkhdly commented Sep 22, 2016

The file that was written to disk was normal and it looked as expected.

@mertkahyaoglu
Copy link
Member

@mrkhdly Could you try after updating to v0.2.0?

@jekyllbot
Copy link

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.

@jekyllbot jekyllbot added the stale label Mar 5, 2017
@mertkahyaoglu
Copy link
Member

I believe this is fixed by #320

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