rotelok / weblabyrinth

Automatically exported from code.google.com/p/weblabyrinth
0 stars 0 forks source link

Strict Standards: Non-static method #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

Install as per the README file. 

What is the expected output? What do you see instead?

Random text with random hyperlinks.

Instead I get these errors:

Strict Standards: Non-static method dissociatedpress::dissociate() should not 
be called statically in /opt/lampp/htdocs/labyrinth/index.php on line 90

Strict Standards: Non-static method dissociatedpress::cleanToken() should not 
be called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php 
on line 96

Strict Standards: Non-static method Labyrinth::ProcessText() should not be 
called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php on 
line 97

Strict Standards: Non-static method dissociatedpress::cleanToken() should not 
be called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php 
on line 96

Strict Standards: Non-static method Labyrinth::ProcessText() should not be 
called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php on 
line 97

Strict Standards: Non-static method dissociatedpress::cleanToken() should not 
be called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php 
on line 96

Strict Standards: Non-static method Labyrinth::ProcessText() should not be 
called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php on 
line 97

Strict Standards: Non-static method dissociatedpress::cleanToken() should not 
be called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php 
on line 96

Strict Standards: Non-static method Labyrinth::ProcessText() should not be 
called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php on 
line 97

Strict Standards: Non-static method dissociatedpress::findChains() should not 
be called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php 
on line 101

Strict Standards: Non-static method dissociatedpress::cleanToken() should not 
be called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php 
on line 96

Strict Standards: Non-static method Labyrinth::ProcessText() should not be 
called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php on 
line 97

Strict Standards: Non-static method dissociatedpress::cleanToken() should not 
be called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php 
on line 96

Strict Standards: Non-static method Labyrinth::ProcessText() should not be 
called statically in /opt/lampp/htdocs/labyrinth/dissociated-press.inc.php on 
line 97

[...]

What version of the product are you using? On what operating system?

WebLabyrinth 0.3.1

Linux debian 2.6.26-2-686

Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/0.9.8l PHP/5.3.1 
mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 

sqlite 2.8.17

Please provide any additional information below.

Just a small annoyance to be honest. Could just turn error warnings off but 
better to deal with the 'problem' I think.

I think the second post on this forum maybe an indicator viable solution:
http://forums.devshed.com/php-development-5/non-static-method-db-connect-should-
not-be-called-statically-462291.htm

Thanks for an awesome idea and your work on the product!

Original issue reported on code.google.com by ryandewh...@gmail.com on 8 May 2011 at 10:09

GoogleCodeExporter commented 9 years ago
I blame this on the fact that I've never created a PHP class before. :)
Looks like a simple fix.

Original comment by b...@mayhemiclabs.com on 9 May 2011 at 2:15

GoogleCodeExporter commented 9 years ago
This should be fixed in SVN as of r15. Please try it out and let me know if it 
fixes the errors on your end.

Original comment by b...@mayhemiclabs.com on 9 May 2011 at 2:27

GoogleCodeExporter commented 9 years ago
Tested the code base this morning on a box that I could turn on E_ALL without 
worrying about a bunch of apps generating crazy messages. Turns out I missed 
one function call. Fixed in r16. I'll releasing it as 0.3.2 within the next 
couple of days. Please let me know if you have trouble.

Original comment by b...@mayhemiclabs.com on 9 May 2011 at 11:47