Txs Nicholas,
1. "partial" migration
Yes I know it is weird. Now that those 2 big websites are migrated I don't want to restart those migrations from scratch :D
But at my next migration I will investigate this further and leave both the old "Akeeba for J3" and the new "Akeeba for JoomlaTM for J4" active so that we can check this in real conditions
2. export/import
I rarely export/import. I already imported at least once successfully in the past with "Akeeba for J3" since it is how I configured in the past all my sites with an Amazon S3 profile.
But I have just checked the following :
- on a J3 website > Profile > export : I get a popup proposing me to download the json file
- on a J5 website (same host, similar server) > Profile > export : the json directly opens in the browser itself the following URL
/administrator/index.php?option=com_akeebabackup&task=Profile.export&id=5&format=json&0f9bca63da887470d50be7346cf14cd2=1
Does that ring any bell?
From there, 2 scenarios (I have gone through it again this morning to clarify)
- when I was using Chrome, I was seeing the json in the browser and I had copied it to a newly created json file. But when importing that I would get ""Invalid file. This doesn't look like an exported profile .json file."
- but right now, I have tested with Firefox... and Firefox has a nice "Save" button at the top of the JSON within the browser. If I save from there and import the json file, then the import works
Si in summary, the json is correctly generated. The only issue is that for some reason it does not trigger a download but it simply displays within the browser.