Email template text

willy Lafort

Member
Mar 5, 2017
30
1
8
65
Hell;
Where are the email template text is located, I'd like to edit password reset and missing call text to a different one..
Thank You..
I've checked (app/email_templates/email_template_edit.php), but looks like the wording is different from what is sent out by fspbx
 
Last edited:
For now they are stored here:

/var/www/fspbx/resources/views/emails

This will change soon. There have been a lot of requests to make this simpler.
 
  • Like
Reactions: yaboc
@willy Lafort Heads up, version 1.9.6 now includes a brand new Email Template page where you can create a copy and override any default templates.
This is a breaking change. Because templates under /var/www/fspbx/resources/views/emails will no longer be used.

You will need to
Code:
git stash
your template changes before the update and apply them using the new Email Template page. Navigate to Advanced-> Email Templates

If you land on the old page, log out and log back in. The menu is cached and gets rebuilt during login.
 
@willy Lafort Heads up, version 1.9.6 now includes a brand new Email Template page where you can create a copy and override any default templates.
This is a breaking change. Because templates under /var/www/fspbx/resources/views/emails will no longer be used.

You will need to
Code:
git stash
your template changes before the update and apply them using the new Email Template page. Navigate to Advanced-> Email Templates

If you land on the old page, log out and log back in. The menu is cached and gets rebuilt during login.
thanks for this great update @pbxgeek

i updated my HA cluster to 1.9.6. When I create custom template on serverA it gets replicated on serverB. However when i delete it on serverB it doesn't get deleted on ServerA. When i create template on serverB it doesn't get replicated on serverA. i've tested extension name changes and those update both ways.
 
@yaboc, that means you might have an issue with database replication. Our update guide specifically outlines how to perform updates and database migrations for redundant servers. You might have missed a step. Postgres log can confirm that