"Currently Running 5.6.0.2 No updates available."
Permalink
^ Is this anything to be concerned about? I just upgraded an old site to 5.6.0.2 and since 5.6.1 is out, clearly there is another update available. I click "check for updates" and it just keeps showing this message.
ooh, that's weird. I manually uploaded the newest 5.6.1 concrete folder, renamed the old one to "concrete-old" and went to run the installer script and it says the same thing still: "Currently Running 5.6.0.2" ... it asks if I want to rerun the script but I think that would probably definitely break it somehow because it seems screwy already.
Yep, this is confusing.
/updates/ folder doesn't show 5.6.1, either, just 5.6.0.2... so 5.6.1. definitely was not installed even though I replaced the old /concrete/ folder with the newest one and pointed the URI to the update tool...
/updates/ folder doesn't show 5.6.1, either, just 5.6.0.2... so 5.6.1. definitely was not installed even though I replaced the old /concrete/ folder with the newest one and pointed the URI to the update tool...
Change your [root]\concrete-old folder back to [root]\concrete, then create a [root]\updates\concrete5.6.1 folder and put the new core in it. Once that is done, you can use the upgrade feature in the dashboard to update you site.
Ah, so that's how it's done these days. Thank you kindly, good sir! Much appreciated.
I wonder whether the update funktion in the backend is going to work again in the near future or we have to live with that workaround. Which, itself is not dramatic, it's just that it makes c5 look messy.
Automatic updates from the back-end will be serving 5.6.1.1, once that version is stable (= minor bugs and issues from 5.6.1 has been fixed).
OK, thanks. Love to be informed :-)
I wonder if one of those things is broken WYSIWYG / TinyMCE ... hope so because I upgraded using the method above and now my Content blocks only display as html (see attached)
This could be caused by a javascript error. Are you seeing any errors in your browser's console?
Yes! I didn't think of that. Not sure how to fix it.
EDIT: Googling for "Concrete5.6 TinyMCE javascript error" I was able to find this bug report and fix:
http://www.concrete5.org/developers/bugs/5.6.0.1/tinymce-does-not-l...
The solution was to "go into the Dashboard > System & Settings > Basics > Editor, change it to Simple, then change it back to custom (and make your changes to the newly updated custom code.)" ....
I simple switched to "simple" clicked "save" and then switched it to custom and clicked "save." Now my TinyMCE works fine. Just a random bug from the upgrade, I guess.
EDIT: Googling for "Concrete5.6 TinyMCE javascript error" I was able to find this bug report and fix:
http://www.concrete5.org/developers/bugs/5.6.0.1/tinymce-does-not-l...
The solution was to "go into the Dashboard > System & Settings > Basics > Editor, change it to Simple, then change it back to custom (and make your changes to the newly updated custom code.)" ....
I simple switched to "simple" clicked "save" and then switched it to custom and clicked "save." Now my TinyMCE works fine. Just a random bug from the upgrade, I guess.
PS... thank you thank you a thousand times thank you! :-) I would have never found the answer if you hadn't suggested it was a javascript error.
NetJunky,
you said: "Change your [root]\concrete-old folder back to [root]\concrete, then create a [root]\updates\concrete5.6.1 folder and put the new core in it."
Should I have only put the "core" directory in upgrades/concrete5.6.1 ?? It worked by putting the whole "concrete" directory in there, but my WYSIWYG / TinyMCE is broken and maybe this is why.
I just realized there is a singly directory called "core" within "concrete."
you said: "Change your [root]\concrete-old folder back to [root]\concrete, then create a [root]\updates\concrete5.6.1 folder and put the new core in it."
Should I have only put the "core" directory in upgrades/concrete5.6.1 ?? It worked by putting the whole "concrete" directory in there, but my WYSIWYG / TinyMCE is broken and maybe this is why.
I just realized there is a singly directory called "core" within "concrete."
By "core" I meant the concrete folder.
Yeah, so this isn't even working on one of my websites.
After I drop the 5.6 concrete folder in ~root/updates if I then go to System Update in the Dashboard, it shows that it's on 5.5.2.1.
If I click "check for updates" it gives me an error, which is apparently just a bug according to Andrew and I should go ahead an upgrade anyway.
So, the only way I know to upgrade is by going to ...www.www.mysite.org/index.php/tools/required/upgrade...
...and clicking "upgrade" ...
I do that and it says "You're already up to date on 5.5.2.1!"
So apparently, it is impossible to upgrade to 5.6 for some reason.
After I drop the 5.6 concrete folder in ~root/updates if I then go to System Update in the Dashboard, it shows that it's on 5.5.2.1.
If I click "check for updates" it gives me an error, which is apparently just a bug according to Andrew and I should go ahead an upgrade anyway.
So, the only way I know to upgrade is by going to ...www.www.mysite.org/index.php/tools/required/upgrade...
...and clicking "upgrade" ...
I do that and it says "You're already up to date on 5.5.2.1!"
So apparently, it is impossible to upgrade to 5.6 for some reason.
does anyone have any idea why this would not update to Concrete5.6.1?
I created a directory in ~/updates/ called "concrete5.6.1" and then I placed the 5.6.1 concrete directory within that.
When I go to "http://www.mysite.com/index.php/tools/upgrade" it merely gives me the message:
"Upgrade to 5.5.2.1 complete!"
This NEVER worked and nobody ever said what the problem might be. The updates folder was new to me as far as manual upgrading goes and it only worked for 5.5.2.1. When I tried the same technique for 5.6.1 it simply ignored 5.6.1 is even in the updates folder.
Really need to figure this out since my website is currently broken again due to removing one of the update folders and breaking my site.
I created a directory in ~/updates/ called "concrete5.6.1" and then I placed the 5.6.1 concrete directory within that.
When I go to "http://www.mysite.com/index.php/tools/upgrade" it merely gives me the message:
"Upgrade to 5.5.2.1 complete!"
This NEVER worked and nobody ever said what the problem might be. The updates folder was new to me as far as manual upgrading goes and it only worked for 5.5.2.1. When I tried the same technique for 5.6.1 it simply ignored 5.6.1 is even in the updates folder.
Really need to figure this out since my website is currently broken again due to removing one of the update folders and breaking my site.
One more question:
It says "Your site is already up to date! The current version of Concrete5 is 5.5.2.1. You should remove this file for security."
Maybe that's the problem. What do I remove for security? Maybe when I remove it I will be able to upgrade to 5.6.1 finally using this ~/updates/ manual method.
It says "Your site is already up to date! The current version of Concrete5 is 5.5.2.1. You should remove this file for security."
Maybe that's the problem. What do I remove for security? Maybe when I remove it I will be able to upgrade to 5.6.1 finally using this ~/updates/ manual method.
FYI...
I reverted to an older version of the database from February which was from 5.5.2.1, I think (or the last release just before that). All I did was import this old database backup with phpMyAdmin and the site started working again.
Then, since I now had 3 versions of of Concrete5 in the ~/updates/ directory, I navigated to "www.mysite.com/index.php/tools/required/upgrade" and wonderfully I was greeted with a message that made sense: I have 3 upgrades waiting! I chose 5.6.1.2 and it worked perfectly.
I have no idea why it wouldn't work before when I tried to upgrade from 5.5.2.1 to 5.6.1.2, but it worked this time.
I reverted to an older version of the database from February which was from 5.5.2.1, I think (or the last release just before that). All I did was import this old database backup with phpMyAdmin and the site started working again.
Then, since I now had 3 versions of of Concrete5 in the ~/updates/ directory, I navigated to "www.mysite.com/index.php/tools/required/upgrade" and wonderfully I was greeted with a message that made sense: I have 3 upgrades waiting! I chose 5.6.1.2 and it worked perfectly.
I have no idea why it wouldn't work before when I tried to upgrade from 5.5.2.1 to 5.6.1.2, but it worked this time.
Hello,
This solution did not work for me. I'm still running 5.6.2 and after checking for updates it shows "No updates available". Can you recommend another solution?
Thanks!
This solution did not work for me. I'm still running 5.6.2 and after checking for updates it shows "No updates available". Can you recommend another solution?
Thanks!
Hi, something new I discovered recently that was probably causing me some problems in earlier days was that there is a line of code in config/site.php file that points to the updates folder and the update within that folder. So, it's kind of a two-part situation. You basically need to copy + paste that code from the older site.php into the newer site.php if it is not there when you create the new website.
I have gotten pretty good at moving websites around since I am doing 6 similar C5 sites in a row at the moment.
I have gotten pretty good at moving websites around since I am doing 6 similar C5 sites in a row at the moment.
