Quantcast
Channel: BugNET Issue Tracker (Moved to GitHub)
Viewing all articles
Browse latest Browse all 2179

New Post: Redirecting to Install page

$
0
0
I finally figured it out. But it required that I dig into the code to find out what was being doing to force the upgrade.

The one thing that I didn't mention is that I had combined my DotNetNuke install and the BugNet install into the same database. DotNetNuke has a table called HostSettings and BugNet uses a table called BugNet_HostSettings, but in the PAST had used a table called HostSettings. In the file SqlDataProviderHelpers.cs in the source code that is located in the Library/Providers/DataProviders/SqlDataProvider directory, in the method GetDatabaseVersion(), the code is checking for a settingsvalue from the HostSettings table and expecting it to fail if it's not version .7 or .8. Since that table exists, but did not contain a row for version, it is returning null, which is then being dumped into the currentVersion variable. Right below that, the code is ONLY checking if currentVersion == string.empty or currentVersion == "ERROR", and no check is being done for NULL.

That check really should be String.IsNullOrEmpty(currentVersion) instead of just checking for string.empty, which would have properly prevented this particular issue from occurring.

In the meantime, I have added the version information to the HostSettings table and all is good. But I would like to see this get fixed properly so that I can remove that value from a DNN table.

I assume that this should be entered as a defect? I shall go ahead and do that.

dubeaud, thanks for your help. :)

Chaitanya Marvici

Viewing all articles
Browse latest Browse all 2179

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>