There is an issue highlighted by @saunders in post https://forums.b2evolution.net/mysql-error-the-select-would-examine-more-than#c113520
If In-skin editing is not activated and I call e.g. https://fokus.genba.org/6-herausforderungen-der-dsgvo?disp=proposechange the dashboard opens an also a new Entry for a post.
If a post is edited in dashboard contents all, there is also a way to click "proposed changes" - and here the selected post can be saved under proposed, is proposed to accept or reject. - Thats how I understand proposed Changes.>
So may be that in case of not activated In-skin editing option some information is missing; nevertheless the opening of a new entry in the dashboard and offering to save it, not only to propose it, is irritating. That should IMHO not happen.
In that post I confirmed that a blank 'new post' page is invoked when clicking on Propose Change from the Evo-bar whereas in the back office under Collections > All and clicking on a post the option works as expected.
This only works if In-skin editing is activated in In-skin Actions Settings and the user has permission to propose changes to an Item set in the Advanced User Permissions and Advanced Group Permissions.
Surely if it is not going to work in a 'non inskin' editing instance, for example, then the option should not be displayed. ?
Then there is the question of why it doesn't work unless the in-skin editing is enablked but works fine in the back office.