|
|
|
Forum Newbie
Group: Customers
Last Login: 13/07/2005 10:42:33
Posts: 19,
Visits: 24
|
|
| Hello all, I've put a large amount of time into re-skinning our RC1 release including custom include files for outer graphics, a custom home page with joins from SQL, and most recent posts, etc.. Anybody have experience with upgrading a previously skinned (non-default) forum to put in bug fixes? I'm a little nervous of doing this as I've got quite a few user's and posts. I realize RC1 is non-public, just looking for fastest, quality way to do this for a number of bug fixes. Custom content and forums are: http://www.amateur-hour.com (gaming site, not the bad stuff). Thanks again, Arroyocode
|
|
|
|
|
Junior Member
Group: Customers
Last Login: 14/12/2005 15:27:57
Posts: 26,
Visits: 158
|
|
| Arroyocode, I have done this from RC1 -> RC2 -> RC3 and its pretty painless for the most part. Most of my changes have been in the CSS and some in the HTML of the skin. One thing that you should do is to use the link provided with the upgrade that points out the changes in an Excel (XLS) document. It helps alot. Since you already have this running in a live environment, I would probably make a copy of that and work on the copy first to make sure its to your expectations.
|
|
|
|
|
IF.NET 4.2 Coming Soon
Group: Administrators
Last Login: 2 days ago @ 16:29:04
Posts: 1,956,
Visits: 3,018
|
|
Arroyocode (Arroyocode.com) (6/27/2005)
Hello all, I've put a large amount of time into re-skinning our RC1 release including custom include files for outer graphics, a custom home page with joins from SQL, and most recent posts, etc.. Anybody have experience with upgrading a previously skinned (non-default) forum to put in bug fixes? I'm a little nervous of doing this as I've got quite a few user's and posts. I realize RC1 is non-public, just looking for fastest, quality way to do this for a number of bug fixes. Custom content and forums are: http://www.amateur-hour.com (gaming site, not the bad stuff). Thanks again, Arroyocode Hi Arroyo, The best approach is to first run any .sql script provided with updates against your existing RC database. Then replace the assemblies with the latest versions within your existing Bin directory. Then run through your existing skin(s) replacing any .ascx files highlighted in Yellow within the Excel documents with the newer versions from the latest release candidate. A few other changes maybe occasionally be required between release candidates such as replacing the resources.xml or emails.xml file or additions to the skin style sheet. These are all documented within the Excel documents. I've sent you a PM with further information,
Kindest Regards,
Ryan Healey
Director / Developer
 Explore our products...
http://demos.instantasp.co.uk/
|
|
|
|
|
Forum Newbie
Group: Customers
Last Login: 13/07/2005 10:42:33
Posts: 19,
Visits: 24
|
|
| Thank you very much for the help. I'm getting ready to tackle this before week's end. Again, thank you for a wonderful product. - Arroyo
|
|
|
|