This is a great feature. Comes in handy when you need to convert your site from webform to MVC, it allows the editor to reuse the blocks, just by adding partial views (MVC renderers).
There is two way to make the IP come from the actual client instead of the CDN edge server. Here is a guide.
Episerver CMS version 10 is since October 2016 available for download, with a dozen tech breaking changes, but what news is there for editors?
Hey EPiServer World, with you in mind! Stuck with an ASP.NET WebForms-solution with no responsive layout? And the owner won’t redo all web to MVC? Then here is the simpler way to go responsive… without rebuilding all and immoderate job effort from editors… only fun work for the web developers.
In multisite scenarios or when you use optimization libraries you’ll need to set the TinyMCE editor css dynamically from the code.
I’ve experience that it can be tricky setting up content provider. Content Providers in EPiServer is a way of publishing external data as pages/blocks etc. Here is an example of an RSS Content Provider.
Sometimes you want to customize your mirrored content, in this example I can customize the url segment, setting the ACLs, and localization. And we do use Fetchdata.
Content Providers in EPiServer is a way of publishing external data as pages/blocks etc… but also a way of publishing content in several places on your web.