Feng Forum

Support => How To's => : Mist. GraphX October 28, 2010, 06:47:35 AM

: [SOLVED] Some questions about a future release and actual bugs
: Mist. GraphX October 28, 2010, 06:47:35 AM
hi,

i use FengOffice for my work everyDay and i want to say first that it's really a great app so thanks for developping it !!

Since the 1.7.1 and after 1.72 release i've experience some bugs in my instalation of FO : new tabs created at launch with error message, no more e-mails or account witch appeared , imposible to create new task in the task tab, and today i've discover that it's impossible for me to modify a contact... i've post  bugs report  but i'would like to know if i'm the only one with these problems, or when a new version correcting these bugs 'll comming.

i'm really sorry to  insist , but it's begin to be annoying for my work and just want to know if a fresh new install could resolved my problems...

thx for your answers
: Re: Some questions about a future release and actual bugs
: supadoctor October 28, 2010, 10:18:24 AM
The topic is very actual and timely.

FO is a good software but like any others free software the support is a weakness. And everyone should understand it before using a free product.

But I think today is a good time to ask yourself: "how I can support the project?"

As for me I sent some money to sponsor WebDAV feature.

Maybe others FO users join me and make some donation for necessary things too?

No need to pay all sum displayed here http://www.fengoffice.com/web/community/sponsor-feature.php But you can communicate with FO admins and find reasonable sum for you.
: Re: Some questions about a future release and actual bugs
: Mist. GraphX October 28, 2010, 11:09:17 AM
Totaly agree with your answer, and know exactly what using an free product is : thats why i prefer to use an existing project and contribute by bugs return, or something else (promote, helping users by teaching them,posting answers in forum's when i can), than creating forks or changing the software i use without discusions :)
In my opinion free software exist with the community of users just because if no one use it or need it... it don't have to exist even if it's free.

Anyway, i wrote this post first to know if my feng office install is corrupt or if someone have the same problems  before trying to make a new install and importing old corrupts data ... that's all (money can do something for that ????)

thank for your answer
: Re: Some questions about a future release and actual bugs
: Mist. GraphX October 29, 2010, 12:09:18 PM
ok thanks for all your answers !!! Community spirit is really impressive here ;-)
So i answer to me : A new fresh instal of FO works well , but the update failed !!! Why ..

i've solved my problems and my instalation of feng office works well ;-) so if someone is interested : i CONTRIBUTE by giving the way and my conclusions

The update of the tables is corrupted when you make a comparaison between shema there is no update or a bug in the SQL update shema

1/ the first time i install FO i've choose MylSAAM engine (maybe the basic bug source is here) ... new tables are created in innodb even if it's specified in config file MylSAAM :/ first update bug. for example in my installation the og_administration_logs was in innodb engine and the other tables where in MylSAAM

so i've convert the engine of all my tables :
How ? Command lines in a  shell :
mysqldump -hHOST -uUSER -pPASS DataBase > file.sql

convert MylSAAM > InnoDB
sed -i .new 's/ENGINE=MylSAM/ENGINE=InnoDB/g' /path/to/fengoffice.sql

quick and sure ;-) don't try with phpMyAdmin or a text editor i've lost time by trying this with a 13M database , command line take 3 seconds to do the job

2/ The mail tables are not updated and fields are not present in the instalation :
og_user_account  table : missing fields
last_error_date
last_error_msg
sync_addr varchar
sync_pass
sync_server
sync_ssl
sync_ssl_port
sync_folder

i've made a SQL update of this table manualy in phpMyAdmin :

DROP TABLE IF EXISTS `og_mail_accounts`;
CREATE TABLE `og_mail_accounts` (
  `id` int(10) unsigned NOT NULL auto_increment,
  `user_id` int(10) unsigned NOT NULL default '0',
  `name` varchar(40) collate utf8_unicode_ci NOT NULL default '',
  `email` varchar(100) collate utf8_unicode_ci default '',
  `email_addr` varchar(100) collate utf8_unicode_ci NOT NULL default '',
  `password` varchar(40) collate utf8_unicode_ci default '',
  `server` varchar(100) collate utf8_unicode_ci NOT NULL default '',
  `is_imap` int(1) NOT NULL default '0',
  `incoming_ssl` int(1) NOT NULL default '0',
  `incoming_ssl_port` int(11) default '995',
  `smtp_server` varchar(100) collate utf8_unicode_ci NOT NULL default '',
  `smtp_use_auth` int(10) unsigned NOT NULL default '0',
  `smtp_username` varchar(100) collate utf8_unicode_ci default NULL,
  `smtp_password` varchar(100) collate utf8_unicode_ci default NULL,
  `smtp_port` int(10) unsigned NOT NULL default '25',
  `del_from_server` int(11) NOT NULL default '0',
  `outgoing_transport_type` varchar(5) collate utf8_unicode_ci NOT NULL default '',
  `last_checked` datetime NOT NULL default '0000-00-00 00:00:00',
  `is_default` tinyint(1) NOT NULL default '0',
  `signature` text collate utf8_unicode_ci NOT NULL,
  `workspace` int(10) NOT NULL default '0',
  `sender_name` varchar(100) collate utf8_unicode_ci NOT NULL default '',
  `last_error_date` datetime NOT NULL default '0000-00-00 00:00:00',
  `last_error_msg` varchar(255) collate utf8_unicode_ci NOT NULL,
  `sync_addr` varchar(100) collate utf8_unicode_ci NOT NULL,
  `sync_pass` varchar(40) collate utf8_unicode_ci NOT NULL,
  `sync_server` varchar(100) collate utf8_unicode_ci NOT NULL,
  `sync_ssl` tinyint(1) NOT NULL default '0',
  `sync_ssl_port` int(11) NOT NULL default '993',
  `sync_folder` varchar(100) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`id`),
  KEY `user_id` (`user_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ;

3/ og_searchable_objects is not added when you update from an older version (in my case)
 create this table with this sql command in phpMyAdmin :

--
-- Structure de la table `og_searchable_objects`
--

CREATE TABLE `og_searchable_objects` (
  `rel_object_manager` varchar(50) collate utf8_unicode_ci NOT NULL default '',
  `rel_object_id` int(10) unsigned NOT NULL default '0',
  `column_name` varchar(50) collate utf8_unicode_ci NOT NULL default '',
  `content` text collate utf8_unicode_ci NOT NULL,
  `project_id` int(10) unsigned NOT NULL default '0',
  `is_private` tinyint(1) unsigned NOT NULL default '0',
  `user_id` int(10) unsigned NOT NULL default '0',
  PRIMARY KEY  (`rel_object_manager`,`rel_object_id`,`column_name`),
  KEY `project_id` (`project_id`),
  FULLTEXT KEY `content` (`content`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

update the  `og_mail_account_users` : missing field last_error_state


DROP TABLE IF EXISTS `og_mail_account_users`;
CREATE TABLE `og_mail_account_users` (
  `id` int(10) NOT NULL auto_increment,
  `account_id` int(10) NOT NULL,
  `user_id` int(10) NOT NULL,
  `can_edit` tinyint(1) NOT NULL default '0',
  `is_default` tinyint(1) NOT NULL default '0',
  `signature` text collate utf8_unicode_ci NOT NULL,
  `sender_name` varchar(100) collate utf8_unicode_ci NOT NULL default '',
  `last_error_state` int(1) unsigned NOT NULL default '0' COMMENT '0:no error,1:err unread, 2:err read',
  PRIMARY KEY  (`id`),
  UNIQUE KEY `uk_useracc` (`account_id`,`user_id`),
  KEY `ix_account` (`account_id`),
  KEY `ix_user` (`user_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ;

update the 'og_mail_content' table missing sync field

--
-- Structure de la table `og_mail_contents`
--

DROP TABLE IF EXISTS `og_mail_contents`;
CREATE TABLE `og_mail_contents` (
  `id` int(10) unsigned NOT NULL auto_increment,
  `account_id` int(10) unsigned NOT NULL default '0',
  `uid` varchar(255) collate utf8_unicode_ci NOT NULL default '',
  `from` varchar(100) collate utf8_unicode_ci NOT NULL default '',
  `from_name` varchar(250) collate utf8_unicode_ci default NULL,
  `sent_date` datetime NOT NULL default '0000-00-00 00:00:00',
  `received_date` datetime NOT NULL default '0000-00-00 00:00:00',
  `subject` varchar(255) collate utf8_unicode_ci NOT NULL default '',
  `has_attachments` int(1) NOT NULL default '0',
  `size` int(10) NOT NULL default '0',
  `state` int(1) NOT NULL default '0' COMMENT '0:nothing, 1:sent, 2:draft',
  `is_deleted` int(1) NOT NULL default '0',
  `is_shared` int(1) NOT NULL default '0',
  `is_private` int(1) NOT NULL default '0',
  `created_on` datetime default NULL,
  `created_by_id` int(10) unsigned NOT NULL default '0',
  `trashed_on` datetime NOT NULL default '0000-00-00 00:00:00',
  `trashed_by_id` int(10) unsigned default NULL,
  `imap_folder_name` varchar(100) collate utf8_unicode_ci NOT NULL default '',
  `account_email` varchar(100) collate utf8_unicode_ci default '',
  `content_file_id` varchar(40) collate utf8_unicode_ci NOT NULL default '',
  `archived_on` datetime NOT NULL default '0000-00-00 00:00:00',
  `archived_by_id` int(10) unsigned default NULL,
  `message_id` varchar(255) collate utf8_unicode_ci NOT NULL COMMENT 'Message-Id header',
  `in_reply_to_id` varchar(255) collate utf8_unicode_ci NOT NULL COMMENT 'Message-Id header of the previous email in the conversation',
  `conversation_id` int(10) unsigned NOT NULL default '0',
  `sync` int(1) NOT NULL default '0',
  PRIMARY KEY  (`id`),
  KEY `account_id` (`account_id`),
  KEY `sent_date` (`sent_date`),
  KEY `received_date` (`received_date`),
  KEY `uid` (`uid`),
  KEY `conversation_id` (`conversation_id`),
  KEY `message_id` (`message_id`),
  KEY `state` (`state`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ;


Thats all folks ;-) it works fine for me , i've all my e-mails, i can modify my account, all bugs have desapeared ;-)

sorry if my english is not really good, hope it could help someone
i can writte this in french for helping french users if necessary

@supaDoctor : is it a contribution ??? :)




: Re: [SOLVED] Some questions about a future release and actual bugs
: supadoctor October 29, 2010, 05:21:15 PM
@supaDoctor : is it a contribution
definitely!!!

I'll check your solution and give a feedback ASAP.
: Re: [SOLVED] Some questions about a future release and actual bugs
: Mist. GraphX October 30, 2010, 05:22:42 AM
:) if it could help !

i've forgot something : first i've copy all the instalation of FO on my computer, :) more sure and quick than working on the web server ...
: Re: [SOLVED] Some questions about a future release and actual bugs
: franponce87 November 01, 2010, 03:34:36 PM
Hello! Totally agree with supadoctor's post. We are glad you both understand our position :)

There apparently are some problems in the script that modifies the database to the 1.7.2 schema, and this has been affecting several users.

Regarding the engine, it would be best if you use the InnoDB one
You may also check if there is a 'sync' field in MailContents.. if it is not, it is missing as well!


Best regards,
Francisco

: Re: [SOLVED] Some questions about a future release and actual bugs
: Mist. GraphX November 02, 2010, 05:46:54 AM
thx ;) i add the missing field 'sync' too. Mail seems to work well now, i've clean the database mail_content and create a new account for ...

The innoDB engine is quite slow on my server, it's a Synology NAS DS209 thats why i first choose the MylSAMM engine.

i've just a problem with search form , i've no result think the table searchable_object is corrupt whith all the manipulations i've done :)

: Re: [SOLVED] Some questions about a future release and actual bugs
: franponce87 November 02, 2010, 08:19:58 AM
No problem!
Just in case, the Searchable objects table has the following attributes:

rel_object_manager
rel_object_id
column_name
content
project_id
is_private
user_id

Best regards,
Francisco
: Re: [SOLVED] Some questions about a future release and actual bugs
: jckresq November 28, 2010, 09:44:53 AM
Thank you!!! - FIXED my problem which was exactly the same since the upgrade.  :)