[NanoCaiordo]

Reverse Engineering database structure to ... DragonflyCMS installer compatible file!

Developers may use this new function found in admin -> database to port their module tables structure to DragonflyCMS installer file format.

Will save a copy into the cache folder, just copy and paste into cpg_inst.php.

The module installer is also reworked again and work is still in progress.

preview: dragonflycms.org/cvs/h....php?v=1.2


By enabling pre_ and post_ functions they will be executed, when? function name is auto explanatory

[layingback]

Sounds good. Been waiting for this. But will it be able to handle updates for existing users? Ie.
if ($prev_version <= '3.3.1.1') {
stuff

[NanoCaiordo]

The new installer makes thinks a bit harder when you need to create the database structure using the new (4 years old) standards.
This is why I've just created this tool. Help me and everyone else to get started.

It will be supported inside inside each function ... but lets the fun start.
Possibilities are infinite and explain them all will take a while.

You or anyone else with a question, shoot me a detailed example about a process you may want to run inside an upgrade and I will show you, luckily, how simple its going to be when using the new installer structure.

Otherwise I'll be aware about issues before it's too late

[greenday2k]

mmm multistage installer, interesting but where is the "install" function ? ;D
what the "install" function does?

Or the install process is just pre and post functions?
are those functions only to be used to send and receive data from the database?
o let create interaction with the user?

Code:

function pre_install() {

        // get data of the site:
        // Let the user choose some installing options
        $response = 'Welcome '.$sitename;
        $response = 'Please choose a name for your module';
        return true;

    }


   function post_install() {

        // fill the database?
        // activate the module?
        // delete temporal tables / data ?  
        return true;

    }

[NanoCaiordo]

The install is fully automated, just provide a $tables structure within cpg_inst or in a data.inc file inside the same directory and the installer will load and install it for you.

pre_ and post_ are ran respectively before and after the installer creates tables and insert data .. same for upgrade and uninstall. Just optional functions.

Interactive? No.
However module name can be changed easily by renaming the folder, the class name and $this->modname to have a uniform name displayed everywhere.

Some more details:
If you add a new column, a new key, a new table ... you will not need to do anything else then update $tables and change $this->version to a higher version number.

That is it, installer will then see an different version, prompt for the upgrade and perform all operation necessary to match your provided $tables with the actual database table ... compatible with MySQL and PostgreSQL.

[layingback]

What version did this first appear? Ie. at what version can we drop the old way?

Can I have 2 installers? I want to switch to the new system - I hate messing with the installer - but what about my users who are on 9.1.2.1 or even 9.0.6.1 - how should I handle those?

[NanoCaiordo]

Been used from DragonflyCMS 9.1.0.1.

No, only one single installer.

9.0.6.1 they should really upgrade.
I personally managed to upgrades 8.x websites, some had issues due mod and hacks and user errors and ... improving the installer.

For example the user delete hack screwed up otherwise easy upgrades, had to modify the installer again.

[NanoCaiordo]

Now admin cache support viewing and deleting installer type cached files.