Hi guys,

I had some problems with a site recently when I did an upgrade to 2.3.6.6. I did the upgrade using the recommended upgrade directions in the mojoPortal documentation (overwriting), but some site features aren't working correctly; I'm noticing some tags being rendered with classes that exist in my development environment but not in the production site, and the shared files upload functionality works for me under Windows 7 and IISExpress with FireFox, Chrome and IE, but not in the production site with a Mac (client's machine) running Safari, where it did work before the upgrade.

What I'm planning to do is blow away the site and re-deploying 2.3.6.6 clean, from scratch, and restoring the connection to the existing database by re-deploying the live web and user configs.

Is there a recommended procedure for what I'm planning, or do I just need to kinda wing it? :)

Best,

Duane Doutel

Hi Joe,

Yeah, fortunately, there isn't a lot of content uploaded yet, but what there is I have backed up. As for web.config and the database itself, they're both up to the 2.3.6.6 level, since I did the setup procedure when I upgraded to 2.3.6.6 over the previous version, and took the web.config from the 2.3.6.6 deployment package, applying the few changes I'd made in the previous version to the new web.config.

I did check the log, and didn't see anything, but it's gotten pretty large and I may have missed something. I guess what I need to know is, when I put the fresh deployment files out there, do I need to do anything else besides replacing the few content files and recreate the ~/sites/1/skins folder with the skin I'm working on for the site? And correct me if I'm wrong, but if I do the above, given a 2.3.6.6-level database already, I shouldn't run the setup/default.aspx, right? just restore the connection string in user.config, and turn on the site?

Many thanks!

Duane

Joe,

Replies on these forums are always helpful! :)

I HAD been building from source; no changes to code, but somewhere, something went awry; that's why I want to fall back on the distribution, and at this point, I think a clean upload from 2.3.6.6 deployment packages are what is needed. I'm using Filezilla as an FTP client. I think the bulk, if not all of these weird issues will go away once I've done that. Good to know that it's always safe to use /Setup/Default.aspx; I'll do that!

Again, many thanks for all the advice!

Duane