Form Caching with Admin Separation

We were tasked to create a section wrapper to add a title and legal disclaimers to a form used on multiple sites. The application I'm currently working on has one Kentico form that appears to be caching when deployed after admin separation. Saved changes are visible in preview mode, but not on the live staging site.

We have tried clearing the System Cache, but with admin separation, the cache clears the admin service, not the live site. I waited a day to check and it appears that forms have a 24 hr cache for the form added in a page builder.

Are there any plans to add a "Publish" feature for forms also?

Section (properties are text only):

@model FormSectionViewModel<TitledSectionProperties>

@if (!string.IsNullOrEmpty(Model?.Properties?.Title))
{
    <div class="ktc-section-title">
        @Html.Raw(Html.Kentico().ResolveRichText(Model.Properties.Title))
    </div>
}

<div class="row">
    <div class="col-md-12">
        @await Html.Kentico().FormZoneAsync()
    </div>
</div>

@if (!string.IsNullOrEmpty(Model?.Properties?.Disclaimer))
{
    <div class="ktc-section-disclaimer">
        @Html.Raw(Html.Kentico().ResolveRichText(Model.Properties.Disclaimer))
    </div>
}

Environment

Tags:
Deployments Environments

Answers

I haven't tested this myself, but changing a form should clear the cache keys for that object and cache change are synchronized across applications with web farm tasks. This applies to your split deployment scenario.

So, this is either a bug in the product or a web farm misconfiguration on your end.

We have several improvements to Forms tracked on our roadmap. If you are interested in something like publishing workflows for forms, share your thoughts as roadmap feedback.

Are both projects - admin and live running on one physical machine or, are those running on fully separated machines/servers?

To response this discussion, you have to login first.