Fix mobile usability issues found on your website http://xxxxxxx.xx

ISSUE: Seems like google Webmaster tools is running a huge email blast to notify their users if a website is compatible with mobile devices, even though 98% if my websites are currently using wordpress. I  have a few sites still using the DotNetNuke CMS system. I plan to migrate them over soon here is a copy of the email that I got form them

Fix mobile usability issues found on

http://yourwebsite.com/

To: webmaster of http://yourwebsite.com/
Google systems have tested XXX pages from your site and found that 100% of them have critical mobile usability errors. The errors on these XXX pages severely affect how mobile users are able to experience your website. These pages will not be seen as mobile-friendly by Google Search, and will therefore be displayed and ranked appropriately for smartphone users.

I will update this post after my migration is complete, and see if I hit any bumps on the road my current migration would be from Managed.com (aka PowerDNN) using DotNetNuke to Godaddy.com using Wordpress.

Resolving the following NB_Store Dotnetnuke error and how to Downgrade the NBStore Module

I had an installtion of Dotnetnuke version 5.2.2.73 with a NB_Store version 02.03.02 in attempts to upgrade the Dotnetnuke NBStore version to 02.03.02 after installation everything worked, then when I tried to insert the Product list module into the content page I received the following error: 

Error: NB_Store_ProductList is currently unavailable.DotNetNuke.Services.Exceptions.ModuleLoadException: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\093391bf\b18d40e7\App_Web_categorymenu.ascx.7007b9cd.rbfo-d68.0.vb(53): error BC32206: The project currently contains references to more than one version of DotNetNuke, a direct reference to version 5.2.2.73 and an indirect reference (through 'NEvoWeb.Modules.NB_Store.CategoryMenu') to version 5.2.3.74. Change the direct reference to use version 5.2.3.74 (or higher) of DotNetNuke. ---> System.Web.HttpParseException: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\093391bf\b18d40e7\App_Web_categorymenu.ascx.7007b9cd.rbfo-d68.0.vb(53): error BC32206: The project currently contains references to more than one version of DotNetNuke, a direct reference to version 5.2.2.73 and an indirect reference (through 'NEvoWeb.Modules.NB_Store.CategoryMenu') to version 5.2.3.74. Change the direct reference to use version 5.2.3.74 (or higher) of DotNetNuke. ---> System.Web.HttpCompileException: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\093391bf\b18d40e7\App_Web_categorymenu.ascx.7007b9cd.rbfo-d68.0.vb(53): error BC32206: The project currently contains references to more than one version of DotNetNuke, a direct reference to version 5.2.2.73 and an indirect reference (through 'NEvoWeb.Modules.NB_Store.CategoryMenu') to version 5.2.3.74. Change the direct reference to use version 5.2.3.74 (or higher) of DotNetNuke. 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 ---

I read the error message and thought that maybe I cud downgrade by installing the NBstore version 02.02.03 but I then got a diffrent DNN error: 

Upload Results If you have reached this page it is because the installer needs to gather some more information, before proceeding.

Error reading the zip package - see below StartJob Reading Installation Manifest file Failure A newer version of this package is already installed - 2.3.2 Failure A newer version of this package is already installed - 2.3.2 Failure A newer version of this package is already installed - 2.3.2 Failure A newer version of this package is already installed - 2.3.2 Failure A newer version of this package is already installed - 2.3.2 Failure A newer version of this package is already installed - 2.3.2 Failure A newer version of this package is already installed - 2.3.2 I did some research online on how to Downgrade the NBSTORE and couldn't find anything that would quickly fix this issue, so I took matters into my own hands and decided to go under the Host menu and delete the extensions manually one by one I deleted the following:  I removed the following: NB_Store_BackOffice NB_Store E-Commerce Module for DNN. 2.3.2 NB_Store_CategoryMenu NB_Store. 2.3.2 NB_Store_Checkout NB_Store. 2.3.2 NB_Store_MiniCart NB_Store. 2.3.2 NB_Store_OrderHistory NB_Store. 2.3.2 NB_Store_ProductList NB_Store. 2.3.2 NB_Store_Search NB_Store. 2.3.2 And re-installed the previous version 2.01.07 and everything now worked with no database errors however all the items that were added previously to the store were now deleted. I will continue my research and post on how I was able to recover the items, however if you don't care about the data (store items/orders) then removing and re-installing the correct version will resolve your error RECOVERY! major issue the only way to recover is by contacting your hosting provider, goodluck for me I have one of the best Dotnetnuke hosting providers out there! They were able to recover my site back to 7 days prior to the issue happening and it all went back to normal!