CMS8 Breadcrumbs

CMS8 breadcrumbs needs fixing.

If i set a page left nav to "This item only", then the breadcrumbs should mirror this.

If i set it to groups, then ditto, it should only show home, the parent and children

At present it always shows the whole shebang.

CMS8 Applications links

Its imperative to resolve the applications link paradigm - so that we can link directly to application items in their respective site or section.

The solution must take into account that some items (e.g. news) may be available on more than one site. Maybe set the application root pages in the sites section, rather than the application section?? keep the application root page info in the sites object, along with an agreed parameter schema?

CMS4 Proposal

This proposal is that the CMS4 should have an ApplicationHelper.aspx file like CMS8

CMS4 Proposal for applications

This proposal is that for applications there are three hidden fields - edit, staging and live, so that different items can be previewed in the same way as pages.

It would mean a lot of re-jigging of old projects - but would be worth it.

CMS8 Cache proposal improvement

A proposal to augment caching. Basically each application has a  cache file dependency so that when you update any data in that application the file is touched. Then say for example you have a home page widget that gets some news, a banner and some content, the resulting html can be cached, until either the banner or news widget cache is updated, then the content will be refreshed.

CMS8 Topnav changes

Its no good having ids in the top nav as then you cant have a top nav in the footer without illegal html, so its changing to classes:

This:

<li id="tnav1"><a id="tna1" href="/About-Us/">About us</a></li>
<li id="tnav2"><a id="tna2" href="/Why-Electra-Partners/">Why Electra Partners</a></li>
<li id="tnav3"><a id="tna3" href="/Investment-Strategy/">Investment Strategy</a></li>
<li id="tnav4"><a id="tna4" href="/Portfolio/">Our investments</a></li>
<li id="tnav5"><a id="tna5" href="/Our-People/">Our people</a></li>
<li id="tnav6" class="last"><a id="tna6" href="/Media-Centre/">Media centre</a></li>

will become this:

<li class="tnav1"><a class="tna1" href="/About-Us/">About us</a></li>
<li class="tnav2"><a class="tna2" href="/Why-Electra-Partners/">Why Electra Partners</a></li>
<li class="tnav3"><a class="tna3" href="/Investment-Strategy/">Investment Strategy</a></li>
<li class="tnav4"><a class="tna4" href="/Portfolio/">Our investments</a></li>
<li class="tnav5"><a class="tna5" href="/Our-People/">Our people</a></li>
<li class="tnav6" class="last"><a class="tna6" href="/Media-Centre/">Media centre</a></li>

Urmm... thats it!

CMS8 Path stuff finally sorted!

Finally reached a workable solution to the web.config pathing problem. I created a module, built into the cms8 dll that sorts out what requests will be sent to the page processor.

Usage is this:

<system.webServer>
    <modules><add name="CMS8Module" type="CMS8.CMS8Module" /></modules>
</system.webServer>

Now if the module is used all extentioned pages (e.g. .htmx) and path type pages (e.g. /about-us/) will be handled by CMS8.Requester2, with the admin section being ignored (as long as the CMS8Config.Adminsite key is set to true and the CMS8Config.ApplicationVPath key is correct). Also htm and aspx files will be ignored by the CMS8 dll.

However this means that 404 errors for .Net and non-.Net resources will need to be caught - here are the settings:

<system.web>
<customErrors mode="On"><error redirect="/404.html" statusCode="404" /></customErrors>
</system.web>

<system.webServer>
<httpErrors errorMode="Custom">
<remove statusCode="404" subStatusCode="-1" />
<error statusCode="404" prefixLanguageFilePath="" path="/404.html" responseMode="ExecuteURL" />
</httpErrors>
</system.webServer>

The "publish 404" function now creates a 404.html as well as the 404.inc files

So in total RequestHandler  can still be used, this silently redirects "/about-us.htmx" pages to "/about-us/" pages WITHOUT 301. Requester will silently redirect in the same way WITH a 301 redirect.#

Requester2 does not do the Page_PreInit to check for "Sitemap.xml" or "robots.txt" and also does not do the redirects for "/about-us.htmx" pages to "/about-us/" pages.

The way forward is the Module + Requester2 way.