Recent Topics

1 Jun 26, 2019 10:56    

Hello,

i have been editing a post and saved it by "save and edit" without problems. After a break I wanted to save the post and got the following MySQL Error.
Since then I have not been able to edit any of my posts. So I cannot even rebuild what happened.
But I hope you will find a fix for that bug.

BUG Proposed - HELP - No editing No Saving: MySQL error! MAX_JOIN_SIZE rows;

PS. In case you checked the link, please delete it before publishing this post

Annotation 1:
After about an hour the system worked fine again. So I presume that there had been some Problems in the cache. In case I can reproduce the bug I will give more information.

Annotation 2:
Since it has happened for second time the bug remains still after 15 hours and I cannot work with b2e because neither editing nor saving works (see next post)

2 Jul 01, 2019 22:05

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

3 Jul 03, 2019 10:04

@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

4 Jul 03, 2019 12:44

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

6 Jul 03, 2019 14:11

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

7 Jul 03, 2019 14:58

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.

9 Jul 03, 2019 17:49

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

10 Jul 03, 2019 18:14

@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 :)

This post has 2 feedbacks awaiting moderation...


Form is loading...

Social CMS – This forum is powered by b2evolution CMS, a complete engine for your website.