-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Site page stats counters on rebuilds #2211
Comments
bep
changed the title
bug: Site page stats counters
Site page stats counters on rebuilds
Jun 13, 2016
I will work on this. |
bep
added a commit
that referenced
this issue
Aug 4, 2016
Work In Progress! This commit makes a rework of the build and rebuild process to better suit a multi-site setup. This also includes a complete overhaul of the site tests. Previous these were a messy mix that were testing just small parts of the build chain, some of it testing code-paths not even used in "real life". Now all tests that depends on a built site follows the same and real production code path. See #2309 Closes #2211 Closes #477 Closes #1744
bep
added a commit
that referenced
this issue
Aug 8, 2016
Work In Progress! This commit makes a rework of the build and rebuild process to better suit a multi-site setup. This also includes a complete overhaul of the site tests. Previous these were a messy mix that were testing just small parts of the build chain, some of it testing code-paths not even used in "real life". Now all tests that depends on a built site follows the same and real production code path. See #2309 Closes #2211 Closes #477 Closes #1744
bep
added a commit
that referenced
this issue
Aug 13, 2016
Work In Progress! This commit makes a rework of the build and rebuild process to better suit a multi-site setup. This also includes a complete overhaul of the site tests. Previous these were a messy mix that were testing just small parts of the build chain, some of it testing code-paths not even used in "real life". Now all tests that depends on a built site follows the same and real production code path. See #2309 Closes #2211 Closes #477 Closes #1744
bep
added a commit
that referenced
this issue
Aug 15, 2016
Work In Progress! This commit makes a rework of the build and rebuild process to better suit a multi-site setup. This also includes a complete overhaul of the site tests. Previous these were a messy mix that were testing just small parts of the build chain, some of it testing code-paths not even used in "real life". Now all tests that depends on a built site follows the same and real production code path. See #2309 Closes #2211 Closes #477 Closes #1744
bep
added a commit
that referenced
this issue
Aug 20, 2016
Work In Progress! This commit makes a rework of the build and rebuild process to better suit a multi-site setup. This also includes a complete overhaul of the site tests. Previous these were a messy mix that were testing just small parts of the build chain, some of it testing code-paths not even used in "real life". Now all tests that depends on a built site follows the same and real production code path. See #2309 Closes #2211 Closes #477 Closes #1744
bep
added a commit
that referenced
this issue
Aug 20, 2016
Work In Progress! This commit makes a rework of the build and rebuild process to better suit a multi-site setup. This also includes a complete overhaul of the site tests. Previous these were a messy mix that were testing just small parts of the build chain, some of it testing code-paths not even used in "real life". Now all tests that depends on a built site follows the same and real production code path. See #2309 Closes #2211 Closes #477 Closes #1744
tychoish
pushed a commit
to tychoish/hugo
that referenced
this issue
Aug 13, 2017
Work In Progress! This commit makes a rework of the build and rebuild process to better suit a multi-site setup. This also includes a complete overhaul of the site tests. Previous these were a messy mix that were testing just small parts of the build chain, some of it testing code-paths not even used in "real life". Now all tests that depends on a built site follows the same and real production code path. See gohugoio#2309 Closes gohugoio#2211 Closes gohugoio#477 Closes gohugoio#1744
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've noticed something weird in
replacePage
onsite.go
.If the original page wasn't built, then it wouldn't be part of
site.Pages
.If you've modified an
unpublishedPage
,replacePage
will be called butremovePage
wouldn't do anything since it can't find it insite.Pages
.addPage
will be called andfutureCount
is increased by1
.If you added a future
publishDate
to an existingPage
insite.Pages
, thenremovePage
will decreasefutureCount
by-1
, andaddPage
will increatefutureCount
by1
, resulting in a net gain of0
.Therefore,
Site stats
afterreplacePage
is called will always be wrong.Should we just keep track a list of
Pages
onSite
that aren't beingbuilt
?The text was updated successfully, but these errors were encountered: