You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have a few Medium posts stored on my filesystem. These posts can be archived using SingleFile, when I open them from Medium without any problem. The posts stored on my filesystem can't be opened normally, as there's something inside the page's script that prevents them from being displayed that way. So I just removed script from the HTML and the page can be displayed in my browser, but then it can't be archived using SingleFile, as it fails with: "this page cannot be saved contains a sidebar experience"
To Reproduce
Steps to reproduce the behavior:
Go to any paywalled Medium post
Archive it with SingleFile - all works ok
Save the post to your file system
Remove script from the saved page, as it has some logic to prevent users from storing medium posts on their filesystems
Open the stored page in your browser - it displays OK
Archive it with SingleFile - "this page cannot be saved contains a sidebar experience"
Expected behavior
The page is archived by SingleFile.
Screenshots
Environment
OS: Win 11
Browser: Chromium based
Version: Latest Brave, Latest Edge
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
I have a few Medium posts stored on my filesystem. These posts can be archived using SingleFile, when I open them from Medium without any problem. The posts stored on my filesystem can't be opened normally, as there's something inside the page's script that prevents them from being displayed that way. So I just removed script from the HTML and the page can be displayed in my browser, but then it can't be archived using SingleFile, as it fails with: "this page cannot be saved contains a sidebar experience"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The page is archived by SingleFile.
Screenshots
Environment
Additional context
The text was updated successfully, but these errors were encountered: