<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by jczopek.dev blog</title><link href="http://world.optimizely.com" /><updated>2020-12-10T23:00:00.0000000Z</updated><id>https://world.optimizely.com/blogs/jczopek-dev-blog/</id> <generator uri="http://world.optimizely.com" version="2.0">Optimizely World</generator> <entry><title>Move blocks from page assets without Delete permission</title><link href="https://jczopek.dev/post/episerver-move-blocks-from-page-assets/" /><id>Probably almost any EPiserver user knows that to move blocks between folders in EPiserver you need to able to delete items from the source folder. And it&amp;rsquo;s fine for most of the time and we don&amp;rsquo;t think too much about it. Until we run into an issue, of course. Things can get tricky when we are faced with some specific requirements, which do not fit into the out-of-the-box capabilities of EPiserver.</id><updated>2020-12-10T23:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiserver &amp; Powerpaste postprocessing</title><link href="https://jczopek.dev/post/episerver-powerpaste-postprocessing/" /><id>One of the most important pieces of EPiserver for content editing is the support for rich text. EPiserver integrates with one of the most popular and well known rich text editors for web browsers - TinyMCE. Out of the box TinyMCE is packed with features and configuration options and its ecosystem is packed with plugins (both free and paid), that can greatly expand its capabilities.
I have recently been asked to add support for PowerPaste plugin for the TinyMCE editor in EPiserver.</id><updated>2020-11-23T00:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Unable to initialize/update EPiserver database with user sercrets enabled</title><link href="https://jczopek.dev/post/episerver-user-secrets/" /><id>I suppose all of you know the importance of not storing secrets for connections to databaes, APIs, identity providers etc. in the repositories alongiside with the code. There are many ways to keep them away from the source code in .NET Core and in .NET Framework.
In order to avoid storing secrets in code I decided to leverage user secrets feature in my current project (provided by Microsoft.Configuration.ConfigurationBuilders.UserSecrets NuGet package). However, there is an issue when upgrading/initalizing Episerver database using Initialize-EPiDatabase and Update-EPiDatabase in Visual Studio Package Manager when UserSecrets package is referenced.</id><updated>2020-11-23T00:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry></feed>