Location: PHPKode > projects > ProNuke. Postnuke To Oracle > postnuke/README-First.txt
POST-NUKE: The Rogue Release (0.70) 
=================================== 

Post-Nuke is an open source, open developement content management system (CMS). 
Post-Nuke started as a fork from PHP-Nuke (http://www.phpnuke.org) and provides 
many enhancements and improvements over the PHP-Nuke system. Post-Nuke is in the 
early stages of developement. If you would like to help develop this software, 
please visit our SourceForge page at http://sourceforge.net/projects/post-nuke, 
or contact J. Cox at hide@address.com

You can also visit us on IRC: Server: irc.postnuke.com Channel: #postnuke



CREDITS
======= 

Development credits have been included from PHP-Nuke. If there 
is an oversight from those files, please let us know. Credit is the payment for 
this project, and we don't want to miss anything, anywhere.

The complete credits file can be found in the html/docs folder.



IS THIS RELEASE STABLE?
=======================

This release is deemed as stable 
as any Alpha release. If you consider PHP-Nuke to be stable software, then you 
will consider Post-Nuke to be stable as well.



CAUTION
======= 

This is a word of caution for those of you that like to use 
plugins that either modify the core files or modify existing tables in the 
database for use. Post-Nuke is in an alpha release phase. We are changing 
rapidly, to either evaluate new ideas, or to add actual completed projects. With 
this in mind, our DB structure is constantly changing, as well as our core 
files. By modifying these areas you are taking a risk that upgrading to future 
versions of Post-Nuke will not go smoothly. This goes for the addons from 
NukeAddon (King Richard is working on completly modularized addons), as well as 
other PHP-Nuke forks, or addon's that make sweeping changes that are not 
isolated to the modules directory.

We will not support anything that changes our core SQL or core files that are 
included in this release.



COMMON INSTALLATION ERRORS
==========================

Files are moved, or are 
made no longer relevant on many occasions during an upgrade. The recommended way 
of doing any upgrade would be to back-up and delete EVERY file that is relevant 
to Post-Nuke in your directory and start fresh. You will not loose any 
information if a backup is made. You also should make a back-up of your SQL 
anytime you make a change to the table structure, which pretty much any upgrade 
will do.  We auto-include any files in the /includes directory, and if these are 
no longer relevent (such as advheadlines.php, meta.php, or any future 
modifications) they will cause you problems.

Please, do yourself a favor and back-up and delete all of your files in your web 
directory that are relevent to Post-Nuke or PHP-Nuke. This will save you many 
fustrations and problems.

If you doubt that the install file updated your database, then try running 
postnuke_update.php which is outside of the root. This will check your table 
structure and make updated if needed.

"A Problem Occurred" indicates a cookie conflict. If you are running multiple 
instances of any Nuke flavor site, then you will need to delete your cookie in 
order to fix this problem. Work is being done to fix this in later releases.

Other common problems involve not CHMOD'ing your config file, or having your 
magic quotes settings wrong in your /etc/php.ini file. These are the correct 
settings:

*** SNIP *** ; Magic quotes for incoming GET/POST/Cookie data. magic_quotes_gpc 
= On

; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc. 
magic_quotes_runtime = Off    

; Use Sybase-style magic quotes (escape ' with '' instead of \'). 
magic_quotes_sybase = Off

*** /SNIP ***



A WORD ABOUT SECURITY
=====================

In order for the modules admin to 
change the name of the module folders to deactivate modules leaves open a hole 
by having to chmod folders 777. This should be your last option.

Your best option is to use the linklist block and create a better main menu as 
described below in HOW TO MAKE YOUR MAIN MENU MULTI-LINGUAL. This option means 
that there is no reason to rename your module folders at all. Future versions of 
Post-Nuke will not include the "Other Options" for the main menu.

The lesser option is to chmod your modules directory 777 and the files inside 
755 in order to activate and deactivate modules that you are using.

We do our best to quickly react to security problems within the script. If you 
feel that you have found something that compromises security, please contact J. 
Cox at hide@address.com



HOW TO MAKE YOUR MAIN MENU MULTI-LINGUAL 
======================================== 

Original URL: 
http://www.postnuke.com/modules.php?op=modload&name=Sections&file=index&req=view
article&artid=18

There is a better way to organize your Main Menu using the Link List. The way I 
am about to describe overcomes any problem that you might have using plugins and 
trying to make the Main Menu multi-lingual.

Instead of using the default Main Menu where you have the "Other Options" 
listed, it would be better to utilize the Link List block. 

Now, you might be worried about the changing of names for your plugins and then 
having to change your main menu everytime. Worry not, my friends. 

Because we have a genious on the staff (Patrick!), the idea of changing plugin 
folder names is built in to the link list. It is very easy to do, and doesn't 
require you to copy and paste the url, and here is how: 

1) Create a new link list in your blocks admin and name it "Main Menu" or really 
whatever you want. 

2) In the title of the content portion of the blocks admin, put whatever name 
you would like for the module. In the case of this site, I decided to name the 
sections, "Project Documentation". 

3) In the URL portion for any plugin just place the plugin name in brackets. 
IE... for Project Documentation on this site I used [Sections] . If this was a 
NS module like the admin modules that you will see in the next release, it would 
be something like this [NS-Sections] . 

4) In the description, just add a quick description for the link. When your 
mouse hovers over it, you will see that description. 

Quite simple. 

You also have the choice of inserting a row if you forgot and need to add 
another link, along with deleting an entry all together. After each new row, 
just save the block and move on to the next row. 

I hope this helps someone that might be confused as to how to make your Main 
Menu ML compatible. I believe PostNuke is the only script that uses this method.



INSTALLATION ============

FRESH INSTALL ------------- Upload the files into your 
website root directory.

CHMOD config.php 666

If you are on virtual hosting, or cannot make a SQL DB from a script, make your 
DB at this time. The rule of thumb is this: if you can make a DB from 
phpMyAdmin, then the install.php script will make the database for you, 
otherwise you need to make it.

Point your browser to install.php (should be in your website root directory)

Follow instructions from there.

Your config file should be written during the installation. If not, please add 
your db info in the config.php within your website root directory.

In your admin preferences select your default language for your site.

Please see FINALIZING INSTALLATION, below.

This should be all you need to do.



UPGRADE FROM POST-NUKE .62, .63, .64 ------------------------------------ 1. 
Back-up the website (all files in, for example, /var/www/html/*).

2. Back-up the databases (nuke, forum, etc.). DO NOT delete the databases within 
MySQL. This can be accomplished by executing the following command for EACH 
database you wish to back-up. You can achieve this by doing the following as the 
root user for each database you want to backup, with MYSQL_USER being the MySQL 
username, MYSQL_PWORD being the MySQL password, and MYSQL_DBASE being the name 
of the database you wish to backup:

	mysqldump -u MYSQL_USER -p$MYSQL_PWORD -B MYSQL_DBASE -c -a --add-drop-table 
	>MYSQL_DBASE.sql

3. Delete ALL PHP files (*.PHP) in, for example, /var/www/html, recursively. It 
is okay to leave ANY files that were not part of the Post-Nuke distribution, 
including graphic files and HTML files.

4. Extract the Rogue distribution to /var/www/html.

5. CHMOD 666 config.php

6. Point browser to http://www.yoursite.com/install.php. Follow instructions 
from there.

7. Post-install: Delete install.php and the install directory.

In your admin preferences select your default language for your site.

Please see FINALIZING INSTALLATION, below.

This should be all you need to do.



UPGRADE FROM PHP-NUKE 5, 5.1, 5.2, 5.3 -- ML-NUKE 5.0 
----------------------------------------------------- Upload the files to your 
website root, overwriting your current PHP-Nuke 5.0 files.

CHMOD config.php 666

Point your browser to install.php (ie: http://www.yoursite.com/install.php) and 
follow instructions for upgrading from PHP-Nuke 5.0. All upgrading can be done 
from this file.

REMOVE meta.php and javascript.php from your includes folder.

Open your config.php and enter the proper database settings.

In your admin preferences select your default language for your site.

Please see FINALIZING INSTALLATION, below.

That should be it.



UPGRADE FROM PHP-NUKE 4.4 ------------------------- Upload the files over your 
current PHP-Nuke 4.4 files

CHMOD config.php 666

Point your browser to install.php (ie: http://www.yoursite.com/install.php) and 
follow instructions for upgrading from PHP-Nuke 4.4. All upgrading can be done 
from this file.

Open your config.php and enter the proper database settings.

In your admin preferences select your default language for your site.

Please see FINALIZING INSTALLATION, below.



UPGRADE FROM POST-NUKE 0.51 OR EARLIER -------------------------------------- 
Upload the files over your current Post-Nuke files.

CHMOD config.php 666

Point your browser to install.php (ie: http://www.yoursite.com/install.php) and 
follow instructions for upgrading from Post-Nuke .5.1.xx. All upgrading can be 
done from this file.

REMOVE meta.php from your includes folder.

Open your config.php and enter the proper database settings.

In your admin preferences select your default language for your site.

Please see FINALIZING INSTALLATION, below.



UPGRADE FROM PHP-NUKE PRE 4.4 RELEASES -------------------------------------- 
You will need to download the upgrade files that are located on 
http://www.postnuke.com in the downloads section. You must upgrade to 4.4 and 
then just follow the 4.4 instructions in this file. Please see FINALIZING 
INSTALLATION, below.



FINALIZING INSTALLATION ======================= In every case, you will need to 
delete the following:

install.php install directory

This is for your security.

=== That's it. === 

Enjoy this alpha release. :)
Return current item: ProNuke. Postnuke To Oracle