===================
XIII. Known
bugs:
===================
- There
may be some problems when 2 or more YapBB's are installed on the same
webserver. This is related to the session- and persistent login system. To
fix: make sure you enter a 100% unique string in $cfgCookiePrefix in 'config.inc.php'
(only use A-Z, 0-9 or '_').
- On
some pages you are required to be logged in. If you are not, you are
redirected to the login page. After you have logged in, you return to the frontpage,
in stead of to the page where you originally clicked the login link.
- You
have to already be logged in to administer the board, before you 'switched
off' the board in the configuration.
- We
have found that sometimes when the session cookie (PHP4 native) is
initialized, some malformed pages are sent out. Just press refresh in your
browser to fix.
- The
system that takes care of sending out topic change notifications isn't
flawless. The system does not operate independantly (through e.g. a
cronjob) but depends on visitors posting new messages. If no new messages
are posted after the 'timer' resets, the latest notification is never
sent.
- The
registerdate of the administrator defaults to somewhere in 1970, possibly
even 1969. This is because there is no information available about when
the default administrator registered.
- When
reading topics with many posts (around the 160), the machine hosting the
forum may run out of memory. This problem is rarely seen on YapBB systems
with the old template engine. The new template engine solves this problem,
but requires you to have at least PHP4.0.2 installed on your host.
- A
small glitch in the new template engine causes incorrect processing of the
sequence \" (slash, quote). When this sequence occurs in a template
file, the engine only displays the quote. Values that are merged into a
template file and contain this sequence are unaffected.
Note: This bug will probably never be fixed because it's not
important enought to me.