I even tried copying over the webconfig from the patch and just editing it to make it connect to the database, but it still is giving me this error.
Tried using my old file, and syncing settings.. I am a bit over whelmed at the moment..
Any chance you guys can lend me a hand with this ?
I am going to keep fighting with it, but so far no luck.
I also added the following to my original web config app settings:
<!-- Indicates if this is a WebPI Installation -->
<add key="WebPIInstallation" value="false" />
<!-- Default redirect URL for mobile clients. If empty, no redirect are performed unless this is set at the page level. -->
<add key="DefaultMobileRedirectUrl" value="/MonoX/Mobile/Default.aspx" />
<!-- jQuery reference path for mobile pages and controls. Change it to use other jQuery versions. Note that you can use different versions of jQuery for mobile and desktop versions of your site. -->
<add key="jQueryMobileBaseReferencePath" value="http://code.jquery.com/jquery-1.6.1.min.js" />
<!-- jQuery mobile reference path. -->
<add key="jQueryMobileReferencePath" value="/MonoX/Scripts/Mobile/jquery.mobile-1.0b1.min.js" />
<!-- Web part verb render mode - titlebar or menu. -->
<add key="WebPartVerbRenderMode" value="Titlebar" />
<!-- Verb button type - link, image, button. -->
<add key="WebPartTitleBarVerbButtonType" value="Image" />
which are changes I see between the new version and the old version..
I am still getting a error though..
I even tried using win diff and going thru the entire file and syncing anything up I felt was outdated.
the web config file looks pretty good.. but I am stumped on why its not working..
I figured out that anything that contains portal or a web part don't work..
Personalization is not enabled and/or modifiable. The
Enabled property must be set to true, and a registered personalization
provider must be selected. The current user must be granted the right to
modify personalization state.
I was able to login, using the login page but then when it forwarded me to the default page.aspx i got the same error..
I then navigated to a page without any portals on it that works when not logged in and then I was greeted with another error..
Value cannot be null.
Parameter name: relativeUrl