YAFLogo

eutychus
  • eutychus
  • 100% (Exalted)
  • YAF Lover Topic Starter
8 years ago
I'm probaby just missing something here, so forgive me, but ...

I want to upgrade to 2.2.3. I downloaded the upgrade version and was about to upload it to my server when I noticed that the configuration files were included. Won't this cause me to lose the connection to the database or any other changes I might have made?

Sponsor
tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.1 BETA
8 years ago
Did you download the upgrade package? In the Upgrade package the config files are not included.
eutychus
  • eutychus
  • 100% (Exalted)
  • YAF Lover Topic Starter
8 years ago
Yes, they are!

 Untitled.png You have insufficient rights to see the content.

eutychus
  • eutychus
  • 100% (Exalted)
  • YAF Lover Topic Starter
8 years ago
Okay, so, I just deleted the config files from that package and uploaded it to my server. However now iyt's not recognizing 2.2.3 as the new upgrade.

 Untitled2.png You have insufficient rights to see the content.

tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.1 BETA
8 years ago
Yes the config files are there if you upgrade from an older version.

But if you follow the upgrade guide here...https://github.com/YAFNET/YAFNET/wiki/Upgrade-(from-Version-1.9.5.5-or-above) then you can see that you don't need to copy the folder to the server.

Okay, so, I just deleted the config files from that package and uploaded it to my server. However now iyt's not recognizing 2.2.3 as the new upgrade.

Did you copy the bin folder with all the dlls?

eutychus
  • eutychus
  • 100% (Exalted)
  • YAF Lover Topic Starter
8 years ago
Okay, did that ... got an install screen with 2.2.3 listed. But ...

When I tried to do the upgrade it kicked back an error that you can see in that attached screenshot.

And when I tried to back out by restoring my backups, it gives me this error:

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load file or assembly 'YAF, Version=2.2.2.0, Culture=neutral, PublicKeyToken=8b49dc47f4701f66' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Source Error:

Line 1: <%@ Page Title="Forum" Language="VB" MasterPageFile="~/forum.Master" AutoEventWireup="true" CodeBehind="Forum.aspx.vb" Inherits="YAF.SampleWebApplication.Forum" %>

Line 2:

Line 3: <%@ Register TagPrefix="YAF" Assembly="YAF" Namespace="YAF" %>

Source File: /forum/forum.aspx Line: 1

Assembly Load Trace: The following information can be helpful to determine why the assembly 'YAF, Version=2.2.2.0, Culture=neutral, PublicKeyToken=8b49dc47f4701f66' could not be loaded.

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 Untitled.png You have insufficient rights to see the content.

tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.1 BETA
8 years ago
You also need to update the YAF.SampleWebApplication.dll
eutychus
  • eutychus
  • 100% (Exalted)
  • YAF Lover Topic Starter
8 years ago
Okay, did that. Now it tries to do the update, but I still get the error I showed in the screenshot in my previous post.
eutychus
  • eutychus
  • 100% (Exalted)
  • YAF Lover Topic Starter
8 years ago
Barring a solution here, is there anyway to get it not to default to the install screen?
eutychus
  • eutychus
  • 100% (Exalted)
  • YAF Lover Topic Starter
8 years ago
Okay, I found a workaround that seemed to work. I went into the mssql/upgrade/constraints.sql file and commented out all of the functions that dealt with a TopicID constraint. The site is upgraded now, but does anyone have any idea how this may affect things in the future?