[Revo] - what files are loaded in server when installing an addon?

Hi! What are the files that are loaded in the server when installing an addon?

Surely the ones in core/packages. And then?

Thank you

The package contents are usually installed under /core/components and /assets/components but the packager can change these if needed, depends on how the addon is actually packaged.

Quote from: shamblett at Mar 09, 2011, 08:20 AM

The package contents are usually installed under /core/components and /assets/components but the packager can change these if needed, depends on how the addon is actually packaged.

Thank you, and how can I know for a specific addon? Can I find that info somewhere? For example, I’m interested in Gallery, that is always giving problems for some reason.

You can follow the transcript as it installs (copy and paste it before you click ’ok’ when it’s finished installing). Most, if not all, of what the package installation is doing as regards DB modifications, file writes etc is recorded there.

Quote from: odeclas at Mar 09, 2011, 08:33 AM

You can follow the transcript as it installs (copy and paste it before you click ’ok’ when it’s finished installing). Most, if not all, of what the package installation is doing as regards DB modifications, file writes etc is recorded there.

Not too much.. This is gallery: db OK, but not much about files in server..

----

/*
* MODx Console Output
*
* @date 2011-03-09 08:56:56
*/
Grabbing package workspace...
Attempting to install package with signature: gallery-1.0.2-rc2
Package found...now preparing to install.
Workspace environment initiated, now installing package...


Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array
(
[key] => xhtml_urls
)



Created table `modx_gallery_albums`
SQL: CREATE TABLE `modx_gallery_albums` (`id` INTEGER unsigned NOT NULL AUTO_INCREMENT,`parent` INT(10) unsigned NOT NULL DEFAULT ’0’,`name` VARCHAR(255) NOT NULL DEFAULT ’’,`description` TEXT NOT NULL,`createdon` DATETIME NULL,`createdby` INT(10) unsigned NOT NULL DEFAULT ’0’,`rank` INT(10) unsigned NOT NULL DEFAULT ’0’,`active` TINYINT(1) unsigned NOT NULL DEFAULT ’0’,`prominent` TINYINT(1) unsigned NOT NULL DEFAULT ’0’,`watermark` VARCHAR(255) NOT NULL DEFAULT ’’, PRIMARY KEY (`id`), INDEX `parent` (`parent`), INDEX `name` (`name`), INDEX `createdby` (`createdby`)) ENGINE=MyISAM

Created table `modx_gallery_items`
SQL: CREATE TABLE `modx_gallery_items` (`id` INTEGER unsigned NOT NULL AUTO_INCREMENT,`name` VARCHAR(100) NOT NULL DEFAULT ’’,`filename` VARCHAR(255) NOT NULL DEFAULT ’’,`description` TEXT NOT NULL,`mediatype` VARCHAR(40) NOT NULL DEFAULT ’image’,`createdon` DATETIME NULL,`createdby` INT(10) unsigned NOT NULL DEFAULT ’0’,`active` TINYINT(1) unsigned NOT NULL DEFAULT ’0’,`duration` VARCHAR(40) NOT NULL DEFAULT ’’,`streamer` TEXT NOT NULL,`watermark_pos` VARCHAR(10) NOT NULL DEFAULT ’tl’, PRIMARY KEY (`id`), INDEX `createdby` (`createdby`)) ENGINE=MyISAM

Created table `modx_gallery_album_items`
SQL: CREATE TABLE `modx_gallery_album_items` (`id` INTEGER unsigned NOT NULL AUTO_INCREMENT,`item` INT(10) unsigned NOT NULL DEFAULT ’0’,`album` INT(10) unsigned NOT NULL DEFAULT ’0’,`rank` INT(10) unsigned NOT NULL DEFAULT ’0’, PRIMARY KEY (`id`), INDEX `item` (`item`), INDEX `album` (`album`)) ENGINE=MyISAM

Created table `modx_gallery_album_contexts`
SQL: CREATE TABLE `modx_gallery_album_contexts` (`id` INTEGER unsigned NOT NULL AUTO_INCREMENT,`album` INT(10) unsigned NOT NULL DEFAULT ’0’,`context_key` VARCHAR(100) NOT NULL DEFAULT ’web’, PRIMARY KEY (`id`), INDEX `album` (`album`), INDEX `context_key` (`context_key`)) ENGINE=MyISAM

Created table `modx_gallery_tags`
SQL: CREATE TABLE `modx_gallery_tags` (`id` INTEGER unsigned NOT NULL AUTO_INCREMENT,`item` INT(10) unsigned NOT NULL DEFAULT ’0’,`tag` VARCHAR(255) NOT NULL DEFAULT ’’, PRIMARY KEY (`id`), INDEX `item` (`item`), INDEX `tag` (`tag`)) ENGINE=MyISAM

Successfully installed package gallery-1.0.2-rc2



/* EOF */

Ok - to my untutored eye, to check all the files are where they’re supposed to be:

1. Download a local copy of Gallery package and unzip it (or look in /your-modx-site/core/packages/gallery-VERSION-NUMBER)
2. Navigate down to modCategory
3. Navigate down to whatever folder name is underneath that
4. In this folder you should see one folder ’0’ and one folder ’1’
4.1 I’m assuming that folder ’0’ should correspond to what goes into /assets/components/gallery
4.2 I’m assuming that folder ’1’ should correspond to what goes into /core/components/gallery


So you have that way of checking for physical files.

:) Thank you