[BUG] "Default page edit mode" not working correctly

[Vinnecent]

As the title says I think the "Default page edit mode" setting does not work correctly or I don't understand what it is supposed to do.

METHOD

1. "Default page edit mode" setting is set to Read
2. go to any page (the edit mode should now be Read)
3. set the edit mode to Edit on the page
4. go to another page

RESULT After going to a different Site the edit mode is still set to Edit

EXPECTED After going to a different Site the edit mode is set to Read because this is my "Default page edit mode"

[Philipinho]

This is the expected behavior. Changing the edit mode on the page makes an API call to update your preference. It is either you are in read or edit mode.

[Vinnecent]

Then I don't understand why there is even a option like "Default page edit mode"?

[Philipinho]

The reason read mode is there is because people wanted it, to prevent accidental edits.

By default, the editor is in edit state if you have permissions to edit the page.

[Vinnecent]

@Philipinho With how it works accidental edits still happen the same as if the "Default page edit mode" did not exists with how the setting is setup. I have this problem with multiple users (They edit pages without noticing).

That was the whole reason for my issue. Because the setting stays on Edit.

This is how it typically happens:

1. User edits a page
2. User forgets to switch back to Read mode
3. User closes Docmost and does something else
4. User comes back and wants to copy or look something up from any page
5. User doesn't notice he is still in Edit mode
6. User changes something in an article without noticing

Maybe this should be a feature request then. From how the setting is worded, "Default page edit mode" should determine what mode I am in when I enter a new page. It would be great if the behaviour of this setting could be changed or maybe change the name of the setting.

In the end this is just my opinion would be interested to see what other people think of this :D

[millab]

I find this to be a big barrier to Docmost being a competitor to Confluence.

I was really hoping that we could stop accidental edits by setting a user's default to read-only. Many times I have accidentally edited pages after previously editing something else. For my use case as a team knowledgebase wiki, it is very important that the information is not easilly modified, but still want to be able to let users maintain the pages themselves. The best way for this to happen is to require the user to click 'Edit' every time they need to perform this function, but otherwise keep pages read-only.

[bgr]

I would also add that in read-only mode you shouldn't be able to reorder items in the hierarchy, and clicking on the page icon shouldn't open the emoji picker but open the page instead (as if you clicked on the text part of the link).

Edit: it's also not possible to comment on the selected text in read mode, you have to enter the edit mode to comment.

[ttys42]

I find this to be a big barrier to Docmost being a competitor to Confluence.

I don't think Docmost is meant to be a competitor to Confluence. We tried it as well, but the two follow completely different philosophies. In Confluence you have a clear distinction between read and edit modes, while in Docmost everything is essentially in edit mode all the time - and they’ve added this odd "read" feature that doesn’t really make sense. You even don't have a "save" button... in a Wiki system... I think they want to compete with notion or so.