[SOLVED] Updating OTP Session template not working, instead email verification template.....

I have self hosted with v1.7.4, while updating OTP Session template, verification template is being updated, earlier there was an issue with variables but not it is not at all updating.

What do you mean by not updating at all?

On updating the Email OTP Template, it is notifying that Email verification template has been updated successfully. Changes reflect in both the templates, regardless of which I update, but the email verification is only sent with the changes. Email OTP is received with the default one only.

They both are updating regardless of which one I change, that means verification one gets updated by updating otp one. But the OTP is received with default template only.

Interesting. Create a GitHub issue for this. I think that's not the only bugged template. Others are too

Strange, I just checked, I was trying to work with verification and OTP ones only.

The session alert is the other one that's broken if I'm not wrong

All are broken

They all are showing Email Verification and updating that only

No

Yes, I am confused now 🤔

All of them are getting updated with same message

What do you mean? Can you send an example of the result/issue?

See, any template you update will update all of them with a message that email verification is updated

That is what I am getting

Weird. Maybe it's an issue of the newest version 🤔

Yes, recently self hosted

I raised an issue and it was closed stating it has been fixed, it might be available with the next release, any idea when it is planned?

Yes, in cloud, probably next week or when they plan the next deployment. For self-hosting, probably a bit longer

<@462046107556511744> , sorry for directly mentioning you but I needed to know this "Issue with default Auth Email Templates" resolution availability timeline for self-hosted. It seems to be resolved by https://github.com/appwrite/console/pull/1940 but when will it be available?

I am still curious as to why this issue is still there in self-hosted but not in cloud

Cloud is ahead of self hosted

why can't we atleast resolve these bugs for self-hosted if they are not there with cloud, it's a request for the things that are needed like this, not everything

anyways, what would be the tentative timeline for this issue to be resolved for self-hosted?

Feel free to modify the code to fix the problem.

Otherwise, we would need to test the self hosted build before releasing and that takes time.

TBD on when as we haven't had the time to create the release and test

okay but the versions are same for both cloud and self-hosted, and if it is fine in cloud, why is the issue there in self-hosted, I am sorry I am asking too many questions

And for the problem fixing, I am still a learner but surely would do so once I get there