Ian Robinson wrote:
If the rest are set to true, you can certainly set that one to true as well - that will enable the composite functionality for that region. But if that line is already there in your web.config, then your symptoms probably aren't from the issue I described.
Do you see any JS errors or any other errors (404s, etc) on the page?
I have no JS errors and have the following set in my webconfig:
<clientDependency version="54" fileDependencyExtensions=".js,.css">
<fileRegistration defaultProvider="LoaderControlProvider">
<providers>
<add name="DnnBodyProvider" type="DotNetNuke.Web.Client.Providers.DnnBodyProvider, DotNetNuke.Web.Client" enableCompositeFiles="false" />
<add name="DnnFormBottomProvider" type="DotNetNuke.Web.Client.Providers.DnnFormBottomProvider, DotNetNuke.Web.Client" enableCompositeFiles="false" />
<add name="PageHeaderProvider" type="ClientDependency.Core.FileRegistration.Providers.PageHeaderProvider, ClientDependency.Core" enableCompositeFiles="false" />
<add name="LazyLoadProvider" type="ClientDependency.Core.FileRegistration.Providers.LazyLoadProvider, ClientDependency.Core" enableCompositeFiles="false" />
<add name="LoaderControlProvider" type="ClientDependency.Core.FileRegistration.Providers.LoaderControlProvider, ClientDependency.Core" enableCompositeFiles="false" />
<add name="DnnPageHeaderProvider" type="DotNetNuke.Web.Client.Providers.DnnPageHeaderProvider, DotNetNuke.Web.Client" enableCompositeFiles="true" />
</providers>
</fileRegistration>
Keep in mind that not all of my Manage buttons (dnnActionMenuTag) are affected... about 80% cannot be selected. There are ones here and there that are selectable.
Anyone else experiencing these symptoms?