Closed Bug 1149883 Opened 7 years ago Closed 4 years ago
Etherpad Import fails for team etherpads
So, I have a case where an internal etherpad was used initially but not because the data in it can't be public... just because it was created internally. I have access to see/view said pad, but when trying to import it I got: https://wiki-sandbox.allizom.org/ReleaseEngineering/Buildduty/Notes/Historic Specifically the "login with persona" as wiki text.
Thanks for reporting issues with the ImportFromEtherpad extension. In the future would you please do on that extension's issue tracker? https://github.com/christi3k/ImportFromEtherpad/issues (In reply to Justin Wood (:Callek) from comment #0) > I have access to see/view said pad, but when trying to import it I got: > > https://wiki-sandbox.allizom.org/ReleaseEngineering/Buildduty/Notes/Historic This is intended behavior. The extension imports only what is publicly available, without login. The pad you're trying to import requires logging in to see the content. If there is no reason the pad is set to private, then you should change it to private or ask the team administrator to do so.
I meant to say: "If there is no reason the pad is set to private, then you should change it to PUBLIC or ask the team administrator to do so.
FYI, the extension now test whether or not the pad is public and displays an error if it's not, rather than simply importing the contents of the sign-in page. Details here: https://github.com/christi3k/ImportFromEtherpad/issues/12
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.