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

v8.19.0 "The resource has been blocked" & "Uncaught TypeError" #728

Closed
3 tasks done
pilgrimlyieu opened this issue Dec 3, 2023 · 3 comments
Closed
3 tasks done
Labels
Bug Something isn't working Solved
Milestone

Comments

@pilgrimlyieu
Copy link

pilgrimlyieu commented Dec 3, 2023

Issue Checklist

Expected behavior

All things normal.

Actual behavior

The official site

The page(not only the official site, but also my blog site after updating to v8.19.0) is empty and I get two errors in Console.(All things normal, without errors in Console in v8.18.2)

1

2

Steps to reproduce the behavior

  1. Visit the official site.

  1. Update blog NexT version to v8.19.0

Node.js and NPM Information

v18.17.0
9.6.7

Package dependencies Information

Seems to be irrelevant. I'll add if necessary.

Hexo Configuration

Seems to be irrelevant. I'll add if necessary.

NexT Configuration

Seems to be irrelevant. I'll add if necessary.

Other Information

Today I visit the official documentation and find it displays nothing. Then I update NexT to v8.19.0 via git pull and get the same thing occurred in my blog. And everything back to normal after using git reset --hard v8.18.2. As a result, I think it may have some thing to do with the new released version.

Otherwise, if it is the issue of my network, just close this issue as invalid.

Thanks in advance!

@pilgrimlyieu pilgrimlyieu added the Bug Something isn't working label Dec 3, 2023
@TScci
Copy link

TScci commented Dec 3, 2023

#727

@njzjz njzjz linked a pull request Dec 3, 2023 that will close this issue
11 tasks
@njzjz njzjz mentioned this issue Dec 3, 2023
11 tasks
@stevenjoezhang
Copy link
Member

Thanks for reporting, it's broken by next-theme/plugins#266

@stevenjoezhang
Copy link
Member

Fixed in c32066a, NexT v8.19.1 released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Solved
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants