Support

Akeeba Backup for Joomla!

#34897 com_cmsupdate error after restoring Akeeba Backup file

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by on Wednesday, 21 April 2021 20:17 CDT

Friday, 19 March 2021 00:20 CDT

chicagogregg

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!


EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.


Description of my issue:

 

The scenario:

* Had a staging area which I cloned my PROD over to. I used this area to work on everything. I upgraded ALL extensions (on both staging and prod) to latest versions and Joomla! to latest (3.9.25).

* Created an Akeeba backup from staging (All configured DB's minus a few customized tables of my own)

* Restored onto PROD environment

* Had an issue with FOF and unable to access backend. Found the KB article on Akeeba site, followed instructions, got it working again, reinstalled Akeeba Backup (twice, per KB)

* Going through other components to validate they are working properly

* The Akeeba com_cmsupdate gives an error "500 - Layout admin:com_cmsupdate/cpanels/default not found."

 

The only thing I found about this issue is something in the KB from 2013 but no responses/fixes.

 

Is this part of the Akeeba Backup? I don't believe I've actually ever used Akeeba CMS.

Example URL is: https://www.domaingoeshere.org/administrator/index.php?option=com_cmsupdate&view=cpanel

 

Is there a fix for this?

Thanks in advance.

Edited by on 2021-04-21 20:45 CDT

Friday, 19 March 2021 02:44 CDT

nicholas

We discontinued Akeeba CMS Update in 2016. This was a stopgap solution because Joomla wouldn't let us provide some much needed improvements to Joomla! Update, the component we had contributed to Joomla! in 2011 (Joomla 2.5.1). In 2015 we worked with the Joomla project to include these improvements. The Joomla project also implemented a major change allowing the Joomla Update component to be updated before Joomla itself, in case a major issue was detected, rendering Akeeba CMS Update obsolete. So we deprecated it and discontinued it within 6 months.

Please uninstall Akeeba CMS Update. It wouldn't even work correctly with Joomla 3.7 and later as it's never been updated for it..

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 19 March 2021 21:47 CDT

chicagogregg

Perfect. Thanks Nicholas. I've uninstalled it. That's sort of what I figured. It shows how long my web site has been around I guess! And how long I've been with Akeeba.

Could you tell me if the same applies to the below?

1. AkeebaStrapper from 2015/2016

2. "F0F (NEW) DO NOT REMOVE)" from 2016-05-12

3. FOF v2.2.1 from 2014-03-09  (Note there is also FOF v2.4.3 (this is protected and can't be uninstalled - which is fine))

4. "JMonitoring - Akeeba Backup" v1.0 from May 2012

 

FOF may have originally caused me not to be able to get back into my site after an Akeeba recovery, but I got that taken care of.

 

Thanks!

Monday, 22 March 2021 00:05 CDT

nicholas

Items 1 and 2, Akeeba Strapper and F0F (f zero f): We have not used either of these in our software since 2015. However, third party extensions may still be using them. Try disabling them before uninstalling them and see if anything breaks. 

Item 3: This is a very old version of FOF we stopped developing in May 2015 and discontinued in June 2016. It is still shipped with Joomla 3.2 to 3.10 inclusive. DO NOT REMOVE, THAT WOULD BREAK YOUR SITE. Note that it's in libraries/fof (f oh f) on your site. Do not remove that folder, it will break your site.

Item 4. This is a discontinued plugin, you can remove it. The JMonitoring extension was discontinued when they were absorbed by Anything Digital and formed the Watchful service back in late 2012. 

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Wednesday, 21 April 2021 20:17 CDT

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
Edited by on 2021-04-21 20:17 CDT

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!