Feng Office 2.0.0.8 - Stable -NEW INSTALL PROBLEM

[cooltop]

When I try to setup Feng office 2.0.0 Stable  I get
Failed to import initial data. MySQL said: Data truncated for column 'type' at row 7


This is from a clean install of Apache, MySql and PHP all updated versions.



1.7.5 version installs with no problems.

[piter]

I've got similar problem, but I'm upgrading from 1.7.5 to 2.0.0.8.
My error is:
Failed to execute DB schema transformations. MySQL said: Data truncated for column 'type' at row 7

Version 1.7.5 is working without any problems.

[Angelos]

I've got similar problem, but I'm upgrading from 1.7.5 to 2.0.0.8.
My error is:
Failed to execute DB schema transformations. MySQL said: Data truncated for column 'type' at row 7

Version 1.7.5 is working without any problems.

Yeap we to have the same problems with the upgrade from 1.7.5 and we did change the db table prefix to fo_ but with the same results!

Any help will be greatly appreciated!

[bgbearcatfan]

Has anyone come up with a resolution for this error?  We are experiencing the same issue and have been unable to solve it.

[bgbearcatfan]

In case it helps anyone...

If i mainly configure the config.php file as well as manually run the two mysql scripts found in the installation folder, it works.  However now i'm greeted with an error message when logging in saying i need to manually create the workspace first.  SO getting closer....

[palenholik]

I resolved the issue by changing MYSQL mode in my.ini, like this.
1. Open my.ini and find "sql-mode"
2. Comment current settings by putting # key in fornt
3. Set new mode "sql-mode=MYSQL40"
4. Save and Restart MYSQL server,
5. finish Feng Office installation and return previous MYSQL mode.

All works fine...

[pkjha30]

Had a similar problem with Version 2.2.3 beta  and previous version. The solution suggested above actually worked..

I did as suggested


# Set the SQL mode to strict For fengoffice Installation change mode
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

#sql-mode="MYSQL40"

Thanks  But developer should really find the issue here. It was not there in Version 1.7.5 . Perhaps related to mysql  4 and 5.

[franponce87]

Hello there!
Which OS are you using? Which MySQL version?

Thanks!

Best regards,
Francisco

[HansDeV]

the problem is located in the field type of the table fo_object_types
the field  type is defined as

enum('content_object','dimension_object','dimension_group', 'located', 'comment')

This should be :

enum('content_object','dimension_object','dimension_group', 'located', 'comment','')

An empty string should be allowed as a possible value, as the field contains '' for 2 of the records in version 1.7.5

in version 2.2.4 , it can be found in
public/install/installation/templates/sql/sql_schema.php , line 140