Forums

Joomla 3.7.5; PHP 7.0; Apache2

When within the Forms Manager and choosing Blocks, results in the error:

1146 Table 'XXXXXXX.#__chronoengine_forms6_blocks' doesn't exist

Hi Arthur,

This is a known bug with the Joomla updater. I think that Max has now published an updated version so it should be fixed. If not you can download the latest version from here and install that to do the update.

Bob

Same proble here, solved installing the latest version downloades from here.

Thanks😉

Hello,

You may also click the "Apply updates" button in the latest update when in the forms manager!

Best regards,
Max

Update 6.0.7 to 6.0.9 (last build) error is still showing. For version 6.0.7, everything was fine.

What is the error and where does it show please ?

Best regards,
Max

Update 6.0.7 to 6.0.9 (last build) error is still showing. For version 6.0.7, everything was fine.

Install the update manually. Download here on the web.
The Joomla update shows an update to version 6.0.9. I feel that the update number is wrong and it is an old version with a bug.

I had the same problem, and solved updating manually. thanks!

I also had the same error with the automatic update from chronoengine server.

1146 Table 'xxxxxxxxxxx. # __ chronoengine_forms6_blocks' does not exist

Everything came back ok with download version 6.0.9 package and manual update.

just updated to the latest version and get same error. Allready a solution availble? Can i just create the table manually?

just updated to the latest version and get same error. Allready a solution availble? Can i just create the table manually?

Download package v 6.0.9 and manually install it from joomla backend.

Hi,
I have the same problem and when i try to update component cf6 or cc6 i have :

Alerte
Le chemin de mise à jour n'existe pas
Message
COM_INSTALLER_TYPE_TYPE_ : erreur de mise à jour.

Update cf6 and twice work well...

I you update cc6.0.4 component crashes, white page : you have to re-install cf6

Hi Christophe,

Yes, CF should be always installed last.

The other error was caused by some issue at the update path and should now be fixed!

Best regards

ok
thanks