Johnny,
1) The error is caused when a variable is assumed to be an object of a
particular type, but for some reason it isn't (probably a null). Sounds
like it might have been a bad write (note there is no pagedata).
Does it fail on this page or all pages?
2) The error message says exactly where the files are:
/home/mark/public_html/phpwiki/lib/Template.php line 212
/home/mark/public_html/phpwiki/lib/WikiDB.php line 536
Which version of phpwiki are you using? Without that it is pretty hard
to figure out what is happending or you could post +/- 10 lines around
the lines in question.
jbw
Johnny L. Wales wrote:
> Hiya!
>
> We've been using phpwiki here for quite some time. We really like
> it. But, someone was trying to do something or other (what, exactly, they
> were doing is a little fuzzy) and somehow broke it in such a way that
> everytime we go to one particular keyword, it produces the following
> error:
> lib/WikiDB.php:536: Warning[2]: Assertion failed
>
> Fatal error: Call to a member function on a non-object in
> /home/mark/public_html/phpwiki/lib/Template.php on line 212
>
> So, I need to know a couple things:
>
> 1. What might cause that error?
> 2. How can I figure out where all the files are stored on my installation?
>
> We're using a Mysql backend, but when I try to look at the offending
> record, I see the following:
>
> +-----+-------------+------+----------+
> | id | pagename | hits | pagedata |
> +-----+-------------+------+----------+
> | 862 | WebraryTags | 11 | |
> +-----+-------------+------+----------+
> 1 row in set (0.00 sec)
>
> Which looks just like a non-offending page:
>
> +-----+------------+------+----------+
> | id | pagename | hits | pagedata |
> +-----+------------+------+----------+
> | 678 | Tech Talks | 251 | |
> +-----+------------+------+----------+
> 1 row in set (0.00 sec)
>
> The person who broke it said he was trying to add some ! before keywords
> to make them not be links. He'd add a few !, hit preview, add a few more,
> hit preview, etc. Then, it suddenly broke and won't un-break in any way we
> can come up with.
>
> Any ideas?
>
> Thanks!
>
|
