search

transitive-bullshit / nextjs-notion-starter-kit

Deploy your own Notion-powered website in minutes with Next.js and Vercel.
https://transitivebullsh.it/nextjs-notion-starter-kit
MIT License
6.17k stars 5.24k forks source link

Search not working #143

Closed nickjstevens closed 2 years ago

nickjstevens commented 3 years ago

For my site the search function does not work - it seems to just hang forever and never returns any results.

See https://www.nickjstevens.com/ for the live site where the issue is present.

yizhen666 commented 3 years ago

i also have the problem.Do you work it out now?

zeyugao commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

yizhen666 commented 3 years ago

Elsa Granger @.***>于2021年8月28日 周六11:14写道：

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/transitive-bullshit/nextjs-notion-starter-kit/issues/143#issuecomment-907558432, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO3JIHG7OSANQZGVUEHQML3T7BIDDANCNFSM5BXGUG6A .

Well I add a comment plug-in unit into the codes, this may cause it I think.

hechangran commented 3 years ago

Same issue here. Console says: Snipaste_2021-09-01_19-55-24

nickjstevens commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

How do I "restore the package version"? I have not modified package.json since cloning...

zeyugao commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

How do I "restore the package version"? I have not modified package.json since cloning...

I just copy and paste the original package.json and yarn.lock to fully restore the dependenies. I do add some extra packages, but I won't upgrade version of existing packages. Did you add some packages or do something like yarn upgrade?

txs commented 3 years ago

I have this issue too!

tisuela commented 3 years ago

I have this issue as well...

imbytecat commented 3 years ago

same issue 😂 can someone fix it?

loda13 commented 3 years ago

same issue too，upgrade the react-notion-x version and the other notion dependencies' version，did not work

loda13 commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

How do I "restore the package version"? I have not modified package.json since cloning...

I just copy and paste the original package.json and yarn.lock to fully restore the dependenies. I do add some extra packages, but I won't upgrade version of existing packages. Did you add some packages or do something like yarn upgrade?

problem solved after using your package.json and yarn.lock

hechangran commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

How do I "restore the package version"? I have not modified package.json since cloning...

I just copy and paste the original package.json and yarn.lock to fully restore the dependenies. I do add some extra packages, but I won't upgrade version of existing packages. Did you add some packages or do something like yarn upgrade?

Are you publishing your site via Vercel?

zeyugao commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

How do I "restore the package version"? I have not modified package.json since cloning...

I just copy and paste the original package.json and yarn.lock to fully restore the dependenies. I do add some extra packages, but I won't upgrade version of existing packages. Did you add some packages or do something like yarn upgrade?

Are you publishing your site via Vercel?

Yes. You can check it out at blog

hechangran commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

How do I "restore the package version"? I have not modified package.json since cloning...

I just copy and paste the original package.json and yarn.lock to fully restore the dependenies. I do add some extra packages, but I won't upgrade version of existing packages. Did you add some packages or do something like yarn upgrade?

Are you publishing your site via Vercel?

Yes. You can check it out at blog

I have cloned your blog and published it via Vercel. However, the search still does not work. Did you publish your blog using the default settings of Vercel? Or you have changed some parameters when deploying on Vercel? Thanks.

hechangran commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

How do I "restore the package version"? I have not modified package.json since cloning...

I just copy and paste the original package.json and yarn.lock to fully restore the dependenies. I do add some extra packages, but I won't upgrade version of existing packages. Did you add some packages or do something like yarn upgrade?

Are you publishing your site via Vercel?

Yes. You can check it out at blog

I have cloned your blog and published it via Vercel. However, the search still does not work. Did you publish your blog using the default settings of Vercel?

zeyugao commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

How do I "restore the package version"? I have not modified package.json since cloning...

I just copy and paste the original package.json and yarn.lock to fully restore the dependenies. I do add some extra packages, but I won't upgrade version of existing packages. Did you add some packages or do something like yarn upgrade?

Are you publishing your site via Vercel?

Yes. You can check it out at blog

I have cloned your blog and published it via Vercel. However, the search still does not work. Did you publish your blog using the default settings of Vercel?

I rechecked again. It seems that it only works in my cname domain, the vercel.app domain’s deployment is not working. Also, the local deployment using vercel dev is working. You can check the urls at here

zeyugao commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

How do I "restore the package version"? I have not modified package.json since cloning...

I just copy and paste the original package.json and yarn.lock to fully restore the dependenies. I do add some extra packages, but I won't upgrade version of existing packages. Did you add some packages or do something like yarn upgrade?

Are you publishing your site via Vercel?

Yes. You can check it out at blog

I have cloned your blog and published it via Vercel. However, the search still does not work. Did you publish your blog using the default settings of Vercel?

Well, I got it. The search api url is defined in https://github.com/zeyugao/blog/blob/main/lib/config.ts#L109, which uses domain config under site.config.js. But you change it to an invalid url in https://github.com/hechangran/blog/blob/main/site.config.js#L11

hechangran commented 3 years ago

I ran into this problem after upgrading some of the componets in package.json. After restoring all package's version, the search works.

How do I "restore the package version"? I have not modified package.json since cloning...

I just copy and paste the original package.json and yarn.lock to fully restore the dependenies. I do add some extra packages, but I won't upgrade version of existing packages. Did you add some packages or do something like yarn upgrade?

Are you publishing your site via Vercel?

Yes. You can check it out at blog

I have cloned your blog and published it via Vercel. However, the search still does not work. Did you publish your blog using the default settings of Vercel?

Well, I got it. The search api url is defined in https://github.com/zeyugao/blog/blob/main/lib/config.ts#L109, which uses domain config under site.config.js. But you change it to an invalid url in https://github.com/hechangran/blog/blob/main/site.config.js#L11

Thanks! After changing it to my domain. The search now works.

transitive-bullshit commented 2 years ago

Looks like the issue here was making sure to have the domain set properly in site.config.js.

You can test the search on https://transitivebullsh.it to see it working in action.

Thanks, everyone.