Hey,

Under Admin I do see the newsletter icon but when I click on it I get an empty page with nothing on it... Am I missing somethere here (well obiously) is there any tutorial on this module? Perhaps there are pre-requisites that need to be installed or something...?

Thanks

Aad

Perhaps the Newsletter module somehow is missing from that page. You can add it using the Add Module function.

Hi Joe,

that is the crazy part, it is not available in the add module wizard.. What can I do to add the module manually??

Thanks for the quick reply!

Aad

Check that the Newsletter module is installed by looking on the Host, Extensions page.

If it is installed, then it may not be available.  These tutorials might help:

• How to Limit Modules Available in the Control Panel (Premium Modules)
• How to Configure Which Modules Non-Administrators Can Add to a Page

Hi Joe, thank you for your thoughts. However, the module is not visible on the host extensions page either, nor is it available for installation.. My hosting provider tells me they do not withold any modules from customers so it's not shielded of... The filemanager module does not budge either.. Should I just go ahead and re-install DNN??

Thanks Aad

Create a new installation (perhaps on a test server) that is the same version as your DotNetNuke installation.  Hopefully, that one will install with a copy of the newsletter module.

Then, go to the Extensions page, locate the Newsletter module.  Click the Edit pencil, and locate the Package Settings section.  You can click a link there to create an installable version of the Newseltter Module.  You can install that in your installation.

Hi Joe,

Sorry it took me a bit to respond, will try that now! I have upgraded my test server to 5.05, will do same now for live server and try to move newsletter module from one to the other! Thanks! Aad

Hi Joe,

No dice manually installing the newsletter module.. All went well creating the package and installing it on the other server.. I now see it in the host - extentions list but when I open the newsletter module in the admin control panel I still only get an empty page...
Additional detail, I upgraded to 5.5 on both servers, on the test server I get the auto upgrade process, on the other server nothing happens, but in host menu it does say it is version 5.5.. Somehow I don't trust the installation the hosting provider performed for me.. Can I just re-install while keeping the original web.config file? Many thanks Aad

Just one more step ...

After installing the Newsletter module, you need to go to the Admin, Newsletter page and install an instance of the module on the page.  Because you see it listed on the Extensions page, you should also see it listed as a module that can be installed on the page.

Hey Joe,

Thanks for the extra step, now it is working! Still wonder why it was not installed by default.. Do you have any idea? Also when I upgrade to a newer version the install wizard does not come up.. Maybe that has something to do with the same issue??

Thanks Aad

I would assume that some error prevented the correct installation. 

There is a setting in web.config which, if set, disables the automatic start of the installation wizard. 

                 < add key="AutoUpgrade" value="true" / >

I believe that it is there to give you some control over when the wizard starts.  For example, to make sure that you are the one who starts it instead of a random visitor to your site. 

Set it to "false" to disable the automatic upgrade.

Jep an error indeed.. Once I set the autouprade to false, the site broke with this error.. Any ideas how to fix this??

The files '/App_Code/NewsSubscription/NewsSubscriptionController.cs' and '/App_Code/IFrame/Domain/IFrameParameterCollection.vb' use a different language, which is not allowed since they need to be compiled together.
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: The files '/App_Code/NewsSubscription/NewsSubscriptionController.cs' and '/App_Code/IFrame/Domain/IFrameParameterCollection.vb' use a different language, which is not allowed since they need to be compiled together.

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): The files '/App_Code/NewsSubscription/NewsSubscriptionController.cs' and '/App_Code/IFrame/Domain/IFrameParameterCollection.vb' use a different language, which is not allowed since they need to be compiled together.]
System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() +452
System.Web.Compilation.BuildProvidersCompiler.PerformBuild() +42
System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) +8809466
System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) +128
System.Web.Compilation.BuildManager.CompileCodeDirectories() +265
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +320

[HttpException (0x80004005): The files '/App_Code/NewsSubscription/NewsSubscriptionController.cs' and '/App_Code/IFrame/Domain/IFrameParameterCollection.vb' use a different language, which is not allowed since they need to be compiled together.]
System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +58
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +512
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +729

[HttpException (0x80004005): The files '/App_Code/NewsSubscription/NewsSubscriptionController.cs' and '/App_Code/IFrame/Domain/IFrameParameterCollection.vb' use a different language, which is not allowed since they need to be compiled together.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +8890735
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +85
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +259

Which version of DotNetNuke is this?

it's the latest version, 5.0.5

Can you revert and try the upgrade again?

I actually think the upgrade went well, I added a 3rd party news subscription module afterwards, then turned off and back on auto-upgrade and then things went boom.. DNN seems to complain about that module and the regular Iframe module which I put in place last week and which functioned just fine before..

This is odd.  Changing the AutoUpgrade key shouldn't do anything if the upgrade actually ran.  You might want to check and see if you did something unintended to web.config.

(Hopefully you make backups before you make changes.)

Hi Joe,

Thanks for bearing with me on this one. I think I may have messed stuff up going back and forth between my two hosting providers and my local files which are synchronized between my laptop, desktop and back up disk.. I think I will just re-send everything from my back up disk to the first hosting provider and if that does not fix things, I will switch over to the second which makes a more solid impression anyway...

Aad