Skip to main content

Umbraco Notifications - Save and Send For Approval Process

In Umbraco you can give different permissions to the different Umbraco users and some of these users might have rights to only create or update content nodes but not to publish them. In this case; you might need your Umbraco system to send notification e-mails to the Umbraco users who can then publish the content nodes.

To do this; you can write your own custom code by creating some event handlers or you can use built-in Umbraco notification functionality.

For the second built-in option first login to Umbraco as admin and go to User's section and update the permissions as shown below;



Once you are done with the user permissions, subscribe your Umbraco users to the content nodes, simply login to Umbraco with those users and find the content node, right click on it and select the following option;



After this you need to make changes in the web.config file of your Umbraco project. For my case I am using my test gmail account for sending e-mails. In order to use your gmail account as your SMTP server, first login to gmail and then go to Google's less secure app access page and allow less secure apps. You might need to enable account access as well by following this google link: https://accounts.google.com/DisplayUnlockCaptcha

After doing these changes on the Google's access page, now change your web.config as follows;

  <system.net>
    <mailSettings>
      <smtp from="[email protected]">
        <network host="smtp.gmail.com"
          port="587"
          userName="[email protected]"
          password="yourgmailpassword"
          enableSsl="true"/>
      </smtp>
    </mailSettings>

  </system.net>


For anonymous access SMTP servers; the Umbraco website IP address(es) must be allowed to use the SMTP server relay and below is how the web.config should be;

<smtp from="[email protected]">
        <network host="yourdomain.outbound1-uk.mailanyone.net" port="25" defaultCredentials="true" enableSsl="false" />

      </smtp>

If you want to you can also override the "from e-mail address" from umbracoSettings.config;

    <notifications>
      <!-- the email that should be used as from mail when umbraco sends a notification -->
      <email>[email protected]</email>

    </notifications>

Now after building your project/deploying your changes to your server, simply login to umbraco with your editor user and update your test content node and and hit Save and send for approval button.



Once all is setup correctly; your publishers who are subscribed to this content node's notifications, will receive an e-mail notification, similar to the following one and simply clicking the link in the e-mail they can publish the umbraco content;


That is all, hope it helps. And remember that you can subscribe your users to different actions as well.

Comments

Popular posts from this blog

How to fix Git push error: "RPC failed; curl 56 HTTP/2 stream 7 was reset send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly"

Problem Today I saw the following problem when I tried to push my changes to a Git server after doing some work for upgrading an Umbraco v7 project to v8.18.8.  Possible reasons After some investigations, it seems like this could be because of the following reasons; Git is not happy with the amount of changes that are being pushed into the server.  There are possible limitations on the server about the size/amount of files that you can push. Your internet connection is not good and stable enough. Your Git client's version is old. Solution options For me, the easiest option was connecting to another Wifi and trying again. Apparently, this option helped quite a few people, so it is worth giving it a try. Unfortunately, it didn't work for me. A bad internet connection wasn't an option for me either, as my internet is pretty fast (500 Mbps). Similarly, my Git client version was the latest version (git version 2.41.0.windows.3).  On StackOverflow, there were a lot of recommendat

How to use JQuery Ajax Methods for Async ASP.NET MVC Action Methods

Making repeatedly calls to async methods can be a nightmare. In this case, it makes sense to use 2 ajax methods, instead of one. Here is a simple solution to overcome this problem. See that  ajaxcalls   is emptied after the success response for the first ajax call and then the second ajax method is used to make one single call to the async action method. Hope it helps. View: @section Scripts{     < script type ="text/javascript">         var smartDebitObject = new Object();         smartDebitObject.MembershipNumber = $( "#MembershipNumber" ).val();         smartDebitObject.ProfileId = $( "#ProfileId" ).val();         smartDebitObject.FirstName = $( "#FirstName" ).val();         smartDebitObject.LastName = $( "#LastName" ).val();         smartDebitObject.AddressLine1 = $( "#AddressLine1" ).val();         smartDebitObject.Postcode = $( "#Postcode" ).val();         smartDebitObject

How to fix "Microsoft SQL Error SQL71564: Error validating element [USERNAME]: The element [USERNAME] has been orphaned from its login and cannot be deployed."

I needed to export a database in BACPAC format today in order to restore it somewhere else, and I encountered the following error. To resolve this issue, I deleted all of the users mentioned in the error log. After successfully creating the BACPAC file, I used it to create a new database with no problems. Error: TITLE: Microsoft SQL Server Management Studio ------------------------------ One or more unsupported elements were found in the schema used as part of a data package. Error SQL71564: Error validating element [USER1]: The element [USER1] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER2]: The element [USER2] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER3]: The element [USER3] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER4]: The element [USER4] has been orphaned from its login and cannot be deployed. Error SQL71