Dear FirstSpirit community,
with the current implementation of the FirstSpirit PORTAL module project component, the following problems exist:
- when assigning/installing the module's project component to a FirstSpirit project, module ressources like:
- ActivatePortalXml.bsh (= scheduler action template)
- GeneratePortalXml.bsh (= scheduler action template)
- GUI_InstallPortalEntryPoint.xml
- GUI_InstallSubEntryPoint.xml
- pagetemplates_export.zip (= page templates)
- scripts_export.zip (= script templates)
- sectiontemplates_export.zip (= section templates)
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.
![portal_module_scripts.png portal_module_scripts.png](/t5/image/serverpage/image-id/4164iE760FF3C697802CC/image-size/large?v=v2&px=999)
![PORTAL_module.png PORTAL_module.png](/t5/image/serverpage/image-id/4165i656012297279F4CF/image-size/large?v=v2&px=999)
- 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
![portal_module_project_component_assignment.png portal_module_project_component_assignment.png](/t5/image/serverpage/image-id/4166iE954D4BF7F6F3DA0/image-size/large?v=v2&px=999)
- 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
Final result:
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.