The last thing that remains to do before starting with the management of your site, is to configure the file config.php This is important because it sets up a connection between the
PHP files of PHP-Nuke and the MySQL database that manages it.
Important: Use a decent text editor!
Do NOT use Notepad or Wordpad to edit the config.php file! These "text" editors don't deserve this name - they introduce extra invisible characters in the file, causing spurious errors with the
PHP interpreter. Everything will look O.K., but you will spend many hours trying to find out why your PHP tells you there is an
Recommended text editors are UltraEdit (excellent, but not freeware), Crimson Editor , WinSyntax (both good for PHP and Freeware, Crimson
Editor has some feature more than WinSyntax) and HTMLkit (free for personal use).
Various text editors and their functionalities for PHP are discussed in this decent text editor thread.
You need to enter a database username and a password in the config.php file. This user must have administration rights on the PHP-Nuke MySQL database (whose name
you also entered in the config.php file). You configure this user to have administration rights on the PHP-Nuke database by either phpMyAdmin, or from the command
grant all privileges on db.* to dbuser@localhost identified by 'dbpasswd';
This is the database user account, on whose behalf everything is done from the database point of view. That is, no matter which user is doing something in PHP-Nuke, when he presses [Enter], the
command will be forwarded to the database client, who will connect to the database server with that username and password you entered in the config.php. If that username and password were wrong, or
that user did not have "all privileges" on the PHP-Nuke database (the database whose name you entered in the config.php), then the client will not be able to connect
and you will get an error (one of these exactly-speaking but nothing-communicating "...was not a valid resource" errors ).
Let's have a closer look at the configuration process. Compared to the 5.6 version, the config.php file has undergone a radical diet, leaving it with only a few lines. The rest has been moved to
the nuke_config table (Section 28.1). This has created problems with the Splatt Forum (Section 7.1), which also used a
table with that name. When you open the file "config.php" you will see the following near the top:
In place of "localhost" you will have to put the host/server that the database is installed on. If this is your own computer, the "localhost" is O.K., otherwise you will have to ask your
In place of "root" you must put the username of the database user that PHP-Nuke will have to use in order to connect to the database and execute the necessary
database operations. This user must have been grented all privileges to the PHP-Nuke database as discussed above.
You will have to insert the password of the database user here.
In place of "nuke" you will have to insert the name of your database here.
I recommend this to be left to its default value, "nuke", is the prefix that goes in front of the name of every database table.
This is the prefix that goes in front of the name of every database user table. The idea here is that you can have one prefix, i.e. one PHP-Nuke database, but
many user prefixes, i.e. different user tables for different sites. The user tables will have a different user_prefix in their names, but the rest of the tables will still use prefix, thus sharing
the same nuke database among different user bases from different sites.
Leave this to "MySQL", if you have a MySQL database (which will be true in most situations). This is case sensitive, so "mysql" or "Mysql" will not do, it has to be exactly "MySQL".
You should change this key to be a unique key that identifies your site. Ideally, no two sites should have the same key.The site key is used to create the random number for the security image
(Figure 3-28) in the Your Account module and the administration section and is an important but often overlooked security feature of PHP-Nuke. See also Section 23.4.2 for software that can help you create a truly random site key.
This is case sensitive! Remember to use The Capital Letters!!! On Linux systems, if you write a user name or a password without taking care of letter case, the
system will not allow you to log in.
You must distinguish between the database user (and password), which you enter in the config.php file, and the administrator "God" account. The database user is only known to the database. The
administrator "God" account (there are also other administrator levels), on the other side, is created by PHP-Nuke automatically for you. This account, as well as the
users accounts, exist only in the PHP-Nuke database, not in the MySQL server's configuration.
How is this PHP-Nuke administrator created? If you go to the "Home" link of PHP-Nuke., you will then see a message telling you the
following - just do what it tells you:
Welcome to PHP-Nuke!
Congratulations! You have now a web portal installed!. You can edit or change this message from the Administration page.
For security reasons the best idea is to create the Super User right NOW by clicking HERE
Click on that link and it will create the PHP-Nuke administrator account for you.
A superuser is NOT a registered User
A superuser is an administrator with all admin powers. One should call it superadmin, because everyone gets confused at first. It is fine (and normal) to have a superuser admin and a registered
user that have the same name. Be careful with side effects when you are logged in as both, see Login Block on Left
doesn't go away.
We are done, the only thing that remains to do is to enter the administration section (www.yoursite.com/admin.php). The very first time you will log in using "God" as username and "Password" as
password. I recommend you to change these as soon as possible. Immediately after that, you should take some security measures, see Section 23.4.2.
The config.php file also defines two arrays, the $AllowableHTML and $CensorList array. As its name says, $AllowableHTML is an associative array containing entries for all HTML tags that are to be
allowed on your site:
The meaning of "1" and "2" is whether the tag accepts attributes or not. For example, if you want the <p> tag to NOT accept attributes (i.e. you accept <p> but you don't accept <p
align="center">) the you put "1", otherwise (i.e., if attributes like "align" etc. are accepted) you put "2". That this is indeed so, can be seen from the check_html() function of mainfile.php
(see also Section 16.1):
if ($a = $AllowableHTML[$tag])
if ($reg == "/") $tag = "</$tag>";
elseif (($a == 1) || ($reg == "")) $tag = "<$tag>";
# Place here the double quote fix function.
// A VER
$attrb_list = ereg_replace("&","&",$attrb_list);
$tag = "<$tag" . $attrb_list . ">";
} # Attribs in tag allowed
else $tag = "";
The code checks if the associated value to the given tag ($tag) in the $AllowableHTML array is "1" or empty. If this is the case, the value of $tag is only "<$tag>". Otherwise a set of
replacements takes place on the attribute list:
The delQuotes() function deletes duplicate space and adds escaped quotes around each attribute value.
The ereg_replace() function replaces the ampersand (&) with its HTML entity "&".
If the tag is not in the $AllowableHTML array, the line in the code above shows that it is replaced by the empty string, i.e. it is not echoed at all. Thus, if there is an HTML tag that you are
missing, you should enter it in the $AllowableHTML array and take care to enter correctly a "1" or a "2" according to your needs. See for example Smilies in news.
The $CensorList array contains a list of words that you don't want to see in texts of articles on your site.