Joomla 5 Notice

We are pleased to announce that as of January 29, 2024, all of our Joomla extensions are compatible with Joomla 5.

For all who are still updateing from Joomla 3 to Joomla 4: Joomla 4 Migration instructions are available here:

There is now a separate Documentation for Visforms for Joomla 4 and for Visforms for Joomla 5!

Forum

Visforms Subscription user can ask questions in our forum. Please log in with the relevant user first.
Everybody can access the forum for reading.

Please only ask 1 question per topic.

Important information for almost every question:
V1: Which Visforms version is running?
V2: Which Joomla version is running?
V3: Which PHP version is running?

Visforms, "Column checked_out can not be null"

  • Bronco
  • Topic Author
  • Away
More
1 week 5 days ago - 1 week 5 days ago #10915 by Bronco
Visforms V5.1.2
Joomla V5.2.1
PHP V8.2

Problem nr 1:
In admin side I click Data of a form to edit. Then when I ONLY click the Close-button, NOT Save & Close-button, I get that error. It works when I use the Save & Close-button.
I can also view the details without problems.

Problem nr 2:
In Frontpage and trying to edit I get 404 Page not found. But that is only for one form. Other forms works.
I tried to edit in admin side and saved and tried again to open the same data in Frontpage but still gets the same error.


Both of these problems is for the same form I setup and it worked earlier as it should before I updated Visforms. It works on the others forms I have without any problems. Before update I installed vfsubscription_j4.0.0_4.4.3.zip

/Thomas
Last edit: 1 week 5 days ago by Bronco.

More
1 week 2 days ago #10916 by Administrator IV
Replied by Administrator IV on topic Visforms, "Column checked_out can not be null"
Hello Thomas,

the error '1048 Column checked_out cannot be null' was a known error in earlier versions.
It does not occur on any other Visforms installation.

When updating to the latest Visforms versions, SQL statements are run and the Visforms tables are adjusted accordingly.
The error is then resolved.

If these SQL statements did not run successfully for you, for whatever reason, you can try to run the SQL statements manually afterwards.
Run the following SQL statements in one go:
Code:
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET time_zone = "+00:00"; ALTER TABLE `#__visforms` modify checked_out int unsigned null; ALTER TABLE `#__visforms` modify checked_out_time datetime null; ALTER TABLE `#__visfields` modify checked_out int unsigned null; ALTER TABLE `#__visfields` modify checked_out_time datetime null; ALTER TABLE `#__vispdf` modify checked_out int unsigned null; ALTER TABLE `#__vispdf` modify checked_out_time datetime null;

The two SQL statements
Code:
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET time_zone = "+00:00";
are only sometimes necessary under certain database server settings.
In most cases they are not absolutely necessary.

Adaptation to your database:
Change the following into the above SQL statements.
#__ --> Your Joomla table name prefix.

The error should then be resolved.

Best regards, Ingmar

:idea: I recommend you the new and up-to-date documentation for Joomla 4:
docs.joomla-5.visforms.vi-solutions.de/en/docs/
Most of this also applies retrospectively to Joomla 3.
Please only ask 1 question per topic :-).

:idea: Ich empfehle Dir die neue und aktuelle Dokumentation für Joomla 4:
docs.joomla-5.visforms.vi-solutions.de/docs/
Das meiste gilt rückwirkend auch für Joomla 3.
Bitte immer nur 1 Frage pro Thema stellen :-).

  • Bronco
  • Topic Author
  • Away
More
1 week 2 days ago #10917 by Bronco
Hi, nope didn't work. Same errors. I saw the same errors report in this forum earlier but that seemed to work when the user clicked Save & Close-button. For me it happens only when I click the Close-button.

  • Bronco
  • Topic Author
  • Away
More
1 week 2 days ago #10918 by Bronco
Hi again.

It did work. I just hade to change all the "#__visforms_*" too :P

More
1 week 2 days ago #10919 by Administrator IV
Replied by Administrator IV on topic Visforms, "Column checked_out can not be null"
Hello Thomas,

I'm very happy that it worked.

Both processes and error messages mentioned here lead back to the same fact that 'null' values ??were suddenly allowed in the affected field during Joomla development (Joomla 4).
By explicitly allowing 'null' values ??in the table design, this fact is taken into account.
The SQL statements usually do this automatically with a total of 6 Visforms tables during the update.

Could you perhaps briefly list at least one of your changed final SQL statements here?
Simply so that it is clear what exactly you have changed and how?

Best wishes, Ingmar

:idea: I recommend you the new and up-to-date documentation for Joomla 4:
docs.joomla-5.visforms.vi-solutions.de/en/docs/
Most of this also applies retrospectively to Joomla 3.
Please only ask 1 question per topic :-).

:idea: Ich empfehle Dir die neue und aktuelle Dokumentation für Joomla 4:
docs.joomla-5.visforms.vi-solutions.de/docs/
Das meiste gilt rückwirkend auch für Joomla 3.
Bitte immer nur 1 Frage pro Thema stellen :-).

  • Bronco
  • Topic Author
  • Away
More
1 week 1 day ago - 1 week 1 day ago #10928 by Bronco
Sure,

First I did what you wrote. Then this:
Code:
ALTER TABLE `d70do_visforms_2` modify checked_out int unsigned null; ALTER TABLE `d70do_visforms_2` modify checked_out_time datetime null; ALTER TABLE `d70do_visforms_8` modify checked_out int unsigned null; ALTER TABLE `d70do_visforms_8` modify checked_out_time datetime null;

And so on.
I probably didn't need to change all the forms I had since it was only one that "malfunctioned".

/Thomas
Last edit: 1 week 1 day ago by Bronco.
The following user(s) said Thank You: Administrator IV

Moderators: Administrator AVAdministrator IV
Powered by Kunena Forum