-
Notifications
You must be signed in to change notification settings - Fork 35
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
On saving page only regenerates once #132
Comments
Not sure either, what OS and version of Node and such are you running? Haven't seen anything like this for a long, long while. |
I'm on OSX 10.11.4, Node v4.4.3, Ruby 2.0.0p648. |
Would it be possible for you to try this in Ruby 2.3 and Node 6? |
I am having the same issue. Mine will regenerate scss changes but not any changes to html files. |
Ditto. Content or template edits only inject once on save. |
Bah, strange. Haven't seen this myself before. I'll look into it. |
I think something has changes with how gulp watches files/runs commands. I'm looking into it but due to exams I have very little time until the end of May. |
I just upgraded and had similar results. |
A temporary fix for this would be to do a manual reload.
|
Yeah, I used to do that but I think it's not technically correct and has some strange behavior. But I might just revert to it. |
@nsocrates thank you very much, that works fine for now. |
I'm having this problem too. The gulp file modification sorta works but having to save multiple times before its refreshes. |
You can change your gulpfile to what was posted below, it'll work. Just to confirm, it's only for HTML and markdown it's not working? |
Yea just HTML |
I'm having the same problem with the page changes only regenerating once. I also get the following warning, seems related...
|
That error usually comes from Jekyll being upgraded and having older gems in your system. Try to clean out old gems. |
Thanks for the tip there. I've actually reverted Jekyll to 3.0.5 and cleared out older gems. Here's my gem list now...
I actually deleted some of the newer version of gems I had that weren't in line with the github pages dependency versions . Now I have an error Any ideas what to do here? |
Not really, I'd force clean all your gems and reinstall. That's what I usually do, nuke it from orbit 😄 |
I'll give it a shot. I just noticed my local grunt CLI version is 1.2.1. Is that right? |
Grunt? I hope you meant gulp :P I haven't actually looked at the version of that since I switched to gulp 4.0. |
Haha, sorry yes, I meant Gulp. So I nuked my gems, and re-installed, and that has removed any errors. I still only get the regeneration on the first page change though I'm afraid. |
Yeah, I'm in the middle of my exams so I won't have time to fix it until next weekend in afraid :) |
No problem. Good luck with your exams! |
The reason is here: gulpjs/gulp#1626 (comment) I've fixed this by creating function: function doRealod(done) {
reload();
done();
} and using it instead of gulp.watch(['src/**/*.md', 'src/**/*.html', 'src/**/*.yml'], gulp.series(log, 'jekyll', doReload));
// ....
gulp.watch('src/assets/images/**/*', doReload); |
Yeah, I saw this pop up on the 'gulp' repo yesterday as a pull request on how to use Gulp 4 with BrowserSync. Thanks though! 😃 |
I've pushed a new version of |
Tried to set up a site today and kept running into something i'm not sure how to resolve. It seems when running running either
gulp
orgulp --prod
I can save a change to a file once and then my site will no longer regenerate.I'm getting this in the console which i'm not really sure how to make sense of and was hoping you might have an idea where to look
The text was updated successfully, but these errors were encountered: