Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - apmuthu

Pages: 1 [2]
Espaņol / Re: Fatal error: Class 'DB'
« on: December 26, 2012, 02:42:08 PM »
You have not uploaded the fengoffice files to your webroot properly and permissioned them correctly. look for what your webroot is.

Check if the config/config.php file is there and it has the necessary details.

Feng Office 2 / FO v2.2.1 OpenVZ Template Released
« on: December 26, 2012, 02:23:43 PM »
The Debian Squeeze OpenVZ Template of FengOffice 2.2.1 - auto pre-installed at first boot - fully randomised MySQL passwords and application hashes / Seeds is now available.

Contact (GNUAcademy) for the template and (Planettel) for Support. It has all issues addressed till date.

The template is listed at the ProxmoxVE site -

Installation problems / Missing entries in config/config.php
« on: December 26, 2012, 01:09:44 PM »
On FengOffice v2.2.1 installation, the generated config/config.php has 14 defines against only 11 in the config/empty.config.php - the Missing ones in it are:

define('DB_ENGINE', 'InnoDB');
define('COOKIE_PATH', '/');
define('SEED', '13312cdd121facd0bef7635bacbd5303');

The last SEED value is computed using:
This detail is in line 147 of public/install/installation/acInstallation.class.phpand public/install/installation/plugin_acInstallation.class.php

Undocumented defines available:

Installation problems / Invalid Admin EMail ID accepted during install
« on: December 26, 2012, 01:04:20 PM »
During installation, in the final step we can enter any name instead of an email id and the install will finish successfully without checking if it has a valid email format or not.

However, we cannot login with the given credentials as the email id format is checked during login.

The fix is to manually correct it in the database table contact_emails table.

Installation problems / Upgrade Fix
« on: December 26, 2012, 01:36:56 AM »
The line 307 of file public\upgrade\scripts\NutriaUpgradeScript.class.php

            $new_config[] = "  define('SEED', '".DB_USER.DB_PASS.rand(0,10000000000)."');\n";

should be

            $new_config[] = "  define('SEED', '".md5(DB_USER.DB_PASS.rand(0,10000000000))."');\n";

Installation problems / Redundant Indexes
« on: December 26, 2012, 12:09:00 AM »
In Feng Office v2.2.1, there are quite a few redundant indexes and a missing Unique index that can be set right with (my db table extension is fo_):

Redundant Key issues:

ALTER TABLE `fo_contact_passwords` DROP INDEX `id`;
ALTER TABLE `fo_contact_permission_groups` DROP INDEX `contact_id`;
ALTER TABLE `fo_object_types` DROP INDEX `name`,
      ADD UNIQUE INDEX `nameclass` (`name`, `handler_class`, `table_name`);
ALTER TABLE `fo_searchable_objects` DROP INDEX `rel_obj_id`;
ALTER TABLE `fo_mail_account_contacts` DROP INDEX `ix_account`;

When ever a field is the first one in a Primary key or in any unique key, it should not be used as a key by itself as it would be redundant.

An additional or exclusive solution can be:

Better still, fix the original schema for the base install as well:
ALTER TABLE `fengoffice`.`fo_object_types` ADD INDEX `nameclass` (`name`, `handler_class`, `table_name`);

This code in the base schema should be in:
by inserting at line 145:
  KEY `nameclass` (`name`,`handler_class`,`table_name`),

"Error while loading inital data for plugin 'mail'. Subquery returns more than 1 row"

The string Error while loading inital data for plugin is found in:

  • public/install/installation/plugin_acInstallation.class.php (Line 710)
  • public/install/installation/acInstallation.class.php (Line 670)

One is used during the install of plugins at initial setup time and the other thereafter.
Both have the function installPlugins() defined in them at line 556.
Lines are 596-624 in the former and 580-607 in the latter are where plugin define types are first inserted.

The location of the SQL statement that raises the error is at
referred to in lines 702 and 663 respectively.

SELECT * FROM fo_object_types WHERE `name`='mail'; // plugin_id=4 yields 2 rows:

id   name   handler_class   table_name   type   icon   plugin_id
21   mail   MailContents   mail_contents   content_object   mail   4
22   mail   MailContents   mail_contents   content_object   mail   4

fo_plugins table does not have id=2.
fo_object_types does not have id=7.
fo_object_types id from 1 to 18 have plugin_id=NULL.

The error arises during the execution of the first SQL statement in :

The record was already inserted when plugin define types are installed.
The mail plugin define types are taken from lines 10-20 in:

In general, you should try to avoid using an ON DUPLICATE KEY UPDATE clause on tables with multiple unique indexes.
The table fo_object_types has multiple indexes and the non-primary keys are not declared unique - not even in combination.

The solution:
Since any mail plugin install inserts the define types taken from plugins/mail/info.php, the first SQL statement can be deleted in

New Community Members / Hello from Chennai, India / Singapore
« on: March 07, 2010, 08:39:04 AM »
Greetings from Singapore and Chennai, India.

Nice community!

Why did OpenGOO change to FengOffice?
Was it because of the GOO or did China buy it up!

The default posting setting is centered instead of left justified - the Board Admin can change it so new users can benefit.

The latest version of OpenGOO - 1.6.2 - has been made available as an OpenVZ template for direct deployment in a container - check out the ProxMox Wiki Page for it here.

Dont forget to fix the bug listed in this forum posting.

Older versions / Re: DataObject->validateMaxValueOf($column, $max) bug
« on: March 07, 2010, 08:10:49 AM »
Yes you are right. The current v1.8 of the said file in the CVS has the error only in line 1115:
Code: [Select]
    if(is_int($value) || is_float($column)) {
should be
Code: [Select]
    if(is_int($value) || is_float($value)) {
Hope the admin will update the repository. The previous 2 diffs are merely adding of a blank line and changing of version number!

Older versions / User Deletion by admin incomplete
« on: March 07, 2010, 07:46:07 AM »
When the admin deletes a user, the user is deleted from the og_users table (the autoincrement is unaltered) but the user's records in the og_user_passwords table remain undeleted.

How To's / How do we disable a user without deleting the user
« on: March 07, 2010, 07:33:09 AM »
Sometimes we need to temporarily disable a user from logging in. Other than mangling the password - how do we disable the user?

Pages: 1 [2]