-
Notifications
You must be signed in to change notification settings - Fork 135
Support for new Notion URL format #69
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
Comments
@bryanhpchiang it looks like the page you linked isn't publicly shared... unless you recently un-shared it, that would explain why loconotion cannot load the content. There's definitely an issue here though, since shared pages have the new Notion URL format of https://example.notion.site/Page-1F29BC48EA1A029FC481B but sub-pages still have the old format https://notion.so/example/Page-1F29BC48EA1A029FC481B which is a redirect page. For me, loconotion correctly loads the primary public Notion page URL, but times out on any subpages. I think the logic at lines 582-584 of |
@tomreitz merged a pull request from @bryanhpchiang earlier today which should address this, want to pull it and check it's all good? |
@leoncvlt thanks for the quick response (and an awesome project!). Subpages still not working for me, see this public page which converts fine, but the subpages in the table time out, per the logs below
If you go to a subpage directly, you'll see that it is public, but is a redirect page from Notion. |
Thanks for pointing that out - my PR doesn't handle subpages. When parsing the subpages (sub_page_href), the www.notion.so part should be replaced with {site_name}.notion.site. I tried a quick fix but there are a few edge cases in the code that I am probably missing, so not submitting a PR yet. |
Hi, I,m currently running into the same issues. Is there any fix available? |
@bryanhpchiang can you post the partial fix here? Others can try it out and help in fixing the edge cases. |
I'm having this issue as well. Would appreciate the partial fix if possible @bryanhpchiang |
I am not a developer, but there is a quick way to make it work properly. Actually, by simply editing the links at lines 582-584 of
after editing:
when running the program, I used |
Created a PR to Use custom new Notion url format https://xxxx.notion.site instead of default one |
@bryanhpchiang could you please pull the PR and verify if its working for you as well? |
@meSunnySrivastava Thanks for putting together this PR. Confirming that it did work for my website to parse subpages. The only issue is that bullet points are now missing. EDIT: EDIT: |
Sorry I had to close the old PR because I pushed to my master directly. :) |
PR has been merged, thanks all! |
I'm still getting the timeout issue. Exact same as the original post above. The page is set to public: The link is https://jamesdeluk.notion.site/James-IT-Notes-9969909992c04b5ba3a734cdf0a74530 (The Copy Link button gives https://www.notion.so/jamesdeluk/James-IT-Notes-9969909992c04b5ba3a734cdf0a74530, which forwards to the above). |
Thought I'd try this again with the new Notion update. A couple things: Trying to access the .site page itself fails: And webdrive.log loops this:
|
Well, that's not gonna work regardless because you're not logged in, so the script is unable to find the |
That's my confusion though. I am logged in, and the page is public. |
Just checking @leshchenko1979, is this fixed by #92? |
I am using current |
Since Notion updated all URLs for hosted pages (see: #134) this ticket is no longer an enhancement, but a permanent bug. We resolved it in our fork here: https://github.com/sueszli/notionSnapshot/ |
Not 100% sure, but I believe the URL format for Notion shared pages recently changed.
It's now
notion.site
instead ofnotion.so
:Editing view: https://www.notion.so/bryanchiang/Bryan-Chiang-fc01c67a1ed9402e83eb8efd5c99a216
Shared view: https://bryanchiang.notion.site/Bryan-Chiang-fc01c67a1ed9402e83eb8efd5c99a216
I get a parser error with the second one.
Will trying modifying the check for a valid notion.so website.
The text was updated successfully, but these errors were encountered: