Form wizard pro

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

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.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
8/28/2014 9:37:48 AM
Gravatar
Total Posts 18439

Re: Form wizard pro

can you try adding this in Web.config inside the <pages><tagMapping>

<add tagType="System.Web.UI.ScriptManager" mappedTagType="AjaxControlToolkit.ToolkitScriptManager" />

and see if that solves it or not?

8/28/2014 10:11:33 AM
Gravatar
Total Posts 118

Re: Form wizard pro

I added 


<add tagType="System.Web.UI.ScriptManager" mappedTagType="AjaxControlToolkit.ToolkitScriptManager" />

right before </tagMapping> and the whole site was unavailable with the following error.

 

Request timed out.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Request timed out.

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:
 

[HttpException (0x80004005): Request timed out.]


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1022 

8/28/2014 10:21:58 AM
Gravatar
Total Posts 18439

Re: Form wizard pro

a request timeout can happen for a lot of reasons after config changes, I would try again and refresh if it times out to give it another chance in case it just timed out waiting for jit compilation to finish.

8/28/2014 10:57:01 AM
Gravatar
Total Posts 118

Re: Form wizard pro

Just noticed something else quite strange. My Admin account's root for uploading files is now the media folder? so I can't access anything before it from the front end. Is this a setting in web.config?

8/28/2014 11:02:11 AM
Gravatar
Total Posts 118

Re: Form wizard pro

Tried adding that code to the web.config file again, it refreshed the homepage this time, but when I tried to access a page with the form on, it errored.

8/28/2014 11:03:37 AM
Gravatar
Total Posts 18439

Re: Form wizard pro

yes the default for that changed, you can change it back:

<add key="ForceAdminsToUseMediaFolder" value="false" />

but you should know why we changed it before you decide if you want to do that.

when we implemented drag and drop for images with automatic upload of the images to the server, it will put those files in the root level folder that the user has access to, for non admin users this is the media folder, but for admins if you drop images it will go in /Data/Sites/[SiteID] folder

so we changed by default to make admins also use media folder, but you can choose not to. If you upload the old fashioned way you can choose where to put the file but if you just drop them into content they will go in your root folder that you can access.

8/28/2014 11:06:56 AM
Gravatar
Total Posts 18439

Re: Form wizard pro

"Tried adding that code to the web.config file again, it refreshed the homepage this time, but when I tried to access a page with the form on, it errored."

ok, better back that out then.

I'm starting to think that the server must have a different version of ajaxcontroltoolkit installed in the GAC and somehow it is using that instead of the one in in the bin folder which is the correct version.

I really wish you could move this installation to .NET 4.5

8/29/2014 2:38:52 AM
Gravatar
Total Posts 118

Re: Form wizard pro

Can I check in the folder to see which version of AJAX I have I'll try to get upgraded to .net 4.5 but will take a bit of time, will that solve it?

8/29/2014 6:48:23 AM
Gravatar
Total Posts 18439

Re: Form wizard pro

The thing is your error says:

"The requested script resource 'Common.Common.js' requires version 'AjaxControlToolkit, Version=4.1.7.123"

and 4.1.7.123 is the version of AjaxControlToolkit.dll that is in your bin folder (or it should be since that is what is in the package)

so the question is how or why is it using a different version, and one theory is that there could be a different version of it in GAC (global assembly cache) on the server and somehow it is using that one instead of the one in the bin folder. This is just a theory about how this error can happen since I am not able to produce the error myself.  You could ask the host to look under Add/Remove Programs to see if it does have AjaxControlToolkit in the GAC on the server.

mojoportal and other features  like Form Wizard Pro do reference version 4.1.7.123 and it does exist in the bin folder, so it should use the one in the bin and it should not produce an error, so I'm just guessing at a scenario that could cause this error. I tried yesterday using the .NET 4 version of the dlls for mojoPortal and Form Wizard and was not able to get this error to happen.

The other thing to consider is whether you are really sure what version of .NET is installed on the server. It is actually not easy to find out without looking in Add/Remove Programs because .NET 4.5 is really an in place upgrade/service pak for .NET 4 and they both use the same version of the CLR. If you look under Administration > System Information in mojoPortal, it is going to say "v4.0.30319" no matter whether it is .NET 4 or .NET 4.5 installed, so don't let that be a basis for thinking it is only .NET 4 installed. .NET 4.5 has been out for 2 years now and it is like a service pak for .NET 4 so there is really no reason not to install 4.5. The .NET 4 package of mojoPortal can run on either 4 or 4.5, but the 4.5 package of mojoportal and add ons are compiled for 4.5, and the most recommended configuration is to use the .NET 4.5 framework and the 4.5 compiled packages of mooPortal and related features.

you might also test whether something about the skin is a factor, ie do you get the same problem if you use a newer skin like art42-wallpaper. for example make sure that the layout.master has ScriptManager

8/29/2014 8:58:19 AM
Gravatar
Total Posts 118

Re: Form wizard pro

Is Mojoportal okay with .net 4.5.2?

8/29/2014 9:22:11 AM
Gravatar
Total Posts 18439

Re: Form wizard pro

yes definitely

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