Dears,

I am using DNN04.08 forum module.Is any other advanced forum module available with ticket system and extra features?

regards

When you say "ticket system" are you looking more for a helpdesk type module? If so, you might want tio give aDefHelpDesk a try, it's free at adefhelpdesk.com Btw, the latest core forum module 05.00.01 is now available over at dotnetnuke.com it has better looking forums than the old 4x. You need to be running DNN 05.06.00 or newer though.

my requirement is i need a forum module like the link below...

https://www.godaddy.com/community/contactus.aspx?isc=gsnnme04&ci=22419§ion=emailus

The recommendation of adefhelpdesk is a good one. I've never used that particular module, but I've heard good things about it. And, the author, Michael Washington, is one of the long-time DotNetNuke "good guys."

Well, meenu, the link you provided is to a contact form not a forum You could try doing something similar with the core Feedback module but if you want ticketing etc then I definitely would consider a helpdesk module. You can start with aDEfHelpdesk but you can always search snowcovered.com for helpdesk for others.

but adefhelpdesk module is supported with DNN 5.X version only na?

i am using dnn 04.08.0 version from long back.
If i upgrade this version from 4.8 to latest version ,then any problems will come or not?

Yes, aDEfHelpdesk requires 4.9+. Not sure if you can upgrade directly to 5.6.1, I *believe* you can skip installing certain upgrades but don't know the sequence. And whilst 5.6.1 installed perfectly on one of my sites, it caused some problems on another and I've seen others having problems with it on the dotnetnuke.com forums (I never had any installation issues before 5.6.1).

Knew I had seen something about suggested upgrade paths somewhere http://www.dotnetnuke.com/Community...fault.aspx

I'd trust Cathal's list!

And, I do recommend upgrading if it's at all possible. Be careful to check with developers of all of your third-party modules before beginning as you may need to do some upgrading. If upgraded modules are backward compatible with the version you are running, do that first.

And, make backups before you start and after every upgrade.

Don't forget to test after each upgrade and fix any issues before moving to the next version.

If you are dealing with a live site, do the upgrading in a dev environment using a copy of the site.

If the live site includes user-contributed content, you may want to disable that temporarily so that your copy stays in sync with the live site during the upgrade. If it is going to take a few days, you might want to do a "rehearsal" first and, having found all of the issues, do it again on the current site (but offline).

i upgraded dnn 4.8 to 5.6.2 successfully.and i try to installed adefhelpdesk module through the instructions specified in the following link.
http://www.adefhelpdesk.com/Documen...fault.aspx

but i am getting message like as follows

Upload Results

If you have reached this page it is because the installer needs to gather some more information, before proceeding.
This package does not appear to be a valid DotNetNuke Extension as it does not have a manifest. Old (legacy) Skins and Containers do not contain manifests. If this package is a legacy Skin or Container Package please check the appropriate radio button below, and click Next.

Skin Container Not a Skin/Container

i solved this issue by the installaton of ADefHelpDesk_02.11.00_Install.zip instead ADefHelpDesk_02.10.00_Install.zip

That message is just a warning that the module is packaged in the "old" format. If you had just clicked Continue, all would have been fine. But, the later version, obviously packaged for DotNetNuke 5.x, is more recent and probably has some bug fixes.

hi joe,

Thanks...what u said is the rgt thing.

i installed ADefHelpDeskWebSite_02.10.00_Install first then i installed ADefHelpDeskWebSite_02.11.00_Install suceessfully.but when i add this module i am getting another error like as foloows




DotNetNuke.Services.Exceptions.ModuleLoadException: c:\Documents and Settings\aftiadmin\desktop\web files\dnn0408\DesktopModules\ADefHelpDesk\Controls\Tags.ascx.cs(86): error CS0433: The type 'ADefWebserver.Modules.ADefHelpDesk.CatagoriesTree' exists in both 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\080565a9\24d55c68\App_SubCode_ADefHelpDesk.gktutdv5.dll' and 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\080565a9\24d55c68\assembly\dl3\719c2e2f\4eaa21b0_89f2cb01\ADefHelpDeskWebSite.DLL' ---> System.Web.HttpParseException: c:\Documents and Settings\aftiadmin\desktop\web files\dnn0408\DesktopModules\ADefHelpDesk\Controls\Tags.ascx.cs(86): error CS0433: The type 'ADefWebserver.Modules.ADefHelpDesk.CatagoriesTree' exists in both 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\080565a9\24d55c68\App_SubCode_ADefHelpDesk.gktutdv5.dll' and 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\080565a9\24d55c68\assembly\dl3\719c2e2f\4eaa21b0_89f2cb01\ADefHelpDeskWebSite.DLL' ---> System.Web.HttpCompileException: c:\Documents and Settings\aftiadmin\desktop\web files\dnn0408\DesktopModules\ADefHelpDesk\Controls\Tags.ascx.cs(86): error CS0433: The type 'ADefWebserver.Modules.ADefHelpDesk.CatagoriesTree' exists in both 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\080565a9\24d55c68\App_SubCode_ADefHelpDesk.gktutdv5.dll' and 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\080565a9\24d55c68\assembly\dl3\719c2e2f\4eaa21b0_89f2cb01\ADefHelpDeskWebSite.DLL' at System.Web.Compilation.BuildManager.PostProcessFoundBuildResult(BuildResult result, Boolean keyFromVPP, VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode) at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.BaseTemplateParser.GetReferencedType(VirtualPath virtualPath, Boolean allowNoCompile) at System.Web.UI.BaseTemplateParser.GetUserControlType(VirtualPath virtualPath) at System.Web.UI.MainTagNameToTypeMapper.ProcessUserControlRegistration(UserControlRegisterEntry ucRegisterEntry) at System.Web.UI.BaseTemplateParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateControlParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseReader(StreamReader reader, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.UI.TemplateParser.Parse(ICollection referencedAssemblies, VirtualPath virtualPath) at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

Are you still having a problem with this?

yah same error is still showing. under DNN site i have a virtual directory with a different web.config,whether it will cause any pblm?

Yes, it is likely to cause problems. A few years ago I had a site that had a web app installed in a subdirectory of the DotNetNuke installation.

But, the good news is that you can correct the problems. You can do this in the web.config file of the web app by adding commands to remove DotNetNuke's namespaces, handlers, etc. that interfere with the web app.

I would think that the lower level web app should not interfere with DotNetNuke.

However, unless there is a compelling reason, I think that it would make a lot of sense to keep DotNetNuke and the web app separate. Is there any reason that you can't do that?

i can keep that web seperate. is any link available to know what steps need to do in web.config to avoid dnn cofg?

dear joe,

i solved my problem.

when i check my database, i saw all "ADefHelpDesk_" tables are thre after the uninstall process of adefhelpdesk module through the website.

i manually deleted all these tables from database,then installed this module again.Now the module installed suceessfully without any errors

You are rolling today! Great.