uvdesk / community-skeleton

UVdesk Opensource Community Helpdesk Project built for all to make a Full Ticketing Support System along with many more other features.
https://www.uvdesk.com
Open Software License 3.0
9.17k stars 464 forks source link

Issue with Email Settings Page #351

Closed WaffleThief123 closed 3 years ago

WaffleThief123 commented 3 years ago

Bug report

Title

Issue with Email Settings Page

Issue Description

When setting up the email accounts, it appears to not accept .cloud as a valid TLD

Steps to reproduce

1. Go to SwiftMail Settings
2. Fill Out Form with a .cloud TLD
3. hit Save 
4. recieve error:

image

Expected result

Accepts settings as valid and tests them

Actual result

Doesnt save and errors.

papnoisanjeev commented 3 years ago

@WaffleThief123

As on Swiftmailer page a email pattern regex check enabled so may be it is not allowing you to add your custom email(.cloud). We have updated the regex here as it is updated in master and will work from next release but you can use it by change this line in your manageConfigurations.html.twig(under vendor/uvdesk/core-framework/Resources/views/SwiftMailer) and make a try.

If Above solution does not work then you can add any other email from front end and change it from swiftmailer.yaml (under config/packages of your project).

WaffleThief123 commented 3 years ago

Awesome, thanks guys gals and nonbinary pals that work on this. Y'all are rad. You can close this out as I view the issue as solved.

WaffleThief123 commented 3 years ago

Asking to reopen due to this only being fixed there, but it also applies to the customer create and agent create fields. I'm gonna update it locally and see if it fixes it to confirm

WaffleThief123 commented 3 years ago

Confirmed, setting this line to be identical to line 251 herein does fix it.

papnoisanjeev commented 3 years ago

@WaffleThief123

Please describe problem you are facing and when.

WaffleThief123 commented 3 years ago

@papnoisanjeev it was the same problem that i referenced when creating this ticket, except on the Add Agent page. I referenced a fix in this comment.