Messages

1

Feng Office 2 / Re: Data is saved but disappears! - Workspace Permissions Problem

« on: May 25, 2013, 02:41:28 pm »

Dear Arthur,

If you already have this annoying bug, upgrading to 2.3 will not resolve the problem

However, if you can afford a clean installation, using 2.2.4.1 or later does not have this bug any more.

Regards,
Alex

2

Feng Office 2 / Re: Data is saved but disappears! - Workspace Permissions Problem

« on: April 04, 2013, 06:04:00 pm »

Updating PHP to a newer version did not solve the problem in my case. I don't know whether the version of PHP was what caused it initially or a bug in the upgrade process from FO 2.2.1 to 2.2.2, but once you have it, it keeps propagating.

As has already been mentioned in the thread titled "FO 2.2.2 - Workspace and group permissions problem", the problem does not seem to exist any longer in a clean installation of version 2.2.4.1. Hopefully, the source of the problem will be discovered and dealt with in the future.

3

Feng Office 2 / Re: FO 2.2.2 - Workspace and group permissions problem

« on: April 04, 2013, 05:52:34 pm »

Dear Francisco,

No, I did not use FO 1.x. The initial version was 2.0.0 (2.0.0.8 stable). Well, if you can find out what went wrong in the update from FO 2.2.1 to 2.2.2 and fix it in one of the future upgrade scripts, that would be fine.

I tried creating new users and/or groups, but it didn't make any difference. Making everyone an admin did not work either. It seems that there is no way to avoid the repeated update in the group permissions :/

By the way, offering to share my DB structure with you was not meant to be a "personal service" request, but rather to help you track down the source of the problem. It is then up to you whether and how you will make use of it. Can't demand much for something given for free


Regards,
Alex

4

Feng Office 2 / Re: FO 2.2.2 - Workspace and group permissions problem

« on: April 04, 2013, 01:48:35 pm »

Francisco, you are right!

I just tested it on a clean installation of FO 2.2.4.1 on Windows with XAMPP (PHP 5.4.4) and the problem no longer occurs.

I initially noticed it on an Ubuntu installation with PHP 5.3.6-13ubuntu3.10, when upgraded from FO 2.2.1 to 2.2.2 and persists until the currently latest version (2.2.4.1).

I took a DB backup of a problematic installation, loaded it locally on the aforementioned XAMPP system and the problem is still there. Hence, it seems that it most probably is a bug in FO 2.2.2 that keeps propagating.

Assuming that I provide you with a copy of the "problematic" DB structure, would it be useful to you for looking into the matter and providing a remedy for it? (Unfortunately, I cannot provide you with the full data due to privacy issues).

Best regards,
Alex

5

Feng Office 2 / Re: FO 2.2.2 - Workspace and group permissions problem

« on: March 23, 2013, 03:21:21 pm »

Well, I had two cases of different FO installations on Ubuntu and Debian, and they both had the same problem. I haven't tested it with a clean install to see how it behaves, but the latest upgrade has certainly not resolved the problem.

6

Feng Office 2 / Re: FO 2.2.2 - Workspace and group permissions problem

« on: March 14, 2013, 04:40:33 pm »

Just upgraded from FO 2.2.3.1 to 2.2.4 and the problem persists 

7

Feng Office 2 / Re: FO 2.2.2 - Workspace and group permissions problem

« on: February 07, 2013, 09:30:54 pm »

Just upgraded from FO 2.2.2 to 2.2.3.1 and the problem persists 

8

Feng Office 2 / FO 2.2.2 - Workspace and group permissions problem

« on: January 18, 2013, 03:12:20 pm »

When upgraded from FO 2.2.1 to 2.2.2, there seems to be a problem with the group permissions:

Within the group that already exists, there are Internal Collaborator and Administrator accounts. Administrators can post and view all files correctly, within the designated workspace. The other users, however, cannot view a newly-posted file. The only way to make this possible is to:

• edit the workspace permissions for the given group
• select a higher-level workspace
• click on "apply to all submembers"
• Save changes

The aforementioned procedure must be repeated for every subsequent file that is added, or after the last file that has been uploaded, so that they all become visible.

The problem is similar to this topic:
Data is saved but disappears! - Workspace Permissions Problem

9

Feng Office 2 / Re: Migration script for 2.0 beta-x to 2.0 stable (2.0.0.8)

« on: August 02, 2012, 08:48:20 am »

Thanks for your reply Francisco!

I had quite an extensive look at both the guides on the wiki and previous posts before posting my question (perhaps I should have mentioned it). The error I was getting was:

Code: [Select]

Failed to execute DB schema transformations. MySQL said: Table 'fo_administration_tools' already exists
I followed your suggestion, but without any luck. The same error occurs. By the way, your suggestion in that post was for the 2_1_molleja.php script. After I had a look at the source, it seems to be used for upgrading from a 2.x stable (e.g. 2.0.0.8 ) to 2.1.0, but not from a 2.x beta to 2.1.0 (which is my case).

The problem seems to originate from:
FENG_ROOT/public/install/installation/templates/sql/mysql_schema.php

Code: [Select]

-- <?php echo $table_prefix ?> fo_
-- <?php echo $default_charset ?> DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci
-- <?php echo $default_collation ?> collate utf8_unicode_ci
-- <?php echo $engine ?> InnoDB
-- varchar cannot be larger than 256
-- blob/text cannot have default values
-- sql queries must finish with ;\n (line break inmediately after ;)

CREATE TABLE `<?php echo $table_prefix ?>administration_tools` (

I can think of two workarounds:
a) Change the table prefix in this file to something else.
b) Change the "CREATE TABLE" commands into "CREATE TABLE IF NOT EXISTS".
But will this successfully migrate the existing data?

By the way, there are a few instances of "CREATE TABLE IF NOT EXISTS" commands in mysql_schema.php.

Thank you in advance,
Alex

10

Feng Office 2 / Migration script for 2.0 beta-x to 2.0 stable (2.0.0.8)

« on: July 26, 2012, 02:58:49 pm »

Hi all!

I see that there is a migration script for 1.7.5 to 2.0.0.8 (aka 2.0 stable), but I don't seem to have any luck with the upgrade from 2.0 beta-3 (aka 2.0.0.6) to either 2.0 beta-4 (aka 2.0.0.7) or higher (I did a test upgrade from 2.0.0.8 to 2.1.0 and it was absolutely fine).

Is there a chance of a migration script from 2.0 beta-3 to a higher version to be constructed in the future, or should I install 2.1.0 and enter my data from scratch?

Many thanks!