will be automatically imported to the corresponding FirstSpirit project. The FirstSpirit IDs of the parent folders are stored to a configuration file names "portal_app.ini" below "<fs4_install_path>/data/projects/project_<id>/modules/FIRSTspirit PORTAL.FS PORTAL"
As we all know, that FirstSpirit IDs are not stable between ex- and imports of FirstSpirit projects, these nodes may vary. When updating the same module on a host where an imported project exist, the assignemt of the module provokes duplicates for: - scheduler action templates (see screenshot below) - template ressource where the technical reference name will be suffixed by "_1" without updating already existing ones (see screenshot below)
as the IDs do not match any more.
failed imports of resources do not provoke exceptions/errors during the project component assignment. The following screenshot shows just 3/6 script resources being imported during the installation run WITHOUT any error feedback
update process (see method "updated()") does not really update the above module-included resources but only migrates the site store
after having assigned the module's project component the nodes the content is not refreshed and only visible, when the client and also the complete server has been restarted
That's why we vote for fixing the above identified problems, especially (2). As (2) is not just PORTAL/PORTAL 2.0 related/dependent it would be a really good to offer a generic solution within the FirstSpirit core module framework.