-
Notifications
You must be signed in to change notification settings - Fork 42
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
Unable to create new pads after restoring from SQL #84
Comments
The offending line is https://github.com/hackpad/hackpad/blob/master/etherpad/src/etherpad/pro/pro_padmeta.js#L53 which is caused by https://github.com/hackpad/hackpad/blob/master/etherpad/src/etherpad/pro/pro_padmeta.js#L43 returning null.
|
Theory: either the global or the local pad id are different because the 'encryption' keys were not the original. Potential strategies:
Question: are links to other pads dynamically generated or are the encrypted id's literally in the pad? In the latter case, 2 would break interpad links. Alternative ansatz: before the actual error in the code, the generation of a new pad fails, causing a reference to a non-existant item. To be looked up. |
The issue is caused by the import SQL dropping previously existing stuff. Specifically, a domain with id 1. In order to make this work, it should suffice to enable the |
Ok, this was two problems:
|
Ok, this was two problems, and they are solved now.
|
Having restored Hackpad from an SQL export, having done a password reset and logged in, there's a 500 when trying the create a new pad.
The exception in the backend log is:
The full stacktrace from the frontend exception log is:
When creating pages from a 'pristine' Hackpad it works fine. Could this be related to the Solr index not being present? @pors Any ideas? Hints? Tips? (Will happily make up for it in PR's :p)
The text was updated successfully, but these errors were encountered: