Need help!
Permalink
Have a major problem with concrete5. I recently have been working hard creating a training video for my site's members. I just got the finished the today when I noticed a problem with my site. First, I went to visit the homepage and noticed that it is missing all of the left sidebar content. I went to check in the source code and sure enough the code there is missing too. Thinking the problem may have been related to a recent concrete5 update, I went back and restored to an earlier version and now I cannot log into concrete5. Instead, I get the following message:
An unexpected error occurred.
An error occurred while processing this request.
Then there is a link to take me back to the homepage, but when I click on it, still shows the same message.
btw ... site url is:http://www.thebrazilianlanguage.com,... like I said, there should be content in the left sidebar, but I am not seeing it.
An unexpected error occurred.
An error occurred while processing this request.
Then there is a link to take me back to the homepage, but when I click on it, still shows the same message.
btw ... site url is:http://www.thebrazilianlanguage.com,... like I said, there should be content in the left sidebar, but I am not seeing it.
I restored back to a previous site settings that I created back in December, but I did not have a database backup. Just for the site settings.
I just recently - within the last two days - received the latest update to concrete5. This is why I thought it had to be the problem.
I just recently - within the last two days - received the latest update to concrete5. This is why I thought it had to be the problem.
What do you mean by site settings?
What exact steps did you take?
What exact steps did you take?
I went to dashboard/restore & backup, then tried to restore using the backup site settings file.
If I understand correctly, you have restored an earlier version of the database from December from the admin URL:
/index.php/dashboard/system/backup_restore/backup/
But you are still running the latest version of core files.
Check your /config/site.php file to see if there is a line like this:
You should remove that line from the site.php file and see if that helps.
/index.php/dashboard/system/backup_restore/backup/
But you are still running the latest version of core files.
Check your /config/site.php file to see if there is a line like this:
<?php define('DIRNAME_APP_UPDATED', 'concrete5.6.1.2');?>
You should remove that line from the site.php file and see if that helps.
You might want to check if your hosting provider does full backups regularly and if you can get a copy of a backup form when the site was OK, and revert to that.
In any case, always need to do a full backup (including database) before any update, it even reminds you to do this before the update process begins... Some lessons are learned the hard way. I know this is no consolation, but it is what it is.
Good luck!
In any case, always need to do a full backup (including database) before any update, it even reminds you to do this before the update process begins... Some lessons are learned the hard way. I know this is no consolation, but it is what it is.
Good luck!
I had the same problem when trying to restore an older version of concrete5. Once the updates are installed there is "no backup" for older versions!
As a result I am still having problems adding blocks to my site! Very frustrating!
At best you can ask for restore a back up to a week ago but anything prior to that will incur this error message.
As a result I am still having problems adding blocks to my site! Very frustrating!
At best you can ask for restore a back up to a week ago but anything prior to that will incur this error message.
Removed that line of code and now it appears I am back in business. Was able to get back into the dashboard. So, what about the concrete5 update? when I loggged back in, concrete5 solicited another update. Should I accept or no? since I think my problems originally started with the update.
You just try a manual update method.
1. Backup your database first and download the backup.
2. Download the latest version of concrete5 and upload only the /concrete/ folder from it to your site root. You can first rename the folder for example as concrete5612 so that it won't yet overwrite the current /concrete/ folder.
3. Rename the current /concrete/ folder to /concrete_old/.
4. Rename the just uploaded /concrete5612/ to /concrete/.
5. Open your browser and go tohttp://www.domain.com/index.php/tools/required/upgrade.php... and run the update process.
After the update is finished you should be good to go.
If something goes wrong, you can rename the concrete folders back and do a database restore.
The most important thing is to have a database backup. You can always go back to different core versions easily but you cannot fix a broken database.
1. Backup your database first and download the backup.
2. Download the latest version of concrete5 and upload only the /concrete/ folder from it to your site root. You can first rename the folder for example as concrete5612 so that it won't yet overwrite the current /concrete/ folder.
3. Rename the current /concrete/ folder to /concrete_old/.
4. Rename the just uploaded /concrete5612/ to /concrete/.
5. Open your browser and go tohttp://www.domain.com/index.php/tools/required/upgrade.php... and run the update process.
After the update is finished you should be good to go.
If something goes wrong, you can rename the concrete folders back and do a database restore.
The most important thing is to have a database backup. You can always go back to different core versions easily but you cannot fix a broken database.
I definately will be doing this instead of the conventional update. thanks for the info.
Did you backup your database before you upgraded concrete5 and did you restore also the database when going back?
When you update concrete5, it usually makes also changes to the database so just going back to the previous versions core files is not enough.
When looking at the source code it seems to still be using files from 5.6.1.2 update: