Module tables and custom database tables

Module tables in bluetronix CMS

Each CMS module can have its own database tables. These tables are managed by the bluetronix CMS and are part of the respective module structure.

The columns of these module tables cannot be changed directly. This ensures that system updates, module functions, and internal scripts continue to work correctly with the intended database structures.

Important: Do not change the structure of an original module table. If you need additional columns or a completely custom database structure, instead create your own copy of the table.

1. Create a custom database table

If you want to customize an existing CMS module, you can copy its MySQL table and save it under your own name.

Suppose you want to extend the shop module with additional database fields. The original table might be called:

Shop

Create a copy of this table and use the suffix _own for the new table:

Shop_own

Subsequently, you can customize the structure of your own table, for example, by adding additional columns.

The original table Shop remains unchanged and can still be managed by the CMS.

2. Create your own module scripts

In addition to the database table, the module scripts that access the respective table also need to be adjusted.

For this, you will create your own versions of the required scripts. The suffix _own will also be used here.

For example, the original shop script becomes:

Shop.pl

your own version:

Shop_own.pl

In your own script version, you can implement individual functions and database accesses.

The original module scripts remain unchanged and can still be updated through CMS updates.

3. Specify the new table name

After creating your own database table and the required module scripts, you must specify the new table name in the corresponding configuration files.

For our example, the new table Shop_own is used instead of the original table Shop.

Original table: Shop

Own table:    Shop_own

Your own module configuration must reference the new table. Likewise, the database accesses of your own module scripts must be aligned with this table.

This allows your individual module solution to work with its own database structure while the original module table remains available to the CMS.

Note: Which configuration entries need to be adjusted depends on the respective module. Use the designated individual configuration files for this.

4. Separate standard files and your own files

For an individual module solution, you should consistently separate the original database table, the standard scripts, and your own adaptations.

The original files and tables remain part of the CMS. Your own versions can be expanded independently and adapted to the needs of your project.

5. Process of a custom module adjustment

If you want to use an existing module with your own database structure, proceed as follows:

1. Kopiere die originale MySQL-Tabelle und speichere sie unter einem eigenen Namen, beispielsweise Shop_own.
2. Passe die Struktur deiner eigenen Tabelle an deine Anforderungen an.
3. Erstelle eigene Versionen der benötigten Modul-Skripte mit dem Zusatz _own.
4. Hinterlege den neuen Tabellennamen in den entsprechenden Modul-Konfigurationsdateien.
5. Passe die Datenbankzugriffe deiner eigenen Skripte an und überprüfe, ob dein individuelles Modul mit der neuen Tabelle arbeitet.

6. Summary

The database tables of the CMS modules are managed by the system. Their columns cannot be changed directly.

For completely custom module solutions, you can copy the original MySQL table, create your own module scripts, and specify the new table name in the module configuration.

This way, you can develop your own database structures and custom functions without changing the original module files or system tables.