After the upgrade from Joomla 2.5.28 to 3.4.1 I upgraded also Chronoforms from 4 RC to 4.0.6.
After the Chronoforms Update I get the following message in the Joomla Backend:
1054 Unknown column 'app' in 'field list' SQL=SELECT DISTINCT app FROM uump6_chronoforms
I can not open the component. The installation is running on PHP 5.3, there are no Database errors.
What can I do to reselve this problem?
Thank you very much!
After the Chronoforms Update I get the following message in the Joomla Backend:
1054 Unknown column 'app' in 'field list' SQL=SELECT DISTINCT app FROM uump6_chronoforms
I can not open the component. The installation is running on PHP 5.3, there are no Database errors.
What can I do to reselve this problem?
Thank you very much!
Hi webhand.
Hmm. I haven't seen this error before. If you are OK with PHP MyAdmin you can add the column
Or you could backup all of the form and both the #_chronoforms and #_chronoform_actions tables; then uninstall ChronoForms and re-install the latest version of CFv4 for Joomla! 3; then restore the forms.
Bob
Here is the create statement for the #_chronoforms table on my test site.
Hmm. I haven't seen this error before. If you are OK with PHP MyAdmin you can add the column
`app` varchar(100) NOT NULL DEFAULT '',
Or you could backup all of the form and both the #_chronoforms and #_chronoform_actions tables; then uninstall ChronoForms and re-install the latest version of CFv4 for Joomla! 3; then restore the forms.
Bob
Here is the create statement for the #_chronoforms table on my test site.
CREATE TABLE `#_chronoforms` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`name` varchar(255) NOT NULL,
`form_type` tinyint(1) NOT NULL,
`content` longtext NOT NULL,
`wizardcode` longtext,
`events_actions_map` longtext,
`params` longtext NOT NULL,
`published` tinyint(1) NOT NULL DEFAULT '1',
`app` varchar(100) NOT NULL DEFAULT '',
PRIMARY KEY (`id`)
) ENGINE=MyISAM AUTO_INCREMENT=146 DEFAULT CHARSET=utf8
Hello Bob
Thanks a lot for your help. 😀
I restored the old installation 2.5.28, backed up the form, then restored the Backup from the 3.4.1 installation,
uninstalled ChronoForms, installed the latest ChronoForms V4, and restored the Backup from the old form.
Now everything works well again. Thanks!
Thanks a lot for your help. 😀
I restored the old installation 2.5.28, backed up the form, then restored the Backup from the 3.4.1 installation,
uninstalled ChronoForms, installed the latest ChronoForms V4, and restored the Backup from the old form.
Now everything works well again. Thanks!
This topic is locked and no more replies can be posted.
