Some words, in some positions in thread titles, cause PHP fatal error.

[john]

It's been noticed before at times on my forums (MINI2 - Fuel For Your MINI Obsession - MINI Cooper - S - One - Diesel - Works - Cabrio) that some threads just don't work. You get blank content (php error reporting is off you see). It doesn't happen very often, so I've never really got into looking at it properly. I've always managed to fix it by renaming the threads a little, but not seen a pattern.

The other day a thread didn't work, it was called "Fantastic News!". I removed the word "News" and it worked.

So today in our test forum I tried two threads.

One called "Some news" the other called "News some". "News some" opened OK, "Some news" didn't work.

In my error logs I see this (full paths etc. changed for security!):

[client my.ip] PHP Fatal error:  main() [<a href='function.require'>function.require</a>]: Failed opening required '/full/path/to/forum/135546-some-index.php' (include_path='.:/usr/share/pear') in /full/path/to/forum/vbseo.php on line 889, referer: http://www.mini
2.com/forum/testing/

Obviously adding the word "news" to my stopword list works, but that's far from ideal as I do feature news on my website.

Any idea why this is happening?

This is with RC 8 by the way, but has been happening with older versions too.

[MichiBeck]

I had a similar problem. In my case "forum" oder "Forum" as last word in thread titles caused the described problem.
One of my custom rewrite rules was 'forum\.php$' => 'forum.html'.
I changed it to '^forum\.php$' => 'forum.html' and the problem was done.

[john]

Thanks!

One of these was the issue (previously there was no ^ before index):

'^index\.php\?page=mini2news&articlestart=(\d+)' => 'news$1.html'
'^index\.php\?page=mini2news&articlestart=0' => 'news.html'

There seems to be no bad side effects from adding the ^ either.