Hi Jens,
Hi Joomshaper Support!
I got a workaround solution with this "dirty" code, runned in PhpMyAdmin SQL!
But this does NOT mean that Joomshaper has not to fix the Bug on their MySQL definition!
#1067 - Incorrect default value (DEFAULT) for 'created_on'.
Here is the quick and dirty fix:
set SQL_MODE = '';
ALTER TABLE `#__sppagebuilder` ADD `content` mediumtext AFTER `text`;
Replaced #_ by my table prefix.
The first line is added so that seems there is no verifcation of the other existing colums any more.
With that, the backend "article" page is loaded.
With a little bit of trying around, but I do not know if this is the solution I edited the tables which were altered in V4.0.0 SQL file too, to the match the acutal MySQL (see for example: https://bugs.mysql.com/bug.php?id=94062) But there are more tables which I think have to be corrected!
Also with command
set SQL_MODE = '';
before
ALTER TABLE `jos_spmedia` MODIFY `created_on` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP;
ALTER TABLE `jos_spmedia` MODIFY `modified_on` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP;
ALTER TABLE `jos_sppagebuilder` MODIFY `created_on` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP;
ALTER TABLE `jos_sppagebuilder` MODIFY `modified` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP;
ALTER TABLE `jos_sppagebuilder` MODIFY `checked_out_time` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP;
ALTER TABLE `jos_sppagebuilder_sections` MODIFY `created` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP;
ALTER TABLE `jos_sppagebuilder_addons` MODIFY `created` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP;
After this change I can execute the following
ALTER TABLE `jos_sppagebuilder` ADD `content` mediumtext NOT NULL AFTER `text`;
The SQL Files from the installation file also do not have the NOT NULL arguements.
The line before text
mediumtext NOT NULL has it. Did you forget it for the content column?