Hello,

I have successfully installed the Shadow Module into my online DNN site (webmatrixhosting). But when I clicked on <Edit Shadow Link>, I hit this error:

Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[NullReferenceException: Object reference not set to an instance of an object.]
Webstone.EditShadow.Page_Load(Object sender, EventArgs e) +1207
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Page.ProcessRequestMain() +731


Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573


A strange thing happened: I went to my local development server and install this module in my test DNN site. I could edit the shadow link if I accessed it on my server's browser but I could not if I used my workstation.

Please help. I dont know what is wrong here. Thank you.

I'd like to help you solve this but I am confused by your tests. Could you try surfing to your online site from your local development server and see if you can use the Edit Shadow Link.

Please let me know. The fact that it works on one browser and not the other is quite odd and has me wondering if something else isn't causing your problem.

Jeremy

Also, could you give me any details on any firewall and/or virus scanning software you are running between your workstation and the online site. Norton products with privacy options enabled have cause a number of DNN problems because they block the viewstate from being passed back and forth.

Yes we do have Symantec Client Security which consists of a firewall (incl IDS) plus their corporate antivirus scanning solution. We cannot disable this unfortunately so is there any way to tweak the code or change some settings to allow this to proceed. We are able to set the firewall sys to allow certain programs or ports to go thru. Any advice?

I don't use the product myself (symantec), but I think if you disable the privicy settings on the client software it will work. I haven't looked in to this much much yet though.

This thread provides a little more detail.
http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=418250

there is a snippet of code in asp.net forums that i have used and it seems to ( usually ) work well, sometimes there is viewstate loss when clicking the back button ...

try this code from this link, and it should help you with the viewstate problem, as it stores the viewstate in session instead of in the page.

http://xpdit.com/DesktopDefault.aspx?tabid=1&BookID=7&ChapterID=25&PageID=154

In regards to Webstone.Shadow (v1.0.5 for DNN2.0)

Can anybody recommend the best method to install the latest webstone.shadow module in a DNN deployment while preserving OLD shadows? Here's what I'd like to do...I would just like confirmation that I'm on the right track - or perhaps a nudge in the right direction:

Background info:

- my DNN 1.0.10e has recently been upgraded to DNN 2.0 and everything went smoothly. (But I've had to temporarily 'recycle' my surveys and shadows)

- I have put the OLD shadow module instances into the recycle bin for the time being while JWhite had an opportunity to re-write this module for DNN2.0. In effect, I've simply removed the old shadow-ed content from my portal's pages.

- I would like to preserve the old shadows somehow...but it seems more complicated than I thought as of course the new version will have it's own moduledefinitionID and controls and even a new name it appears ("webstone.shadow")

SO: step-by-step:

a) Put all the existing 'shadows' into the recycle bin DONE

b) Backup the database of course. DONE

c) Upload the new shadow module's zip file using the DNN file manager (regular install procedure)

d) At this point...I suppose I can re-create 'instances' of shadow module (the NEW shadow module) on the desired pages (but I'd like to transfer my OLD shadows to these new instances...so, with this in mind)

e) I'd like to remove the OLD shadow module without deleting the database references to the 'shadows'. (to accomplish this, is it recommended that I delete the appropriate references in the old .uninstall file prior to actually deleting the module from DNN "Module Definitions" tab?)

f) Then can I alter the "Modules.ModuleDefID" field to reflect the NEW DefinitionID? Effectively switching the OLD instances to the NEW module?

g) then take the modules OUT of the recycle bin?

I'm using a combination of the DNN UI, and a database editor (MS Access project to be precise) -- so with access to both the raw data and the UI I think that this task is possible.

I've been trying these steps in a test environment but I'm getting errors and generally not having much luck (and 'luck' seems to be an integral part of my process at this point). Any help would be appreciated.



Regards

Hi Dave,
You should be able to do this. The fact that the dlls and folders are different make this something of an easy task I believe.

Find the old Shadow Module ModDefId and the new Shadow Module ModDefId

Then try the following script in Host->SQL:

update Modules


Set ModDefId=89 


Where ModDefId=75

In the above instance change 89 to the new ModDefId of the new Webstone.Shadow and change 75 to the ModDefId of the old Shadow module

Let me know your results and I'll try to create a better upgrade script that is more automated with the next version.

Thanks for the response!

I'm going to sleep now. But I'll get back at this tomorrow and let you know how things go.

Regards

Hello jwhite,

I gave up. sorta.

The reality is that I had only 12 shadow instances. And after reviewing the process I decided I'd save myself some time by simply UNinstalling the old shadow module, INstalling the new shadow module, then recreating each instance normally.

The problem I had was this:
- the .uninstall file in the old shadow module version will delete all references to shadow modules, including foreignkey references et al.

- but it appears that the 0.1.05.DataProvider file in the new shadow module ALSO executes each old stored procedure upon 'install'.

So, both procedures will effectively delete my shadow instances. (making it hard to 'preserve' them long enough to transfer the moduledefID)

And, while this might not pose a problem for a guru like yourself, it became rather complicated in a hurry. And in the end...for the small number of shadows I had in my portal, it was faster (for me) to avoid this trouble altogether.

Perhaps next time I'll have more success and be able to contribute more.

On a related topic:
I wonder, as the PA installer gets better, it might be a very nice addition to control the PA installer a little during the installation process. Perhaps there would be a way to build 'conditional' installation procedures so that YOU (module developer) could execute different install scripts depending depending on MY (end user) input. For example, during the install procedure, it might be handy to have an option to "Delete old records? Yes|No". Or perhaps YOU (module developer) might choose different procedures depending on whether or not a previous 'Shadow' version is in the ModuleDefinitions table. i.e. you could execute either a 'fresh install' script of the webstone.shadow OR an 'upgrade' script. But these enhancements are perhaps a long ways away and may be rendered moot depending on not-to-distant-future DNN versions.

It seems that some 'logic' and conditional behaviour in the PA installer might be a real necessity in the future as more modules are available and the need to peform 'installs', 'uninstalls', and 'upgrades', and perhaps 'imports/conversions'.

In any case, thanks for your input and again, I think your shadow module is one of the most useful modules available. It's certainly worthy of all the praise you receive.

I'm going back to my portal now. Cheers.

Dave,
This is built in now to the PA installer but I had not accounted yet for the old module as it was not built on the same installer architecture and would not have handles the update automatically.

Xpdit: Re: your link....

.... DNN 1.0.12 !? Reaaaaalllyyy???

wanna tell us about that one? ;-)