Upgrade to mojoPortal v. 2.3.9.3 - New Internal Comment System - web.fulltrust.config

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
10/20/2012 4:14:00 AM
Gravatar
Total Posts 149
Partner
mojoPortal Skinning, Custom Development and Support in Italy?
EffectiveWeb.it

Upgrade to mojoPortal v. 2.3.9.3 - New Internal Comment System - web.fulltrust.config

I would like to share the follofwing upgrading experience and get some feedback to understand how to proceed with the upgrade to the 2.3.9.3 version.

After upgrading to mojoPortal v. 2.3.9.3, existing Blog posts generate erros when clicking on the post title.
Same problem with the new Comment Feature.
The error was apparently related to the new commenting system

[NullReferenceException: Object reference not set to an instance of an object.]
mojoPortal.Web.UI.CommentsWidget.OnInit (EventArgs e) +121

I uploaded again tall the released objects to assure that all files were included, then I noticed that the problem could be related to my version of web.config.

Usually, the package was released with web.config file set by default for Medium Trust webservers. For my full trust server I used to replace the web.config file with file web.fulltrust.config, provided with the downloaded zip file.

With release 2.3.9.3 the file web.fulltrust.config is not included therefore I accidentally changed the new web.config file with an earlier version of web.fulltrust.config (which was there since the previus upgrade). Hence reporting missing items.

Web.config file included in the 2.3.9.3 package seems already in its "FullTrust" version.

On the other hand, I noticed that file web.mediumtrust.config (to be used for Medium Trust Hosted Sites) contains the following : <add key="RunningInMediumTrust" value="false"/> which I suppost should be seto to "true".

Can anyone confirm that:

  1. the web.cobfig released with 2.3.9.3 is already the full trust version
  2. for medium trust server, after replacing web.config with web.mediumtrust.config, the <add key="RunningInMediumTrust" value="false"/> should be set to "true"

Thanks

Diego

10/20/2012 6:46:45 AM
Gravatar
Total Posts 18439

Re: Upgrade to mojoPortal v. 2.3.9.3 - New Internal Comment System - web.fulltrust.config

Hi Diego,

Regarding the error, yes it would happen if not using the new Web.config because the control references for the comment widget and some other things were added and without them errors will happen.

Yes, on the initial release I forgot to make the default web.config be the medium trust one so Web.config in the package was full trust and web.mediumtrust.config also existed.  I realized that mistake several days ago and corrected the package for MS SQL .NET 4 becuase it is required to be configured for medium trust before I can submit the update to the web app gallery.

I need to double check but I'm 99% sure that web config setting for medium trust has not been used in a long time because we found another way to detect trust level. I will look into that and remove that setting if I'm correct. The only difference these days between the full and medium trust config files is the NeatUpload settings.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.