Hi matthius,

Even though I'm not part of the dev team, I thought I'd give you my input. :-)

I got a similar problem in _dataobjectlist.class.php on line 111 in function & get_next().

$r = false;
return $r; -- Notice: Only variable references should be returned by reference--

Instead of modifying the function declaration I simply added

$r = false;
$temp = & $r;
return $temp;

Now it doesn't complain anymore.

I hope this helps,

Regards
-Jor-el

Hi!

Yes the correct fix is
$r = false;
return $r;

Would you guys mind fixing these in CVS when you find them?
(Please contact me for CVS access)

Thanks.

fplanque, read the post above yours again. It seems that "$r = false; return $r;" has been used already, but caused the notice.

Unfortunately problems persist in the CSV 2,0 I recently downloaded. If somebody can tell me how I can upload files (TurtoiseCVS installed) I will fix the files.

Afwas you need to be granted permission, blueyed and francois can grant you that permission. From memory with TortoiseCVS you just make the changes to the file as you normally, right click it, and then "commit", but I haven't used it since b2evo 1.8 came out, so my memory is lacking.

JFI: I cannot grant any permissions.

I found this problem in the latest CVS as of today.

The file is inc/_core/_template.funcs.php line 428

I solved it changing the aforementioned line as this:

$temp = $MainList ->get_item();
return $temp

I'm runing PHP version 4.4.4

This program makes use of the Zend Scripting Language Engine:
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies with the ionCube PHP Loader v3.1.29, Copyright (c) 2002-2007, by ionCube Ltd., and with Zend Extension Manager v1.0.10, Copyright (c) 2003-2006, by Zend Technologies with Zend Optimizer v3.0.1, Copyright (c) 1998-2006, by Zend Technologies

Austriaco, thanks for the fix, I've just committed it (slightly changed).

Is this really true? Did Austriaco just solve a three year old major annoying problem with just one line of code?

WOW

I'd like to take credit, but I merely took the solution from another thread and applied to this particular case.

This is a quite common problem, and there might be other places which need the same fix still.

@blueyed
This, or something very similar is a major Admin problem in the latest 2.1.0 Beta release, as reported here
http://forums.b2evolution.net/viewtopic.php?t=13215

It's another problem over there actually. I remember having (hackishly) fixed the first problem, but have no clue about the others (they are different). You may want to figure out the problem yourself - e.g. by installing xdebug, which provided backtraces for errors, warnings and notices.