Episerver Forms: Avoiding spam with a honeypot
Spam comes in many forms and can be really annoying. Often, when you put a form on your website it will be found by spam bots that will post lots of spam in the form. A common defense is CAPTCHA's, but they are annoying the real users and typically not WCAG compliant. Here, I'm showing a simple Episerver implementation of another approach that works wonders for me - the honeypot.
Showing the right block types at the right time
Often, it can be handy to have very exact and dynamic control over what editors can see or do. One of my weapons of choice for this is the good, old and trusted Virtual Roles. In this scenario we have a multi-site Episerver, where some of the block types it should only be possible to use on one of the sites.
Enrich Episerver Forms with additional system fields
Episerver forms adds a couple of system columns to each form submission when you export the submissions. But it happens that the people that need the form submission reports want additional data - for example the url of the page the form was on - and for some reason they don't know all Episerver page Guids by heart.
Exploring the Episerver Nuget Feed
The best thing about Episerver is the community and all the great contributions coming from it. Many of them make it into packages on the Episerver nuget feed - along side Episervers own packages. I have for a long time worked on building tools to explore and visualize this more - and now I'm finally ready to one-by-one share some of the tools coming out of it.
Using Episerver Forms to book meetings in Outlook with Microsoft Power Automate
It's not as hard as you might think - and doesn't require any code - to connect your Episerver Forms with hundreds of other systems, using services like Microsoft Power Automate (formerly Flow), Azure Logic Apps, IFTTT or Zapier. I made a 5 minute video, showing how you can let your visitors request a meeting on a given date from a form on your website, and then having it being automatically booked in your Outlook 365 calendar.
Attribute to set XHTML property settings in Episerver
A pretty normal task is to have an XHTML property that uses only a very specific subset of the normal TinyMCE functionality. For example a text field that also allows the editors to create links - but nothing else. I came up with what I think is an elegant solution here.
Powerslice: Identify unused blocks
Powerslice might have a few years on it's back, but it's still a great editorial tool, when you are working with large amounts of content and have access to Episerver Find. Here's an example of a recent slice I made that let's editors easily identify unused blocks.