While Episerver contains a ton of functionality - both in the core products and via add-ons - there is always room for improvements. These are the 10 most requested missing features, as reported by the Episerver community.
Wouldn't it be convenient to export and import content directly from the page tree in Episerver?
Publishing an entity just results in "An unknown server error has occured" in the event log on your outbound connector? Verify that all CVL items have a value.
Episerver's continuous delivery policy provides tweaks and features that make editors' lives easier. Did you catch all of these?
Writing client side applications in your Episerver-solutions, and creating custom localization functionality in the front end? Why not use what Episerver already has?
Missing wildcard hostname mapping might make the inRiver connector fail when importing resources.
If you're using inRiver PIM with the Episerver connector, and upgrading the PIM system from 6.2 to 6.3, there's a breaking change you should be aware of, that could potentially make products on your page invisible.
Having two-way-relationships between content is a common scenario on the web today. Automatically linking from each end of the relationship to the other. We've composed our own, very simple module to do this - and it's now open sourced!
Many companies set up their own, internal package feeds these days, in addition to all the public ones out there. To create awesome packages, there are a few things you should keep in mind.
Simple lists of label-value-pairs on information pages often result in cluttered views. Tidy those up drastically with some simple UIHint-magic.
Integrations can boost your CMS capabilities, or become a long-term liability. To reduce the risk of bad integrations, dig a little deeper than the one-liner answers.
Integrations in CMS projects often get complicated, but customers love simplicity. So are ready-made modules the perfect answer?