[SOLVED] pgraded from Bonde to 1.8 and my design is now hosed.

[pixelita]

Whiskey. Tango. Foxtrot!!!

The design is completely borked after the upgrade. It was thoroughly tested a month or so ago.  Now even though the images are in the /images folder where they belong, some are being called and some are not.  Yes, I changed the stylesheet to {cms_stylesheet} in all the templates.

What gives?

Borked site is here:
http://sheldon.mytestbed.com

This is kind of what it is supposed to look like:
http://sheldonfd.org

Ugh!!!!!

[pixelita]

You know, when this kind of thing happens, it does NOT encourage me to run the latest version. AT ALL.  The site was absolutely fine except for one small issue with an RSS feed.  But I wanted to make sure I had the latest version before I came on here asking for help.

Now I have no choice, it appears, but to live with the RSS problem, and revert back to Bonde.  At least we had a site three hours ago.

Now we have utter crap.

I've been a huge evangelist for CMSMS but I'm about two shakes away from porting this sucker to WordPress.

[pixelita]

For the time being, unless and until someone can help figure out why the design is completely hosed in 1.8, I have reverted the files and database back to Bonde (1.6.6).

[uniqu3]

After switching to {cms_stylesheet} did you also change paths in your CSS?
Since 1.8 and usage of {cms_stylesheet}, .css file is saved in /tmp folder so if you use for example #something {
background: url(uploads/yourtherme/something.gif);} in the stylesheet this will lead to not showing the image so the path needs either url([[root_url]]/uploads/yourtherme/something.gif); or url(../../uploads/yourtherme/something.gif);

[tyman00]

1.) I will agree with unique3... make sure your paths are correct in the stylesheet for the new tag

2.) This is why it has always been highly recommended that you use a second test site for staging the upgrade in the event something does go awry

3.) Without more details or a real live working version of the issue, it's very difficult for us to provide better support.

[pixelita]

An update. I got it back up and running on version 1.8.  My RSS Feed issue still hasn't gone away (I had hoped that upgrading to the latest CG Feedmaker module would have cured it.

My solution was to stand pat with the {stylesheet} tag rather than the {cms_stylesheet} tag.  I develop offline using Topstyle Pro and having that weird tag in there ... couldn't see my images.  So unless there's some huge security issue with keeping the {stylesheet} tag, I'm hanging tight with it.

I'll mark this thread "RESOLVED" SOLVED now.  And headed off to post about the feed issues.

Here's the site if anyone wants to take a look. I'll be requesting a site check once I get the RSS feed issue nailed.
http://sheldon.mytestbed.com