customizing devise flash message after sign up - devise

I would like to show appropriate flash message to the user after he signs up.
My app is configured so that user is logged in automatically after the registration, but he has to confirm the email (he can be logged in for 5 days without confirming the email).
With my current configuration, devise will display the following flash message to the user:
Welcome! You have signed up successfully.
I would like to tell them that they have to confirm the email:
Welcome.. You have signed up successfully. Please confirm your email address by clicking the link..
As I see, this message is already defined in the locales/devise.en.yml with the signed_up_but_unconfirmed but why its not showing up with my configuration?
How should I fix this?
Thanks for help

If you have enabled devise's confirmable module in your user model, after registration the user should be seeing the default text:
"A message with a confirmation link has been sent to your email address. Please open the link to activate your account."
The message above as defined in the devise.en.yml file with the key en:devise:registrations:signed_up_but_unconfirmed

Related

Mail Message not authenticated from CPANEL

pls i tried implementing the PHP mailer library with using my webmail credentials, but on delivering to the clients(Gmail) it displayed a yellow warning alert indicating the google couldn't cerify of the message is actually from the Domain, stating the message isn't authenticated, Ive tried various solutions online but all to no avail and also the DKIM and SPF configuration indicated that they are all valid, Pls how do i fix this
I've tried to configure the DKIM and SPF but it has already been configured by my network provide(Host), stil the message still displays the yellow warning sign that the mail is not authenticated

"Send With DocuSign" URL Button Works In Sandbox But Not Production

An APEX email error is received when trying to utilize the "Send With DocuSign" URL button on the contract object in Salesforce. This button was just created to meet the requirements to move from a JavaScript button. The button does not trigger an error in Sandbox, works as expected. But I can not replicate in production without getting the error shown below. Any idea on how to get this resolved?
Developer script exception from Franklin Madison Group : DocuSignAPICredentials : Please verify that you have been granted access to DocuSign, your account settings are correct and that you have responded to all activation emails.
Apex script unhandled exception by user/organization: 0053n000007GFbq/00D70000000Je65
Visualforce Page: /apex/dsfs__docusign_editenvelope
caused by: dsfs.UnauthorizedException: Please verify that you have been granted access to DocuSign, your account settings are correct and that you have responded to all activation emails.
Class.dsfs.DocuSignAPICredentials.getInstance: line 71, column 1
Class.dsfs.DocuSignAPICredentials.getInstance: line 56, column 1
Class.dsfs.AccountFeatures.getInstance: line 139, column 1
Class.dsfs.EnvelopeController.loadEnvelope: line 164, column 1
Cause
Common causes for the issue are listed below,
The DocuSign user associated with the Salesforce user sending the envelope is not active
The Salesforce user has not been added to the DocuSign users list in DocuSign Setup settings (in Salesforce)
You are attempting to use Salesforce Login Access on behalf of a user "not yet Authorized DocuSign eSignature for Salesforce (DAL)"
Note: If the user hasn't authorized already, please refer to Step 4 in this article
Solution
Before continuing, ensure that you are on the most recent version of DocuSign eSignature for Salesforce (DAL). If you are on an outdated version, some of these steps will be unavailable.
To resolve this error, you’ll need to verify both issues that cause this error has been addressed.
First, you’ll need to verify that this Salesforce user has been added to DocuSign.
To verify if a Salesforce user has been added properly:
Navigate to DocuSign Setup.
Select User Management, then select Add User.
Enter the name of the user in the Value box. When they appear in the search results, select the checkbox next to their name and select Continue.
Assign the appropriate permissions to the user and select Apply. If your package is up to date and a DocuSign user already exists for this user, the Salesforce user will be mapped to their existing DocuSign user.
Click Done to finish.
Second, verify that the DocuSign user associated with this Salesforce account is active.
To check if a user is active in DocuSign:
Navigate to the DocuSign web app and select Settings.
Navigate to Users and search for the user in question.
If the user is not active, select Actions > Resend Invitation to send the invite to the user again.
To activate a user:
The User will need to navigate to their email client and open the invitation email.
Click the link in the email to activate.
Create a password and security question.
Once the user is active, have the user attempt to send an envelope from Salesforce to confirm the issue is resolved.
Additional Troubleshooting
If the DAL Admin and all users are noticing the same error, try to disconnect and reconnect.
Steps to Disconnect [Note: Disconnecting accounts will remove the DocuSign Gen and DocuSign Negotiate permissions for the Salesforce users that were given access under the old connection. You have to re-add DocuSign users and permissions in your organization.]
Steps to Reconnect
If the Salesforce Administrator attempting to make this change is unable to access the DocuSign Setup object, ensure that they have the correct permission set assignment to access the object.
To view permission set assignments in Salesforce:
Navigate to Setup, select Users.
Navigate to the user in question and open their profile.
Navigate to Permission Set Assignments, if the DocuSign permissions are missing, edit the section and add DocuSign Administrator.
Note: If you are running both DocuSign Apps Launcher and legacy DocuSign eSignature for Salesforce, you will see duplicate permission sets with similar names. Add both to ensure correct permissions are applied to the user.
Retest to see if the user can access DocuSign Setup. If it’s still failing, follow the steps in this article to navigate to the DocuSign Troubleshooting page and select Delete DocuSign Credentials. You should then be able to navigate to DocuSign Setup and reestablish the connection between DocuSign and Salesforce.

Keyrock enabling two factor authentication

I am trying register a user in my keyrock installed on my own computer.
I put localhost:8000/ in firefox, and it redirects me to fiwareLab. But when I want to sing up a user, everything is ok, but then, when I guess that I have to confirm the account, the page show me "Activation key invalid" and in my console, the computer show me
enter image description here
So, I think that I have to enable the two factor authentication, but I don't know.
Could you help me, please?
Thank you so much.
To create a new user, you have to do the following steps:
In the IdM Horizon login screen, instead of put username, password and click sign in, just click on Sign up link or use idm_ip:8000/sign_up/ directly on your browser. After that, type information about the new user (username, email and password), check the I accept FIWARE... box and click Sign Up button.
Now, out of the container, see the log through:
docker logs <container_name>
There, you will see, in the last lines of the log, the activation link that was supposed to be sent to the new user's email. Copy it, paste on your browser and modify the fiware-lab host on the url specifying your IdM Keyrock address. This way, your new user will be activated through the passed code.
I hope this can help you.

Creating the Custom Verified Email Page URL & Custom Reset Password Page URL

Using Back&, I'm working on creating the "Custom Verified Email Page" & the "Custom Reset Password Page" to work with my app so that users can verify emails at signup and request password resets via email.
Does anyone have an example of what these pages should be doing? I know the URL receives a token for the transaction but what are we suppose to be doing with it?
Thank you.
You don't have to do anything with it (look under security -> security acctions -> newUserVarification. Backand handles all of it for you. Make sure you specify a Custom Registration Page URL and the Custom Verified Email Page URL. If you don't have the registration url, the link in the email to confirm you as a new user will always send you to a blank page that reads, "SignUp redirect url was not supplied in configuration".

WHMCS not sending the cpanel details to clients

I am a newbie for whmcs. I have configure all the necessary configuration in whmcs and my whm/cpanel are also connected with whmcs. I have tested, it shows successful message to me. But my clients getting the welcome mail, order confirmation mail and invoice mail except cpanel details.
Please suggest me what to do?
Thanks in advance.
Make sure that you have severs configured in 'Setup' > 'Products/Services' > Severs and check that your client is assigned to the server in their hosting product
It could be due to error(s) in the service welcome email template.
At the admin area, go to that specific user services and at the footer, click on "Resend Product Welcome Email" .
You will be redirected to the sent emails log for that client.
If it did not send, check Utilities > Logs > Activity Log .
If you wish to send the email manually, go to Orders->List All Orders and then click on the ID of the order for which you want to send the email. Make sure you are on the Products/Services tab. Scroll to the very bottom of the page where you see Send Message. Select Hosting Account Welcome Email from the drop-down and click on send message.
If the email template contains an error, you will be told after the page refreshes. If not, you will see a success notification. This at least tells you that your automatic email error isn't coming from the email template. It also helps you send the email automatically while researching for a solution to automate the process.