CPG Dragonfly™ CMS

DragonflyCMS features an installer class to facilitate new install and upgrade processes. It offers a wide range of options to support as many as possible basic and advanced operations.
We should understand how it works before we start using it.

Table of content

• Classes and data files used
• Data flow diagram
• How and when use it

Classes and data files used

• Core-Level: install/step3.php for DragonflyCMS install or upgrades
• Module-Level: admin/modules/modules.php for a module install or upgrades

• SQL handling
• includes/classes/installer.php
• includes/classes/db_check.php
• modules/example/sql/data.inc
• modules/example/sql/cpg_inst.php

Data flow diagram

During a module install or upgrades, this is basically the internal data flow:

cpg_inst.php - + - > db_check - -> installer - - > RDBMS dedicated manager
data.inc - - - ^

Its always possible, at any time, to manually inject data directly into the installer:

cpg_inst.php - -> $installer->add_query() - - > RDBMS dedicated manager

As well as bypassing all of the above tools for an immediate data transaction, useful for SELECTs:

cpg_inst.php - -> $db->sql_query()

The installer will load into memory any $installer->add_query() and execute all of them, in the same order as they are received, only after $installer->install() is called by DragonflyCMS's core. So, always remember that transactions requested with $installer->add_query() are not going to be immediately available, eg we cannot SELECT or UPDATE them until $installer->install() is executed.

How and when use it