The bug occurred again. Now I registered that it happened right after I had activated cross categories of different collections.
so may be this is the trigger for that bug.
Anyone who can fix this? (@fplanque )

This bug happened for the fist time after Upgrading to 6.11.2

The bug persists and I can neither edit posts nor save them.
So help would be great and is needed. Hope for it.

PS: the URL (linking form "Edit") that leads to the Error Message (but this also applies to any other page, just with different page number :

…/blogs/evoadm.php?ctrl=items&action=edit&p=466&blog=12&redirect_to=https://…/blogs/lector.php/scharfrichter-in-pruefungskommissionen-an-hochschulen?disp=single&title=scharfrichter-in-pruefungskommissionen-an-hochschulen&more=1#item_466

@fplanque
When running the SQL Select directly in my Database the following Error occurs:

#1054 - Unknown column 'a.iver_type' in 'where clause'

It is really annoying that I can not edit any post in any collection of this Installation. This sets my work nearly to unproductive.
So; if there is someone out there in the b2everse who can help me get rid of this bug an fix it, I would appreciate this very much.

Best Regards, Will

@saunders I can imagine 2 reasons when looking at your error message:

1. The webhost has a low limit on MAX_JOIN_SIZE
2. You have so many item versions that the query has gorwn too large.

You could try deleting all version history from evo_items__version. Make a backup first.

@saunders Hello, please try a fix from commit https://github.com/b2evolution/b2evolution/commit/4eb3367ba2998700094927cf884228b2cf595346.

@saunders the above fix attempts to use less join size so that you don't hit the MAX_JOIN_SIZE of your server.

@fplanque @yurabakhtin

after you adviced to contact my hoster, he checked it and did some coding within b2e:

/inc/_core/model/db/_db.class.php
They added

494                //BIG SELECT
495                $this->query('SET SQL_BIG_SELECTS=1');

Now the problem is solved and I am able to edit and save changes.

My Questions:

• should I do the fixes, @yurabakhtin adviced additionally?
• this fix is just for this version and will be overwriten by the next upgrade. So is it possible that you write those lines in the master?

Thanks and Regards, Will

should I do the fixes, @yurabakhtin adviced additionally?

No , you should replace the host fixes with our fixes.

So is it possible that you write those lines in the master?

No. If our solution works, it's more efficient.

@fplanque I did it the way you advised. Your solution works also fine and fixes the problem. - Thanks!

BTW: what exactly does "propose change" - have not found information about and would know, what's it about.

Best Regards, Will

https://b2evolution.net/man/disp-proposechange

@amoun thanks; I already read this information. But in practice there remains a question marks:

• 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.

@saunders

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.

Yes I agree it's dumb :)

Created a new topic on the Proposed Changes issue
https://forums.b2evolution.net/do-not-display-proposed-changes-option-when-in

@amoun thanks