Jon Stovell

> ``` > // Load up the current user safely. > $p = User::load(0); > User::$me = $p[0]; > ``` > > This seems to call ok. This would be...

I have also seen this error occur when trying to log an error that had a very large backtrace string. Specifically, the backtrace string was too large to fit in...

Oh, shortening the backtrace in that case wasn't a problem and I easily solved it. (It was for custom code, and not relevant here.) The point of mentioning it was...

You're right. Thanks.

> Most of these issues you pointed out are present in the Cache API implantation as well. As evident from my copy and paste operations. Not surprising. I didn't get...

It makes sense if you made a typo in the edit reason and want to fix that without making any further changes in the message itself.

@DiegoAndresCortes, could you please also submit a PR to make the same changes in 3.0?

Note: This PR targets release-2.1, but it has been assigned to the milestones for SMF 3.0. The PR will need to be updated and resubmitted to target release-3.0. I am...

Hm. In my tests, the results were also erratic, but somewhat _differently_ erratic than what you describe, @DiegoAndresCortes. The boards always moved, but not always to the right place. More...

SMF is released under a BSD-3 licence, which means SMF can't include code released under the GPL. GPL code can include BSD-3 code, but not the other way around.