BugNET

Open source issue tracking & project management
  search

Forums

HomeHomeSupportSupportUpgrading BugNE...Upgrading BugNE...198 -> 211 Upgrade compilation problems198 -> 211 Upgrade compilation problems
Previous
 
Next
New Post
9/8/2010 2:15 AM
 
User is offline philw
No Ranking

Joined: 7/2/2009
Posts: 38
I followed the instructions for the 198 -> 211 upgrade precisely, including backing everything up, so at least I can get back from where I am to where I was.

The upgrade log looked fine, with both the database and everything else reporting successful upgrade.

The home page has formatting issues on Firefox, which is a surprise - it looks much worse than the previous version.

I can get a list of issues up, but get a compile error on clicking any of them:
Compiler Error Message: CS1061: 'ASP.issues_usercontrols_comments_ascx' does not contain a definition for 'cmdCancelEdit_Click' and no extension method 'cmdCancelEdit_Click' accepting a first argument of type 'ASP.issues_usercontrols_comments_ascx' could be found (are you missing a using directive or an assembly reference?)


Change log crashes on click, with a similar looking error:
Compiler Error Message: CS1061: 'ASP.projects_changelog_aspx' does not contain a definition for 'ChangeLogRepeater_ItemDataBound' and no extension method 'ChangeLogRepeater_ItemDataBound' accepting a first argument of type 'ASP.projects_changelog_aspx' could be found (are you missing a using directive or an assembly reference?)

I'll have to back this out if there's not an obvious solution. I followed the instructions precisely, and I have upgraded this before. web.config merging was straight forward, with Machine Key, Install date, and connexion string going across. I logged out before I did the upgrade.

(1) Anyone know what's going on here please?
(2) Do I need to restore the database to the previous version (yup, I backed it up immediately prior to the update so I can do this but it's a pain).
 
New Post
9/8/2010 2:51 AM
 
User is offline philw
No Ranking

Joined: 7/2/2009
Posts: 38
Ok, I can answer (1).

The upgrade needs full trust, so it won't work on Medium Trust host environments, although it doesn't tell you that. It will appear to upgrade correctly, but in fact it has not. The solution is to re-run the upgrade on a full trust site, which upgrades the DB (again?) and does whatever it does to the local configuration (I think it tweaks the web.config but have not checked that - you need Full Trust if it does that). Anyway, do teh upgrade on a full-trust IIS install, then move the files up to the Medium Trust install and it's done.

All is good.
 
New Post
9/8/2010 3:11 AM
 
User is offline philw
No Ranking

Joined: 7/2/2009
Posts: 38
Oops, not so fast... it all works, except the text of the defect note and any comments is coming up with 404s. It's still looking for FCKeditor:

http://[site]/BugNET/FCKEditor/editor/fckeditor.html?InstanceName=ctl00_Content_DescriptionHtmlEditor_DescriptionHtmlEditor&Toolbar=Default

Any ideas - this is kind of bad!
 
New Post
9/8/2010 6:56 AM
 
User is offline Davin Dubeau
1st Level Poster


Davin Dubeau's Avatar

bugnetproject.com
Joined: 3/2/2006
Posts: 1425
philw wrote:
Oops, not so fast... it all works, except the text of the defect note and any comments is coming up with 404s. It's still looking for FCKeditor:

http://[site]/BugNET/FCKEditor/editor/fckeditor.html?InstanceName=ctl00_Content_DescriptionHtmlEditor_DescriptionHtmlEditor&Toolbar=Default

Any ideas - this is kind of bad!

The default editor in BugNET is now the CKEditor, but if you wish to use the FCKeditor that is fine too. I would adjust the basepath parameter in the web.config for the FCKEditor. It looks like you need to remove the "BugNET" from the path and the html provider should be able to find the fckeditor files.

Davin Dubeau

follow us on twitter facebook users group google plus
 
New Post
9/8/2010 2:39 PM
 
User is offline philw
No Ranking

Joined: 7/2/2009
Posts: 38
Thanks.. I'll try that. I don't care what editor it uses; I'd rather use the default one... I'm not sure why it wants to use FCK. Is there any way I can tell it to use the default one?

I will try to remove "Bugnet" from the path - thanks.
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeSupportSupportUpgrading BugNE...Upgrading BugNE...198 -> 211 Upgrade compilation problems198 -> 211 Upgrade compilation problems


Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.
Copyright © 2011 BugNET   Terms Of Use  Privacy Statement  Page generated in 0.0312006 seconds.