search

zoomkoding / zoomkoding-gatsby-blog

✍️ Simple & Neat UI & Full Featured Blog Template
https://www.zoomkoding.com
BSD Zero Clause License
286 stars 49 forks source link

Posts 페이지 업데이트 안되는 버그 #36

Closed yjksw closed 3 years ago

yjksw commented 3 years ago

안녕하세요 ~~!! 이번에 블로그를 새롭게 단장하면서 이것저것 해보고 있는 중입니다 ㅎㅎ 너무 예쁜 테마를 만들어주셔서 감사합니다 !!

다름이 아니라 포스트를 업로드할 때 새로운 카테고리의 포스트를 업로드했는데요,, 홈 화면에서는 새로운 카테고리가 생성되어 탭에 잘 보여지는데 상단의 Posts를 누르고 들어가면 업데이트가 안되는 현상을 겪고 있어요 ㅠㅠ 태그를 클릭하여 들어가거나 url을 직접 입력하여 www.{블로그}/posts/{카테고리명} 을 입력하면 해당 페이지가 잘 나오는데 상단의 Posts를 누르고 들어가면 업데이트 되지 않은 상태로 화면에 나옵니다 ㅠㅠ ALL탭에 포스트 수도 업데이트가 안되구요 !! 혹시나 배포 딜레이 떄문인가 하여 몇시간 기다려보았지만 여전하네요 ㅠㅠ

예시)

제가 현재 적용하고 있는 블로그 주소는 yjksw.github.io 입니다 !!

감사합니다 ㅎㅎ

zoomkoding commented 3 years ago

안녕하세요! @yjksw 님! 블로그 테마를 맘에 들어해주시니 감사합니다! 😀

말씀해주신 이슈를 확인해보니 배포해주신 환경에서는 posts 페이지가 이상하게 보이는데, 로컬 환경에서 확인해보니 재현이 안되네요! image 예상해보기로는 배포 중에 이슈가 발생한 듯한데 deploy를 진행하시면서 나오는 로그를 전달해주시면 확인해보도록 하겠습니다!

yjksw commented 3 years ago 
☁  yjksw.github.io [master] npm run deploy

> zoomkoding.com@1.1.0 deploy /Users/yunjung/Github/yjksw.github.io
> gatsby build && gh-pages -d public

success open and validate gatsby-configs - 0.075s
warn Plugin gatsby-remark-images is not compatible with your gatsby version 2.32.13 - It requires gatsby@^3.0.0-next.0
warn Plugin gatsby-remark-prismjs is not compatible with your gatsby version 2.32.13 - It requires gatsby@^3.0.0-next.0
warn Plugin gatsby-remark-copy-linked-files is not compatible with your gatsby version 2.32.13 - It requires gatsby@^3.0.0-next.0
warn Plugin gatsby-remark-smartypants is not compatible with your gatsby version 2.32.13 - It requires gatsby@^3.0.0-next.0
success load plugins - 0.622s
success onPreInit - 0.027s
success delete html and css files from previous builds - 0.005s
success initialize cache - 0.002s
success copy gatsby files - 0.042s
success onPreBootstrap - 0.012s
success createSchemaCustomization - 0.066s
success Checking for changed pages - 0.001s
success source and transform nodes - 0.076s
success building schema - 0.169s
info Total nodes: 158, SitePage nodes: 28 (use --verbose for breakdown)
success createPages - 0.151s
success Checking for changed pages - 0.000s
success createPagesStatefully - 0.035s
success Cleaning up stale page-data - 0.001s
success update schema - 0.014s
success onPreExtractQueries - 0.000s
success extract queries from components - 0.255s
success write out redirect data - 0.003s
warn The icon(static/favicon.png) you provided to 'gatsby-plugin-manifest' is not square.
The icons we generate will be square and for the best results we recommend you provide a square icon.

success Build manifest and related icons - 0.088s
success onPostBootstrap - 0.094s
info bootstrap finished - 3.108s
success run static queries - 0.014s - 3/3 215.09/s
success run page queries - 0.127s - 17/17 133.61/s
success write out requires - 0.002s
success Building production JavaScript and CSS bundles - 3.379s
success Building HTML renderer - 2.241s
failed Building static HTML for pages - 0.812s

 ERROR #95313

Building static HTML failed for path "/posts/스프링부트"

See our docs page for more info on this error: https://gatsby.dev/debug-html

  Error: ENOENT: no such file or directory, open
'/Users/yunjung/Github/yjksw.github.io/public/page-data/posts/스프링부트/page-data.jso  n'

  - render-page.js:657 getPageData
    /Users/yunjung/Github/yjksw.github.io/public/render-page.js:657:1022

  - render-page.js:662 Module../.cache/static-entry.js.__webpack_exports__.default
    /Users/yunjung/Github/yjksw.github.io/public/render-page.js:662:1473

  - render-html.js:30
    [yjksw.github.io]/[gatsby]/dist/utils/worker/render-html.js:30:36

  - debuggability.js:384 Promise._execute
    [yjksw.github.io]/[bluebird]/js/release/debuggability.js:384:9

  - promise.js:518 Promise._resolveFromExecutor
    [yjksw.github.io]/[bluebird]/js/release/promise.js:518:18

  - promise.js:103 new Promise
    [yjksw.github.io]/[bluebird]/js/release/promise.js:103:10

  - render-html.js:28
    [yjksw.github.io]/[gatsby]/dist/utils/worker/render-html.js:28:47

  - util.js:16 tryCatcher
    [yjksw.github.io]/[bluebird]/js/release/util.js:16:23

  - map.js:68 MappingPromiseArray._promiseFulfilled
    [yjksw.github.io]/[bluebird]/js/release/map.js:68:38

  - promise_array.js:115 MappingPromiseArray.PromiseArray._iterate
    [yjksw.github.io]/[bluebird]/js/release/promise_array.js:115:31

  - promise_array.js:79 MappingPromiseArray.init
    [yjksw.github.io]/[bluebird]/js/release/promise_array.js:79:10

  - map.js:37 MappingPromiseArray._asyncInit
    [yjksw.github.io]/[bluebird]/js/release/map.js:37:10

  - async.js:97 _drainQueueStep
    [yjksw.github.io]/[bluebird]/js/release/async.js:97:12

  - async.js:86 _drainQueue
    [yjksw.github.io]/[bluebird]/js/release/async.js:86:9

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zoomkoding.com@1.1.0 deploy: `gatsby build && gh-pages -d public`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zoomkoding.com@1.1.0 deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/yunjung/.npm/_logs/2021-09-22T12_08_08_003Z-debug.log

감사합니다 !!

zoomkoding commented 3 years ago

@yjksw님 빠르게 확인해주셔서 감사합니다! 이전 빌드가 캐쉬되어서 발생하는 이슈 인듯 보입니다! root directory에 public와 .cache 폴더를 삭제해보시고 다시 배포해보시겠어요?

yjksw commented 3 years ago

방금 제거하고 배포하여 잘 동작하는 것 확인했습니다 ~~!! 정말 감사합니다 ~~!! 👍