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

Regeneration of _includes files #340

Open
enkota opened this issue Apr 8, 2017 · 8 comments
Open

Regeneration of _includes files #340

enkota opened this issue Apr 8, 2017 · 8 comments
Labels

Comments

@enkota
Copy link

enkota commented Apr 8, 2017

Hey,

As I've noticed from #320 --watch flags are disabled and work from the admin.

When I go to update the header file for instance inside _includes I need to manually go into a post and re-save for changes to update. Am I missing something here? Sorry, pretty new to Jekyll!

@ashmaroli
Copy link
Member

Yes, that's an unfortunate technical consequence. Admin does not support editing template files as of now -- only content files.
The workaround is to comment out this plugin and serve the site again and re-enable the plugin when you're done editing template files.

@enkota
Copy link
Author

enkota commented Apr 9, 2017

@ashmaroli I see! No biggie at the moment, I'll just develop first then add in content via admin later. Thanks 👍

@benbalter
Copy link
Contributor

One workaround that was proposed was a "regenerate" button someplace in the UI.

@mertkahyaoglu
Copy link
Member

@benbalter IMO, there are two ways to achieve this. One is a hacky way which we just send a PUT request to configuration endpoint without any changes to trigger site.process. Second is that we create an individual endpoint for regenerating. Which one do you suggest?

@ashmaroli
Copy link
Member

One workaround that was proposed was a "regenerate" button someplace in the UI.

But since the template file wont be edited via the UI, its still a minor inconvenience.

@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.

@mariusa
Copy link

mariusa commented Jul 11, 2017

I'd like to +1 too. Not only for includes, but also for .js/.css files edited using another editor.
A button in Admin wouldn't help, as it's the same effort to go to terminal, ctrl+c and re-run last command.

The solution would be simply to re-generate when changing files, no matter if files are changed via admin or other editors. Not sure why the admin has to take over re-generation when enabled as a plugin? Just write files to disk, like all editors.

Thanks for considering.

@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.

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

No branches or pull requests

6 participants