1 agent_kith Nov 30, 2016 08:54
3 fplanque Dec 15, 2016 02:42
Do you know a view to reproduce this 100% of the time?
Thanks.
4 agent_kith Dec 15, 2016 03:15
Do you know a view to reproduce this 100% of the time?
Thanks.
No. It only happened some of the time when I first reported this. And I just tried to do the same to the post that triggered it and can't get the same thing again.
To be honest I'm not sure if this is a b2evolution issue, or my provider. I did a support ticket with them on this and they checked and said it didn't trip anything.
I'd let you know once I find a way to do this 100% of the time. Thanks for looking into this.
5 agent_kith Dec 20, 2016 09:40
Been trying to find a way to do this but unfortunately can't.
Here are some more information which may help (or more likely send you down some wild goose chase)
Strangely this only happen to posts I'm drafting. Editing and saving published posts so far don't trigger this error. Not sure if the text itself is an issue, but in general the posts I'm working on are usually around 2000 words or more.
Also only started to have this issue in 6.8.1 and 6.8.2.
6 agent_kith Dec 23, 2016 05:43
So, I've modified the code in question slightly and print out the contents when it's content_scroll, the code is
bad_request_die( sprintf( T_('Illegal value %s (%d) (%d) (%s) (%s)'),
$var,
!is_scalar( $GLOBALS[$var] ),
!preg_match( $regexp, $GLOBALS[$var] ),
$GLOBALS[$var],$regexp ));
And I get the following output. So on appearance the problem is the contents of "content_scroll" is a floating number, but the type says it's of integer. And hence the error.
I'm not familiar enough with the code yet to know if there is some deeper issues at work here. And odds are there are deeper issues at play, because this failure doesn't happen 100% of the time.
7 fplanque Dec 26, 2016 07:55
Ok thanks, we think we have identified this and fixed it. It should be working in the next release (coming soon).
8 agent_kith Jan 13, 2017 03:07
Just a quick follow, am on 6.8.3-stable for a couple days now, and AFAICT this issue is gone. Pretty confident this is fixed now.
Thanks again to the b2 team for the great software that is b2evolution!
9 fplanque Jan 13, 2017 17:13
Thanks for the confirmation.
Attached screencap which is probably easier to see.