How to install modules that do not change the database structure

26.3.1. How to install modules that do not change the database structure

These are the simplest modules to install. Their installation consists only of copying the module's files in the aproppriate folders in PHP-Nuke. There are no changes to the original tables and no new tables involved.

These modules may consist of only a public part, only an administration part , or both. But how tell if a certain module requires a database modification or not? Generally, a module package comes with the following folders:

html (1)
html/modules (2)
html/admin (3)
html/images (4)
html/sql (5)
(1)
This is a container folder that is not involved in the installation.
(2)
The subfolders of this folder constitute the public part of the module and should be copied under a directory with the module's name in the PHP-Nuke modules folder.
(3)
The subfolders of this folder constitute the administration part of the module and should be copied under PHP-Nuke's admin folder.
(4)
Contains any images used by the module. Its contents should be copied in the PHP-Nuke images folder.
(5)
Contains the file with all the necessary modification commands for the database, if any. It is the existence of such a file (sometimes not with the .sql ending) that suggests that the module in question requires changes in the database. However, its absence is not a sure sign that such a change is not needed at all: some modules will make their changes to the database on-the-fly, e.g. through some install.php PHP script that we will have to open with our browser during installation.

Help us make a better PHP-Nuke HOWTO!

Want to contribute to this HOWTO? Have a suggestion or a solution to a problem that was not treated here? Post your comments on my PHP-Nuke Forum!

Chris Karakas, Maintainer PHP-Nuke HOWTO

 

Site Info v2.2.2

Last SeenLast Seen
Server TrafficServer Traffic
  • Total: 343,859,988
  • Today: 32,255
Server InfoServer Info
  • Dec 11, 2017
  • 01:13 pm PST
 
 

Daily Inspiration