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
Is Notion API stable enough to use for blogs? #163
Comments
I meet the same problem. NotionAPI collectionQuery error Response code 400 (Bad Request), so the collection block doesn't work. Need help. |
check out here: NotionX/react-notion-x#139 (comment) |
Yep, this is what is causing this problem. Just happened today. only the second breaking change that Notion has made like this in probably the last 9 months. So its pretty stable. I am working on making a fix for this right now. |
|
Have you fixed it? |
@XahidEx yes. but I don't think someone has updated notion-starter-kit to take the updates. But react-notion-x has been fixed and the starter kit depends on it. you should be able to update it yourself by going to the packa.json and updating the react-notion-x and notion-client versions. |
|
Fixed! But got another issue. Why my blog posts on the left side? |
This fixes issues mentioned in transitive-bullshit#163
This should now be fixed in If you have separate styling issues, please open a new issue. |
This fixes issues mentioned in transitive-bullshit#163
I just found an issue which seems to be of Notion API.
Your blog (https://transitivebullsh.it/) also is not showing any contents like below.
It is happening to my blog which is thankfully built based on this repo as well.
Even the pages existed (ie. https://notion-blog-seong7.vercel.app/npm-dependency-version) turn 404 not found as below.
Although I've seen such issue only once this time, but got curious if Notion API is stable enough to use for my blog.
I actually didn't even know it yet has only been a beta.
I just want to hear opinions of yours and anyone's who loves this project and build their blogs using it.
The text was updated successfully, but these errors were encountered: