File extensions

[brianteeman]

Do we really need to define this here. Surely we should be using the settings in the media manager and not introduce yet another place where file types are defined. We already have too many.

gsoc25_api/src/administrator/components/com_ccm/src/Helper/MigrationHelper.php

Line 142 in c51ba43

$supportedExtensions = [

[HermanPeeren]

This component is eventually meant to be able to migrate content from and to any of the CMSs that have their content model defined and mapped to our common content model. This helper function is used for any target CMS, not only Joomla (although that is not functional yet, as we aimed at WordPress to Joomla migration first). This Joomla component could eventually even be used if both source and target CMS are not Joomla. So we don't assume that the Joomla instance where this component is installed on, is also the target CMS. It is just a "host" for this application (which is most convenient when the source or target CMS is the Joomla instance on which this component runs).

BTW a nice feature is that there will also be a possibility for Joomla to Joomla migration, for instance for the defined custom fields (like we did in com_hopper) or to transfer some pieces of content from one Joomla site to another. Unfortunately not ready yet, but it is close.

[brianteeman]

then it will need to have the ability to configure the allowed extensions. But I also think this is creating security issues if you have configured the host CMS to only accept specified file types but here you are just allowing almost anything and ignore the host settings. Imagine you have already configured the host not to support gif images. When you use this code then gif images will be imported and uploaded to the host but NOT visible at all in the media manager as they are not supported.

[HermanPeeren]

Will have a look if this helper function is (still) necessary for any of those migrations via the web services API, and if it works.

This component is only used to migrate content (including users, media, etc) from one CMS to another. The user of this component must have credentials and rights for both sites and can be installed on a totally different Joomla site (even on your localhost, while the source and target CMS are online...) . Whatever that user does with the migrated content on the target CMS is not the responsibility of the migration tool.