Fatal error: Class 'ChronoFormsAdmin' not found

I know there are many threads dealing with this error, but I don't have a definitive answer yet. I am running Joomla 2.5, and Chronoforms 4.0 RC2. I tried to install the newest Chronoforms 4 on top of my existing, but it failed. Is there a tutorial for a manual install? Is there anything else I can do to fix this error?

Hi Greg R,

There should normally be no problem installing the current release over an earlier version of CFv4. The error message is from the main admin class in /administrator/components/com_chronoforms/controller.php. It looks as though that file hasn't installed or is corrupted.

This FAQ has a link to a tutorial on manual installation of a component. If that doesn't work you may need to do an manual uninstall - remove all the CF folders, backup the DB tables and remove any ChronoForms entries from the Joomla! components and menus tables. Hopefully you won't need to do that.

Bob

Bob, thanks for your reply, as always. One fine point of distinction, the error is coming from: administrator/components/com_chronoforms/admin.chronoforms.php on line 88. I've checked this file, and it's not missing, or corrupt. This Chrono installation has been running as-is for about a year. Is it possible that a php upgrade caused the issue? I'll look at the manual installation video. After all this time, I wish we had a better idea as to why it happens.

Hi Greg,

Yes, well, one reference is where the class is loaded from and the other is where the load is called from.

A PHP upgrade shouldn't have any effect on this. The only problem we've seen in the 5.2->5.3 upgrade is the introduction of a default value for max_input_vars. That causes problems with saving large or complex forms.

Bob

Just for reference, here is the error I get when I try to do a normal Joomla install over the existing:

500 - An error has occurred.

Installation unexpectedly terminated:

Return to Control Panel

Call stack
# Function Location
1 JAdministrator->dispatch() /var/www/vhosts/website.com/httpdocs/administrator/index.php:46
2 JComponentHelper::renderComponent() /var/www/vhosts/website.com/httpdocs/administrator/includes/application.php:152
3 JComponentHelper::executeComponent() /var/www/vhosts/website.com/httpdocs/libraries/joomla/application/component/helper.php:357
4 require_once() /var/www/vhosts/website.com/httpdocs/libraries/joomla/application/component/helper.php:388
5 JController->execute() /var/www/vhosts/website.com/httpdocs/administrator/components/com_installer/installer.php:22
6 InstallerControllerInstall->install() /var/www/vhosts/website.com/httpdocs/libraries/joomla/application/component/controller.php:754
7 InstallerModelInstall->install() /var/www/vhosts/website.com/httpdocs/administrator/components/com_installer/controllers/install.php:30
8 JInstaller->install() /var/www/vhosts/website.com/httpdocs/administrator/components/com_installer/models/install.php:110
9 JInstallerComponent->install() /var/www/vhosts/website.com/httpdocs/libraries/joomla/installer/installer.php:472
10 JInstallerComponent->update() /var/www/vhosts/website.com/httpdocs/libraries/joomla/installer/adapters/component.php:219
11 JInstaller->abort() /var/www/vhosts/website.com/httpdocs/libraries/joomla/installer/adapters/component.php:834
12 JError::raiseError() /var/www/vhosts/website.com/httpdocs/libraries/joomla/installer/installer.php:417
13 JError::raise() /var/www/vhosts/website.com/httpdocs/libraries/joomla/error/error.php:251500 - An error has occurred.

Installation unexpectedly terminated:

Return to Control Panel

Call stack
# Function Location
1 JAdministrator->dispatch() /var/www/vhosts/website.com/httpdocs/administrator/index.php:46
2 JComponentHelper::renderComponent() /var/www/vhosts/website.com/httpdocs/administrator/includes/application.php:152
3 JComponentHelper::executeComponent() /var/www/vhosts/website.com/httpdocs/libraries/joomla/application/component/helper.php:357
4 require_once() /var/www/vhosts/website.com/httpdocs/libraries/joomla/application/component/helper.php:388
5 JController->execute() /var/www/vhosts/website.com/httpdocs/administrator/components/com_installer/installer.php:22
6 InstallerControllerInstall->install() /var/www/vhosts/website.com/httpdocs/libraries/joomla/application/component/controller.php:754
7 InstallerModelInstall->install() /var/www/vhosts/website.com/httpdocs/administrator/components/com_installer/controllers/install.php:30
8 JInstaller->install() /var/www/vhosts/website.com/httpdocs/administrator/components/com_installer/models/install.php:110
9 JInstallerComponent->install() /var/www/vhosts/website.com/httpdocs/libraries/joomla/installer/installer.php:472
10 JInstallerComponent->update() /var/www/vhosts/website.com/httpdocs/libraries/joomla/installer/adapters/component.php:219
11 JInstaller->abort() /var/www/vhosts/website.com/httpdocs/libraries/joomla/installer/adapters/component.php:834
12 JError::raiseError() /var/www/vhosts/website.com/httpdocs/libraries/joomla/installer/installer.php:417
13 JError::raise() /var/www/vhosts/website.com/httpdocs/libraries/joomla/error/error.php:251

Hi Greg R,


This FAQ has a link to a tutorial on manual installation of a component.

Hi Bob, that video you mentioned (not yours, but the Nutshell video link lower down) is really nothing to do with a manual extension install, but rather how to install an extension from a server directory as opposed to a local directory, which while helpful, still utilizes the installation script, which is not what I need.

I'm going to back up my Chrono files, and start upgrading key files to see if I can resolve the error that way.

In the later version of Chrono 4, you took the functions that were in admin.chronoforms, and moved them over to controller.php. I just upgraded those 2 files, and everything works. So far!

Hi Greg,

Good to see that you got it working.

I don't think that there is a 'manual install' in the sense of do it all by hand :-(

Bo

Well sure😛 :

Step 1, upload all your files to the server

Step 2, run the SQL in the installer on your database with phpmyadmin (that's the dangerous part)

As long as you back up your files, that's fine, but understanding the implications of the database changes can be a challenge. Fortunately, the couple of files seemed to do the trick.