Closed mooreds closed 5 months ago
@mooreds the templates where named according to the Name field used in the default deployment. There is no other correlation by side the name.
As mentioned in https://github.com/FusionAuth/fusionauth-site/pull/2758#issuecomment-1878798655 to use/understand the files it would require something like a JSON file to understand which File, Name, From Email, Default from Name, and Default Subject correlates.
Hmmm. I don't want to deal with a mapping JSON file right now, and don't want to change the default template names in the app.
How about we just use the names of the templates as above, even if they differ slightly from the Name field? They're pretty close.
Yes, the earlier comment was more to make sure it is clear that the names will be disconnected from the names used in the UI. My plan was to rename them according to your issue and create a PR. And once completed look in to node cli and come up with a suggestion with the slightly different names.
As part of https://github.com/FusionAuth/fusionauth-site/pull/2758, we have all the default template files.
As part of https://github.com/FusionAuth/fusionauth-issues/issues/2609 we are going to copy them over from the application code on release.
However, the files in fusionauth-site don't match up with the files in the application.
Here are the differences. These are the file names in the application:
Please update fusionauth-site to read from the correct filename, as well as the template list accessible by wget -i.
For instance, update everything to read from
two-factor-remove.txt.ftl
rather thantwo-factor-authentication-method-removed.txt.ftl