No Dashboard!
Permalink
When I try to open the 'Dashboard' after login I get the following error message:
Fatal error: Call to undefined method ConcreteDashboardHelper::getDashboardBackgroundImage() in /home2/webnzedc/public_html/webdev/concrete/themes/dashboard/elements/header.php on line 67
line 67 $backgroundImage = Loader::helper('concrete/dashboard')->getDashboardBackgroundImage();
HELP!!
Fatal error: Call to undefined method ConcreteDashboardHelper::getDashboardBackgroundImage() in /home2/webnzedc/public_html/webdev/concrete/themes/dashboard/elements/header.php on line 67
line 67 $backgroundImage = Loader::helper('concrete/dashboard')->getDashboardBackgroundImage();
HELP!!
Have you recently updated C5? Any changes you have made to the overall environment - updated addons, themes, changes to settings?
What version of C5 are you running?
Is it that you have no dashboard toolbar? Or that you cant get to the actual dashboard?
What version of C5 are you running?
Is it that you have no dashboard toolbar? Or that you cant get to the actual dashboard?
I am currently running 5.5.1 but I also had the problem when running it under 5.4.2.2 -- upgraded in the hope that the problem would be fixed but it wasn't. As far as I know there have been no new addons in recent times or change to the themes.
Sorry, about the dashboard, when I loggin, the Dashboard button appears on the upper toolbar, but clicking it gives the error message.
I don't think the error message you are getting existed before 5.5 (someone can chip in and tell me if I am wrong). Without digging into the core code, I suspect it is to do with the background photo that 5.5 displays.
Did you upgrade to 5.5.1 just by copying the code in? Or did you run the upgrade php file?
Did you upgrade to 5.5.1 just by copying the code in? Or did you run the upgrade php file?
I ran the Concrete5 upgrade using SimpleScript -- a utility that is used at Bluehost.com (ISP provider) for installing software on the site. I run about a dozen other websites and have successfully upgraded them to the recent 5.5.1 versions without any problems. It could be a theme or an install problem since both problem sites (one a sandbox testing site and the other a live client site) use the same theme.
I have just noticed from the source code that both sites are still running version 5.4.2.2 !! It could be that in trying to install the upgrade to 5.5.1 something unpleasant has happened. Where are the backups you say?? The relevant site is:http://dignitysa.com
I have just noticed from the source code that both sites are still running version 5.4.2.2 !! It could be that in trying to install the upgrade to 5.5.1 something unpleasant has happened. Where are the backups you say?? The relevant site is:http://dignitysa.com
It is starting to look like the update process did not fully complete. This is unfortunately not unusual on shared hosting if upgrade is run from within C5. The web process doing the update runs out of processor allocation before it has finished the job.
To explore further, and maybe find out where the upgrade failed, some more investigation:
Do you have phpMyAdmin?
If so, look in the config table of the database for the C5 version noted there. It will tell you what version of C5 it thinks is actually active.
Also, using ftp or your host control panel look in the C5 root on the server for the updates folder, and see what versions are actually in that folder.
Finally, look in the file /config/site.php and see if there is a version listed in the last line of that file.
(If you post the /config/site.php file here, make sure to remove the database, user and password lines first!!!)
To explore further, and maybe find out where the upgrade failed, some more investigation:
Do you have phpMyAdmin?
If so, look in the config table of the database for the C5 version noted there. It will tell you what version of C5 it thinks is actually active.
Also, using ftp or your host control panel look in the C5 root on the server for the updates folder, and see what versions are actually in that folder.
Finally, look in the file /config/site.php and see if there is a version listed in the last line of that file.
(If you post the /config/site.php file here, make sure to remove the database, user and password lines first!!!)
We had that too. Just update again.
This is the most likely solution.
I was checking versions to confirm that it was the right problem for that solution.
Give it a go, but just to be safe, if you have a database backup facility provided by your host (or through phpMyAdmin), run that first just in case running the upgrade again makes things worse.
I was checking versions to confirm that it was the right problem for that solution.
Give it a go, but just to be safe, if you have a database backup facility provided by your host (or through phpMyAdmin), run that first just in case running the upgrade again makes things worse.
The update to 5.5.2.1 crashed the site. See attached file for error messages!!
After some nail-biting and nerve-racking efforts I managed to restore the site to its previous dysfunctional state.
Basically I am not interested in geeking around trying to find where the fault is -- I just want the site to work. This should not be necessary for a mature, reliable website software.
After some nail-biting and nerve-racking efforts I managed to restore the site to its previous dysfunctional state.
Basically I am not interested in geeking around trying to find where the fault is -- I just want the site to work. This should not be necessary for a mature, reliable website software.
The error message is typical of an incomplete upgrade, where the server ran out of time before everything was complete, but after the upgrade had gone too far to be able to turn back.
What corretje meant was to re-run the upgrade for the version that the upgrade had failed on (5.5.1). Having said that, with 5.5.2.1 just released its not surprising that the message got confused. Well done for taking the backup and at least being no worse for it (save a lot of unwanted messing about).
Can we go back to what I posted yesterday, getting as much info as possible on what different C5 versions may or may not be configured in various places.
What corretje meant was to re-run the upgrade for the version that the upgrade had failed on (5.5.1). Having said that, with 5.5.2.1 just released its not surprising that the message got confused. Well done for taking the backup and at least being no worse for it (save a lot of unwanted messing about).
Can we go back to what I posted yesterday, getting as much info as possible on what different C5 versions may or may not be configured in various places.
In reply to your previous questions:
1. For the config table in the database, there is an entry for SITE_APP_VERSION: 5.5.2.1
and for APP_VERSION_LATEST: 5.4.2.1 with their associated dates.
2. The updates folder is empty --!
3. The file/config/site.php has no version listed on the last line. This probably means that no updates occurred.
My plan is to build another site from scratch in the event that the current dysfunctional one finally falls over for good.
WORDPRESS is beginning to look more and more user-friendly !
1. For the config table in the database, there is an entry for SITE_APP_VERSION: 5.5.2.1
and for APP_VERSION_LATEST: 5.4.2.1 with their associated dates.
2. The updates folder is empty --!
3. The file/config/site.php has no version listed on the last line. This probably means that no updates occurred.
My plan is to build another site from scratch in the event that the current dysfunctional one finally falls over for good.
WORDPRESS is beginning to look more and more user-friendly !
Sorry for taking time, have been away from my desk.
I think you should try a manual upgrade to 5.5.1, checking that it is proceeding correctly at each step of the way. By doing it in discrete steps you are less likely to over-run server limits.
1. Make fresh backups of your database and all files from /siteroot/ and below.
2. Download a fresh zip of 5.5.1 from
http://www.concrete5.org/developers/downloads/...
3. Unzip this into:
/siteroot/updates/concrete5.5.1/
4. Check you have these subfolders and files within the 5.5.1 folder:
/siteroot/updates/concrete5.5.1/concrete/ (contains the 5.5.1 concrete core)
/siteroot/updates/concrete5.5.1/config/
/siteroot/updates/concrete5.5.1/files/ (empty)
/siteroot/updates/concrete5.5.1/LICENCE.txt
/siteroot/updates/concrete5.5.1/robots.txt
/siteroot/updates/concrete5.5.1/INSTALL (installation instructions)
/siteroot/updates/concrete5.5.1/index.html
5. Up to this point you have done nothing that will break what is already there. The next step is the one that actually changes the database.
6. Visit the url
http://yoursite.com/index.php/tools/required/upgrade...
Step 6. May refuse to run because you have SITE_APP_VERSION at a greater version, in which case you may need to fiddle that value with phpMyAdmin.
Step 3. and 6. are the ones that may timeout or otherwise run into server limits.
I think you should try a manual upgrade to 5.5.1, checking that it is proceeding correctly at each step of the way. By doing it in discrete steps you are less likely to over-run server limits.
1. Make fresh backups of your database and all files from /siteroot/ and below.
2. Download a fresh zip of 5.5.1 from
http://www.concrete5.org/developers/downloads/...
3. Unzip this into:
/siteroot/updates/concrete5.5.1/
4. Check you have these subfolders and files within the 5.5.1 folder:
/siteroot/updates/concrete5.5.1/concrete/ (contains the 5.5.1 concrete core)
/siteroot/updates/concrete5.5.1/config/
/siteroot/updates/concrete5.5.1/files/ (empty)
/siteroot/updates/concrete5.5.1/LICENCE.txt
/siteroot/updates/concrete5.5.1/robots.txt
/siteroot/updates/concrete5.5.1/INSTALL (installation instructions)
/siteroot/updates/concrete5.5.1/index.html
5. Up to this point you have done nothing that will break what is already there. The next step is the one that actually changes the database.
6. Visit the url
http://yoursite.com/index.php/tools/required/upgrade...
Step 6. May refuse to run because you have SITE_APP_VERSION at a greater version, in which case you may need to fiddle that value with phpMyAdmin.
Step 3. and 6. are the ones that may timeout or otherwise run into server limits.
Hi
I really, really, really appreciate the time and effort you have put into rebuilding and updating mysite. And I definitely shall go thru the detailed instructions you have given.
My situation is we are about to launch a public petition in South Africa to legalise assisted dying. I have people in SA who are adding content and making pages. I can not afford to have the site down for even a brief period. They are happy with the way things are working and they can hide pages and content until 'launch time'. In fact not being able to open the Dashboard is a mixed blessing since they can't seriously alter the site -- Microsoft might call this dysfunction a 'feature'.
My plan B is to build a backup site which I can quickly switch to in the event that the site crashes.
Thanks again and you shall hear from me as to how things turned out.
I really, really, really appreciate the time and effort you have put into rebuilding and updating mysite. And I definitely shall go thru the detailed instructions you have given.
My situation is we are about to launch a public petition in South Africa to legalise assisted dying. I have people in SA who are adding content and making pages. I can not afford to have the site down for even a brief period. They are happy with the way things are working and they can hide pages and content until 'launch time'. In fact not being able to open the Dashboard is a mixed blessing since they can't seriously alter the site -- Microsoft might call this dysfunction a 'feature'.
My plan B is to build a backup site which I can quickly switch to in the event that the site crashes.
Thanks again and you shall hear from me as to how things turned out.
Hi - can I jump in on this and say this is happening to me also. I've tried everything but it refuses to move off 5.4.2 and I'm getting the same
I have followed the instructions above but on the upgrade page it says 'you have successfully upgraded to 5.4.2.2. I've spent hours on this and can't seem to get it to perform the upgrade.
The frustrating thing is I have it working fine on another server with a successful upgrade. Any ideas anyone getting to the end of my tether on this one....
when I try to get onto the dashboard.
I have followed the instructions above but on the upgrade page it says 'you have successfully upgraded to 5.4.2.2. I've spent hours on this and can't seem to get it to perform the upgrade.
The frustrating thing is I have it working fine on another server with a successful upgrade. Any ideas anyone getting to the end of my tether on this one....
I have finished Plan B and built another site and it is up and running. Finding the fault with the old site now becomes something of a puzzle solving challenge. I have followed your steps 1 - 6 and as you predicted at step 6 I get "Your site is already up to date! The current version of Concrete5 is 5.4.2.2".
It seems no matter what I do, it does not update. I have tried tinkering with the VERSION files using phpMyAdmin and after running the upgrade it always reverts to SITE_APP_VERSION 5.4.2.2. I have tried removing the VERSION files and other potential items but it still reverts to 5.4.2.2. There must be some lingering data that gets reinstated each time.
It seems no matter what I do, it does not update. I have tried tinkering with the VERSION files using phpMyAdmin and after running the upgrade it always reverts to SITE_APP_VERSION 5.4.2.2. I have tried removing the VERSION files and other potential items but it still reverts to 5.4.2.2. There must be some lingering data that gets reinstated each time.
This is a guess. Perhaps you could try also tweaking APP_VERSION_LATEST forward to the version you are trying to upgrade to manually.
(To anyone coming in to this late - tweaking the database manually is dangerous. Always backup before, that way if the tweak makes a mess of it you can at least get back to where you started)
(To anyone coming in to this late - tweaking the database manually is dangerous. Always backup before, that way if the tweak makes a mess of it you can at least get back to where you started)
I have tried that -- same result, still 5.4.2.2
Have you tried this
To force concrete to update again?
http://www.yoursite.com/index.php/tools/required/upgrade?force=1
To force concrete to update again?
Yes, every time I try the upgrade, I get that option to repeat, result is alway: "Upgrade to 5.4.2.2 complete!"
I was sitting here thinking that Dave(Weyboat)'s suggestion would be the final step to solving it.
What are the file permissions of config/site.php?
One of the last things the upgrade does is to change or add a line at the end of that file pointing to the code in the updates folder, and the line includes the version number.
What are the file permissions of config/site.php?
One of the last things the upgrade does is to change or add a line at the end of that file pointing to the code in the updates folder, and the line includes the version number.
In the config/site.php - there was no line for the version number, so I took the liberty of adding:
<?php define('DIRNAME_APP_UPDATED', 'concrete5.5.2.1');?>
After running the upgrade command, the version 5.5.2.1 was installed!! but no pages were rendered due to the following error message:
An unexpected error occurred.
mysql error: [1146: Table 'webnzedc_cnc2.atBoolean' doesn't exist] in EXECUTE("select value from atBoolean where avID = '23' LIMIT 1")
Thankfully the site is not 'live'.
This seems to be a new problem, is this progress?
<?php define('DIRNAME_APP_UPDATED', 'concrete5.5.2.1');?>
After running the upgrade command, the version 5.5.2.1 was installed!! but no pages were rendered due to the following error message:
An unexpected error occurred.
mysql error: [1146: Table 'webnzedc_cnc2.atBoolean' doesn't exist] in EXECUTE("select value from atBoolean where avID = '23' LIMIT 1")
Thankfully the site is not 'live'.
This seems to be a new problem, is this progress?
Can you list the folders that reside inside your /root/updates/ folder?
Note: Not the /root/concrete/updates/ folder..
Note: Not the /root/concrete/updates/ folder..
Two folders:
concrete5.5.2.1
concrete5.5.2.1.zip
concrete5.5.2.1
concrete5.5.2.1.zip
In the concrete5.5.2.1 folder is there a sub folder of the same name (concrete5.5.2.1)
If so try moving the sub folder out into the /root/updates/ directory,
In order to achieve this you will have to rename the parent concrete5.5.2.1 folder to something like concretetemp,
If so try moving the sub folder out into the /root/updates/ directory,
In order to achieve this you will have to rename the parent concrete5.5.2.1 folder to something like concretetemp,
There is no sub folder with the same name, attached are the contents of the concrete5.5.2.1 folder
I have restored the site to its previous state running 5.4.2.2 with the same old 'No dashboard' problem.
Can you post a url to that site?
So you have an installation of concrete5.5.2.1 for the webnzed.com site and in that package you have created a folder called /theoldgignity/ and installed concrete5.4.2.2,
Is that correct?
Is that correct?
No, it doesn't work that way. The primary domain in the account is webnzed.com and it has a c5 installation, several independent sub-domains were created each with their independent c5 installations. When the dignitysa.com domain was no longer working I renamed it theolddignity and installed a new c5.5.2.1 in the primary domain and assigned it the dignitysa.com sub-domain. Initially all domains had c5.4.2.2 (or whatever the version was current at the time). I was able to update all domains to c5.5.2.1 except the sub-domain that is now called theolddignity.
At this point fixing the faulty site is no longer an issue and as JohntheFish correctly pointed out somewhere along the line the site did not get probably updated and now is stuffed.
Thanks for your suggestions, I have learned more about c5 than I wanted to know! If you are interested the rebuilt site can be seen at:http://dignitysa.com
At this point fixing the faulty site is no longer an issue and as JohntheFish correctly pointed out somewhere along the line the site did not get probably updated and now is stuffed.
Thanks for your suggestions, I have learned more about c5 than I wanted to know! If you are interested the rebuilt site can be seen at:http://dignitysa.com
Unfortunately I think that is a step backward. What you have effectively done is told C5 to use an update that has not yet fully installed, so the version of the code it is trying to run is looking for database stuff that does not exist yet.
However, by adding it (and then removing it), you have added to the trail of evidence and eliminated a remote possibility. It shows that the update is failing before it gets as far as adding that line to config/site.php.
However, by adding it (and then removing it), you have added to the trail of evidence and eliminated a remote possibility. It shows that the update is failing before it gets as far as adding that line to config/site.php.
OK, I'm in a similar boat and freaking out. I upgraded to 5.5.2.1 from 5.4.2.2. It said it upgraded. NO DASHBOARD.
I tried upgrading again and it says I've already upgraded to 5.5.2.1
I get NO error message. I just have NO DASHBOARD.
I backed up the site files and database before upgrading. But how to I "Go back" so I can start over????
I tried upgrading again and it says I've already upgraded to 5.5.2.1
I get NO error message. I just have NO DASHBOARD.
I backed up the site files and database before upgrading. But how to I "Go back" so I can start over????
OK, so this gets me to the dashboard, but it still does not show up when I click on back to website. How do I get this fixed?
Are there changes to the template I need to make?
OK, I made some changes to my theme (custom) and now my dashboard is back! yay!
BUT, now in my theme it's pulling up divs that are NOT in my theme. Any ideas on what could be causing this?
BUT, now in my theme it's pulling up divs that are NOT in my theme. Any ideas on what could be causing this?
I now have another site where I can not get a dashboard -- the similar error message. This site is for a well paying client and so far I have managed to update the site without a dashboard but I am skating on very thin ice!!
HELP!!