====================================
XXIII.
Frequently Asked Questions:
====================================
- Q1.
After the installation of my YapBB, I get this kind of error message:
Fatal error: Failed opening required '/home/test/YapBB-1.1-Beta-Release/include/class_template.php'
(include_path='.:/usr/share/php') in include/global.php on line 877
- A1.
This may have 2 possible causes. Either the file is actually missing,
(which is not very likely) or you have misconfigured your YapBB.
Consult section VII 'Configuration' in this document for more information
about properly setting the variables in 'config.inc.php'.
- Q2.
After I installed YapBB and entered the forum, I get: Parse error: parse
error in include/global.php on line 89
- A2.
Most likely you got PHP3 installed on your server. Either upgrade to PHP4
if possible or download a new version of YapBB, which includes support for
PHP3.
- Q3. I
get these stupid warnings that variables are not initialised.
- A3.
Make sure that this line is in PHP.INI:
error_reporting = E_ALL & ~E_NOTICE ;Show all errors except for
notices
- Q4. What
does this mean?
Parse error: parse error, expecting `']'' in d:\mijn
documenten\school\realtime site\forum\register.php on line 169
- A4. This
is a small error in the initial 1.1 version of YapBB. Please download the
latest update or, preferably, upgrade to version 1.2.
- Q5. I
get this warning (or similar). What should I do?
Warning: open(d:/phpdev/tmp\sess_f3c8361eebcc29f5e6acb3f2382ae70c, O_RDWR)
failed: m (2) in include/global.php on line 734
- A5.
Fortunately, this is not an error caused by YapBB. It is due to a
misconfigured PHP installation. To solve, simply create a directory called
'tmp' in the root of the disc on which PHP is installed. Alternatively,
you can open up your PHP.INI file and find any occurances of '/tmp' and
change them to match your correct 'temp' directory. (usually
C:\WINDOWS\TEMP on Windows platforms)
- Q6.
MySQL said: Got error XXX from table handler
What does this mean?
- A6.
This is probably not an error generated by YapBB, but rather by MySQL.
Possible causes may be a corrupted MySQL database. Consult the MySQL
documentation at http://www.mysql.com/
- Q7.
Is YapBB a copy of XXX?
- A7.
No. YapBB is a 100% original implementation of a forum system. It is not a
copy, rip, enhancement of any of these systems:
YaBB
vBulletin
Ultimate BB
YapBB was written completely from scratch and only uses small pieces of
code that we got from other sources. Those were made availlable for use;
nothing has been ripped.
As for the appearance, yes, we've been inspired by other systems, but the
general layout is just what it is: too general. In my opinion all systems
look alike, one way or another.
- Q8.
The login system doesn't work. After I login and go post a message, YapBB
still requires me to enter my account data. How come?
- A8.
This may be a problem of PHP4.0.3, although we have not determined this
for sure. The sollution is to enable $cfgPHP3compatibility in
config.inc.php. This kicks in the custom session system that works
properly.
- Q9.
Where are all the settings that control the appearance of YapBB?
- A9.
The look and feel is now controlled by template files, which can be found
in the 'templates' subdirectory. All the *.ybt files are actually HTML
files, but are incomplete. They are incomplete in the sence that they only
contain the layout/structure of the end result. The contents (or data) is
still generated within all *.php files. A central CSS file (style.php) in
the directory that contains your template contains all the information
needed to alter the appearance of YapBB. To also alter the structure of
the end result, you'll also need to edit the *.ybt files.
- Q10.
I get these vague errors saying something with 'pe:' or 'ue:'. What are
they?
- A10.
These are generally debugging messages. Under normal circumstances, these
messages should not surface. However, if you've done something that wasn't
expected, they may occur. Please contact us for details. If you do, please
include the original error message and a description of what you think you
did that caused the error.
===============
END OF MANUAL
===============