"delay": 86400, // one day, in seconds
"loopDelay": 3600, // one hour, in seconds
"text": "The content of this pad has been deleted since it was older than the configured delay."
don't work after putting in settings.json and restart app.
I think a text should be displayed at a new pad, or? In my case there is no text...
Etherpad stores the documents and its data in the mysql database on your VPS. While editing, the clients sync their changes mostly real-time to the server.
I am not fully sure what happens if you are offline and edits cannot be submitted to the server, for some time, then later the client gets online again, while the document already has changed by other clients on the server. Essentially for such more complex conflict resolutions, you have to ask upstream or see what their docs have to say about this.
The latest version has fixed a few issues related login session and shows now the default welcome screen if requireAuthentication is false
I have added a login button on the top right though for users to authenticate and thus have a list of their own pads
@chetbaker we receive bounce emails when contacting you via support. Not sure if your mailboxes are working correctly. However to give an update here on the issue, it seems there is a session bug within etherpad. To clear that up, please visit manually https://pad.example.com/ep_cloudron/logout with your main browser and then attempt a relogin.
@chymian-0 We saw the exact same problem with @robi's instance. Essentially, one of the plugins was preventing the startup. After the log line "Your Etherpad version is 1.8.12", one is supposed to see "http server listening" or something like that. I recommend "npm rm" on each of the plugins as suggested in https://docs.cloudron.io/apps/etherpad/#troubleshooting to debug which plugin causes this issue. Unfortunately, this is the life with plugins in etherpad, they keep breaking between releases 😞
Since I just looked into this, the errors (or rather warnings) from npm are for one thing, that etherpad does not have a package.json file in the root folder, but relies on the node_modules folder for listing. Also npm by default attempts to check for update of itself, which fails and it should not update on its own, since we only test against specific versions.
The vulnerabilities are indeed an issue, however as @girish mentioned we cannot blindly update them, so all those have to be ideally reported upstream with all the relevant plugins even.