Hi,

Originally all of the features supported using the cache but over time as more ajax was used in features caching became inappropriate for those features that use ajax and do ajax postbacks. My intention is to extend the feature definitions to add a property indicating whether they are cacheable so I can show or hide the cache settings accordingly. But for the short term I have hid the cache setting on feature instances by default because most users should not use caching at all.

The Html content feature does support caching and you can enable it so you will see the cache setting on the General tab under feature instance settings (ie the gear icon next to the title of a feature instance). Just add this to Web.config (or ideally user.config)

<add key="DisableContentCache" value="false" />

Then you will see the cache setting appear. For features that do ajax postbacks like the blog, feed manager, polls, and others, I recommend you leave the cache time as 0 which means no cache. For the html feature it is perfectly fine to use it and set whatever cache value you like.

The reason I say most users should not use the cache at all even for features like html which can use it, is because most users (I think) are using mojoPortal in shared hosting, often very cheap shared hosting with very little ram and in these environments you shouldnot try to use cache because it consumes memory. If you have very little memory and you try to use caching you end up exhausting the memory which forces frequent recycling of the application causing bad performance.

Hope it helps,

Joe