5.6.1.1 update from 5.6.1b1 just annihilated my new site!

Permalink 1 user found helpful
kick...ow....kick......owwww why oh wy do I always fall for this update nightmare!

My new site was all ready to go currently on 5.6.1b1, it has been running slowly as have a number of my clients site I have built in C5. I saw the 5.6.1.1 was an update option and with the promise of speedier loads, I decided to update.

Yes, did a backup first ;o)

Hit update and the whole site seemed to have lost it's link to my custom theme, as all the css was hosed!.

In a panic, I reverted back to 5.6.1b1 in my site.php file and the site theme is working, but every block I put into pages are missing.

Tried to roll back database backup, still no blocks and pages back as normal.

Help....

My clients sites are running C5 and I thought my own site would be a better bet to update first to see if speed enhancements really are worth the upgrade.

There is no way, I want to completely bring down their sites, but I want mine back.

Any help?

Thanks

pixeleleven
 
mhawke replied on at Permalink Reply
mhawke
Is there a public URL we could have a look at?
pixeleleven replied on at Permalink Reply
pixeleleven
Thanks for the speedy reply. I have the site running behind my url in a private folder, which I know does not help ;o)

But I have just emptied cache, refreshed server and browser and happily the blocks and all my original are back in using a 5.6.0.2 revert with a database rollback.

It would be great to know how to fix this 5.6.1.1 css redirect people are currently getting allowing my theme to load correctly and be able to use the new update?

Thanks
DBKG replied on at Permalink Reply
Same issue here.

Updated from 5.6.1 to 5.6.1.1 and now almost no css in effect.

I tried to go back to previous version/database, which has worked for me in the past, but got a MySql error when trying to install the backed-up database.

Should have checked the boards first...

http://www.charlottedragonboat.com/... is the domain. I am going to keep working on it, but for the moment, it's in a bit of a state.

Thanks.

Tim
VidalThemes replied on at Permalink Reply
VidalThemes
I have read in another post someone having the same problems switched their CSS links from:

<link rel="stylesheet" type="text/css" href="<?php echo $this->getStyleSheet('style.css')?>" />


to

<link href="<?php   echo $this->getThemePath()?>/style.css" rel="stylesheet" type="text/css" media="screen" />


Obviously there is a problem there, so this may only be a temporary fix, but apparently this is working, looks like its being reported as some kind of cache problem, in the leaders board.
VidalThemes replied on at Permalink Reply
VidalThemes
sorry my mistake its not on the leaders board, the other thread about it is here:

http://www.concrete5.org/community/forums/themes/version-5.6.1.1-er...
DBKG replied on at Permalink Reply
I don't know if this means anything, but in Firebug, this is listed under the HTML tab:

<link href="/files/cache/css/heart_concrete5/main.css" type="text/css" media="screen" rel="stylesheet">

<link href="/files/cache/css/heart_concrete5/typography.css" type="text/css" media="screen" rel="stylesheet">

<link href="/files/cache/css/heart_concrete5

Is it looking for the header stylesheets in the cache? Or am I misreading that?
VidalThemes replied on at Permalink Reply
VidalThemes
Yes from what I can gather that seems to be the problem.
mkly replied on at Permalink Reply
mkly
Hello,
There was an issue with getStyleSheet. See this thread for a temp patch

http://www.concrete5.org/community/forums/themes/version-5.6.1.1-er...

Let me know if it works for you.

Best Wishes,
Mike
mhawke replied on at Permalink Reply
mhawke
I can confirm that this fixed two of my sites that broke after updating to 5.6.1.1:

http://www.concrete5.org/index.php?cID=467169...
pixeleleven replied on at Permalink Reply
pixeleleven
Thanks guys,

I tried the fix, could not find a /core/ folder then found the thread which said that it was in the updates folder with the version. Found the line 269 and changed and saved.

That did nothing but I then realised that the update has to be run again with this 269 code change, yes?

I cleared cache before doing this.

So I have done that and all I get now is a totally blank site, help?

Thanks
pixeleleven replied on at Permalink Reply
pixeleleven
I can flick between 5.6.0.2 in site.php and site is fully working. Now change to 5.6.1.1 in site.php and totally blank site.

Perhaps this fix is not universal?

Anyone know if the actual bug fix will be coming anytime soon as I will probably leave the updating until there is a stable version.
Thanks guys.
pixeleleven replied on at Permalink Reply
pixeleleven
I fixed it!, I am now on 5.6.1.1

I deleted the original folder and uploaded 5.6.1 to my server, this updated through the dashboard fine. Then I did a fresh update in dashboard to the newly searched 5.6.1.1.

This did a remote install, broke my page up as I witnessed before, I then changed the line 269 in my update folder as Mike suggested, refresh, cleared cache and bingo!

Nothing broken, all looks good.

Chuffed to bits, thanks all.
love replied on at Permalink Reply
love
This is great if you're a developer and you can fix php and css.

What if you're not? And you have lost all your files...as I have!

What are the steps to retrieve and go back to the old version?

Thanks.