Sorry if this is the wrong area to post this, but this problem is persistant and repeatable and causes my boss to want to remove b2evolution from our companies website because he "hates" errors. Means the software's not working.
When submitting a new posyt, I get the following error when pinging b2evolutions.net:
Pinging b2evolution.net...
---GOT---
HTTP/1.1 200 OK
Date: Fri, 15 Feb 2008 04:20:51 GMT
Server: Apache/2.0.54 (Debian GNU/Linux) mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-19 mod_perl/1.999.21 Perl/v5.8.4
X-Powered-By: PHP/4.3.10-19
Set-Cookie: cookieevonetsession=9906919_bheFbx6FHzP2vdL1aDSgLO8VopJKkL9Q; expires=Mon, 12 Feb 2018 04:20:51 GMT; path=/; domain=.b2evolution.net
Content-Length: 152
Connection: close
Content-Type: text/html
<br />
<b>Fatal error</b>: Call to a member function on a non-object in <b>/home/b2evonet/www/inc/_core/_param.funcs.php</b> on line <b>1756</b><br />
---END---
HEADER: Date: Fri, 15 Feb 2008 04:20:51 GMT
HEADER: Server: Apache/2.0.54 (Debian GNU/Linux) mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-19 mod_perl/1.999.21 Perl/v5.8.4
HEADER: X-Powered-By: PHP/4.3.10-19
HEADER: Set-Cookie: cookieevonetsession=9906919_bheFbx6FHzP2vdL1aDSgLO8VopJKkL9Q; expires=Mon, 12 Feb 2018 04:20:51 GMT; path=/; domain=.b2evolution.net
HEADER: Content-Length: 152
HEADER: Connection: close
HEADER: Content-Type: text/html
XML error: junk after document element at line 2Remote error: Invalid return payload: enable debugging to examine incoming payload (XML error: junk after document element at line 2) (2)
Done.
General Support
b2evolution CMS Support Forums
Hi Rayvenhaus. Have you had any success with this issue? It is most likely not a bug because it does not happen all the time (even if it's bugging you yah?).
Have you tried getting a fresh copy of the package, unzipping it, and replacing the plugins folder on your server with a new one? Actually all you would need to test for a crapped up file is to replace the "ping b2evolution" plugin... No promises that'll work, but if it does then great and if not then you know it wasn't a crapped up file.