Well it's been a week of challenges again getting sites to run DNN and other modules, modules that used to work and since upgrading they don't, and the feedback from developers is they have some problems tracking these things down since they can't find any specific changes to make it break to the level that some do.  I'm working on getting http://www.inkandtoneronline.com.au finished and ready for action!

An interesting error that appeared on a project I'm working on brought up this in the event log.  I had upgraded to a later version of Catalook and DNN and it went pear shaped... I thought I'd have to redo the whole site. After getting one set of errors rectified and being able to get the cart actually displaying pages, another error presented itself, which I remember had been a problem before when accidently a complete release of DNN was made available on a completely different build number and modules went awol.. it was quickly fixed and only a few hundred downloads were affected, but in the mean time, it sent some key developers into a panic as they had to recompile to match the build number.

Here's an example of one error that appeared after the others were fixed...

Indirect reference is being made to assembly DotNetNuke.WebControls version 1.5.3.20116, which contains 'CATALooK.C_TreeControl.DNNTree'. This Project references a prior version of DotNetNuke.WebControls version 1.5.2.29213. To use 'CATALooK.C_TreeControl.DNNTree', you must replace the reference to DotNetNuke.WebControls with version 1.5.3.20116 or higher.

This appears to be because on this particular instance the DNN Core is complied using the revision number on their builds they deliver the source with 4.5.1.28, whereas some developers are using 4.5.1. 

Changing the version number to display later than the current build and recompiling fixes it (so I was told since I don't write the code)

However, I also know it took quite a few hours to find out the other errors that occured since one error was hiding another.. and that is also something I learnt today - Errors can hide within themselves and not display their true identity until the others have been fixed.  Dang.. and I thought skinning was a challenge... I think I'll keep the skinning and design hat on thank you very much.

I'm not here to tell people how to code, but I do know that I've seen that error before and for the person who looks at their logs and can't work out the errors - this type of wording might give you an indication on some of the errors that appear in the log viewer - which is found under Admin/Log Viewer and handy to check and empty sometimes.

Nina Meiers