Hi there,

I realise that DNN 4.0.1 is brand new and that the Blog probably hasn't been tested on it, however I'll post this anyway just in case it triggers any thoughts on how to fix it:

The blog ran ok on DNN 4.0.0 apart from no longer being searchable by the DNN core search. I could live with that for now.

Now after an upgrade to DNN 4.0.1 the blog generates the error below and kills off all other modules on the page. I have tested this by placing a fresh blog on it's own page and it also immediately generates the error. Other modules all seem to work fine so far.

A critical error has occurred. Field not found: 'DotNetNuke.Framework.CDefault.Title'.

Just wondering if anyone might have any ideas on this.

Regards,

Rob

hmm... line 50 of /library/components/shared/CDefault.vb is commented out:

'Public Title As String = ""

I am pretty sure the field "Title" of CDefault it used by a lot of modules to dynamically change the page title. This will break all those modules...

DNN Blog | Twitter: @erikvb | LinkedIn:

Two things.

1. The code was commented out in 4.0.1 because the base class "Page" now includes a Title property, so I am not sure why the code isn't working.  Leaving it in caused a syntax warning, which I understood to mean that the property defined in CDefault would be ignored and the base classes property would in fact be used.

2. Maybe a bigger issue, is whether it is actually good practice to manipulate the Page title.  I would suggest that for modules to "play well together" they shouldn't manipulate anything outside of their container.  Lets look at a scenario where 2 different modules on the same page both try and manipulate a Page level property - who wins?